Compiling std.algorithm for unittests consumes all the memory on many machines. I've been looking into what is allocating all that memory, and it isn't so easy without adding instrumentation code anywhere.

Anyone know of a convenient tool to do this on Linux?

(valgrind just hangs, or at least I gave up on it after 6 hours)

Maybe Dr. Memory could work out well as an alternative to valgrind with this issue?
http://www.drmemory.org/

On Saturday, 22 June 2013 at 21:41:15 UTC, Walter Bright wrote:
> Compiling std.algorithm for unittests consumes all the memory on many machines. I've been looking into what is allocating all that memory, and it isn't so easy without adding instrumentation code anywhere.
>
> Anyone know of a convenient tool to do this on Linux?
>
> (valgrind just hangs, or at least I gave up on it after 6 hours)

With valgrind; did you use massif?
That would be the right tool to use instead of memcheck (the default tool).

On 6/22/2013 4:24 PM, Kiith-Sa wrote:
> With valgrind; did you use massif?
> That would be the right tool to use instead of memcheck (the default tool).

I've never heard of massif. Will check it out.

On 6/22/2013 4:18 PM, Geancarlo Rocha wrote:
> Maybe Dr. Memory could work out well as an alternative to valgrind with this issue?
> http://www.drmemory.org/

The web page indicates it is designed for looking for memory allocation bugs. That isn't the issue I'm having.

On 2013-06-22 23:41, Walter Bright wrote:
> Compiling std.algorithm for unittests consumes all the memory on many
> machines. I've been looking into what is allocating all that memory, and
> it isn't so easy without adding instrumentation code anywhere.
>
> Anyone know of a convenient tool to do this on Linux?
>
> (valgrind just hangs, or at least I gave up on it after 6 hours)

There's a tool called dtrace on Mac OS X and *BSD which possibly could be used for this. Don't know if there's a corresponding tool for Linux. Hmm, seems to be available on Oracle Linux.

http://en.wikipedia.org/wiki/DTrace

-- 
/Jacob Carlborg

Am 22.06.2013 23:41, schrieb Walter Bright:
> Compiling std.algorithm for unittests consumes all the memory on many machines.
> I've been looking into what is allocating all that memory, and it isn't so easy
> without adding instrumentation code anywhere.
>
> Anyone know of a convenient tool to do this on Linux?
>
> (valgrind just hangs, or at least I gave up on it after 6 hours)

there are "sometimes" better tools on windows or commercials - you should try these

http://www.softwareverify.com/cpp-memory.php - i like this one

http://mtuner.net/

http://www.puredevsoftware.com/MemPro.htm

all for memory leak detection, but also doing memory profiling

On Sunday, 23 June 2013 at 09:37:26 UTC, Jacob Carlborg wrote:
> On 2013-06-22 23:41, Walter Bright wrote:
>> Compiling std.algorithm for unittests consumes all the memory on many
>> machines. I've been looking into what is allocating all that memory, and
>> it isn't so easy without adding instrumentation code anywhere.
>>
>> Anyone know of a convenient tool to do this on Linux?
>>
>> (valgrind just hangs, or at least I gave up on it after 6 hours)
>
> There's a tool called dtrace on Mac OS X and *BSD which possibly could be used for this. Don't know if there's a corresponding tool for Linux. Hmm, seems to be available on Oracle Linux.
>
> http://en.wikipedia.org/wiki/DTrace

That would be SystemTap on Linux. However, I wonder if it is the right tool for the job.

On 2013-06-23 15:12, qznc wrote:

> That would be SystemTap on Linux. However, I wonder if it is the right
> tool for the job.

Mac OS X has Instruments as well, which is used for these type of tasks. It's built on top of Dtrace:

http://en.wikipedia.org/wiki/Instruments_(application)

-- 
/Jacob Carlborg

On 6/23/2013 5:21 AM, dennis luehring wrote:
> Am 22.06.2013 23:41, schrieb Walter Bright:
>> Compiling std.algorithm for unittests consumes all the memory on many machines.
>> I've been looking into what is allocating all that memory, and it isn't so easy
>> without adding instrumentation code anywhere.
>>
>> Anyone know of a convenient tool to do this on Linux?
>>
>> (valgrind just hangs, or at least I gave up on it after 6 hours)
>
> there are "sometimes" better tools on windows or commercials - you should try these
>
> http://www.softwareverify.com/cpp-memory.php - i like this one
>
> http://mtuner.net/
>
> http://www.puredevsoftware.com/MemPro.htm
>
> all for memory leak detection, but also doing memory profiling

Thanks!