>>>>> "TM" == Tom Metro <[email protected]> writes:
TM> Some code I'm working on is triggering an out of memory error, and I'd
TM> like to figure out what specifically is responsible. (It's a complex
TM> system with dozens of libraries and it runs in parallel across a cluster
TM> of machines. Running the code in a debugger isn't a practical option.)
TM> Any recommendation for tools to do this?
TM> I don't recall if the typical profiling tools record memory usage, but a
TM> traditional profiler would be overkill for what I need.
TM> The ideal solution would be something that could hook the OOM exception
TM> and dump the symbol table along with stats for how much memory each
TM> symbol is occupying. Another useful possibility would be dumping the
TM> call stack.
if you run out of vram and you didn't expect it, wouldn't that signify a
possible leak? maybe Devel::Leak will help. i know a very good malloc
replacement and leak detector lib but it is closed source and
commercial. if your shop can afford it it may be worth the cost. or use
it under a free 6 month trial. i connected the author (a good friend of
mine) to the perl6 dev team to try it out but it didn't get enough
momentum. i was trying to get him to open source it and get a wider user
base who might pay for support. anyhow it is worth checking out if it
can help. you can find it at:
http://newcodeinc.com/
uri
--
Uri Guttman ------ [email protected] -------- http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support ------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
_______________________________________________
Boston-pm mailing list
[email protected]
http://mail.pm.org/mailman/listinfo/boston-pm
