On Tue, May 18, 2010 at 10:22:32AM +0200, Jan Rychter wrote: > This could be difficult. It happens unpredictably, it could be months, days, > or hours before the bug is triggered. The backtrace isn't always as clear as > above, in fact sometimes I only see a "heap exhausted" message. > > It is of course possible that I'm exhausting the heap in some runaway code — > but if so, how do I track it down?
Does the backtrace always point at this spot, i.e. the pathname stuff? Leslie -- You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/weblocks?hl=en.
