> No, I have several crash reports with no backtrace at all, just information > about the heap being exhausted. Which makes me think there might be something > that causes a runaway loop that allocates memory — but I don't know how to > go about catching that sort of thing.
I'd employ some heuristics. Check regularly for free space; if it's near the zero mark, get a backtrace for all threads and write them to a file. 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.
