Am 06.05.2013 22:16, schrieb Stephen Boyd:
Ok. I tested it and it definitely helps.
==10728== LEAK SUMMARY:
==10728==definitely lost: 316,355,458 bytes in 8,652 blocks
==10728==indirectly lost: 1,327,251,588 bytes in 16,180,628 blocks
==10728== possibly lost: 677,049,918 bytes in
On 05/09/13 08:10, René Scharfe wrote:
Am 06.05.2013 22:16, schrieb Stephen Boyd:
Ok. I tested it and it definitely helps.
==10728== LEAK SUMMARY:
==10728==definitely lost: 316,355,458 bytes in 8,652 blocks
==10728==indirectly lost: 1,327,251,588 bytes in 16,180,628 blocks
==10728==
On 04/30/13 15:47, René Scharfe wrote:
Am 30.04.2013 02:11, schrieb Stephen Boyd:
(resending since the attachment seems to make vger sad)
Hi,
I'm running git rev-list | git cherry-pick --stdin on a range of about
300 commits. Eventually the chery-pick dies with:
error: cannot fork()
On 04/30/13 15:47, René Scharfe wrote:
Am 30.04.2013 02:11, schrieb Stephen Boyd:
(resending since the attachment seems to make vger sad)
Hi,
I'm running git rev-list | git cherry-pick --stdin on a range of about
300 commits. Eventually the chery-pick dies with:
error: cannot fork()
Stephen Boyd sb...@codeaurora.org writes:
(resending since the attachment seems to make vger sad)
Hi,
I'm running git rev-list | git cherry-pick --stdin on a range of about
300 commits. Eventually the chery-pick dies with:
error: cannot fork() for commit: Cannot allocate memory
Am 30.04.2013 02:11, schrieb Stephen Boyd:
(resending since the attachment seems to make vger sad)
Hi,
I'm running git rev-list | git cherry-pick --stdin on a range of about
300 commits. Eventually the chery-pick dies with:
error: cannot fork() for commit: Cannot allocate memory
(resending since the attachment seems to make vger sad)
Hi,
I'm running git rev-list | git cherry-pick --stdin on a range of about
300 commits. Eventually the chery-pick dies with:
error: cannot fork() for commit: Cannot allocate memory
Running valgrind shows me that the tree traversal
7 matches
Mail list logo