Our deployed application is failing shortly after starting
with an out of memory condition. I seem to recall that there is a way to have
the debug vm output what it is doing message send by message send. Does this
ring any bells with anyone? -----
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Joerg:
> Our deployed application is failing shortly after starting with an out of memory condition. I seem to recall that there is a way to have the debug vm output what it is doing message send by message send. Does this ring any bells with anyone? FWIW, "one of" the typical reasons for this has to do with Fonts. In any case, what platform is the deployed application running on? And So It Goes Sames ______________________________________________________________________ Samuel S. Shuster [|] VisualWorks Engineering, Store Project Smalltalk Enables Success -- What Are YOU Using? _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
In reply to this post by Joerg Beekmann, DeepCove Labs (YVR)
Run with the debug VM and use the -o10s command line option.
Pipe it to a file. Use a file viewer than can handle large files
:-)
At 05:44 PM 2010-04-26, Joerg Beekmann, DeepCove Labs \(YVR\) wrote: Content-Class: urn:content-classes:message --
Alan Knight [|], Engineering Manager, Cincom Smalltalk
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
That’s what I recall. Thanks Alan From: Alan Knight
[mailto:[hidden email]] Run with the debug VM and use the -o10s command line option.
Pipe it to a file. Use a file viewer than can handle large files :-) Content-Class: urn:content-classes:message -- Alan Knight [|], Engineering Manager, Cincom Smalltalk _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
One pattern to watch out for in those kind of logs is that
the system tries to raise an exception but is unable to do so, the
attempt raises another exception, and so forth. So going back early in
the log and finding the early references to e.g. Notifier might be more
helpful than working backwards. So, of course, is looking for very long
lists of the same message, whose implementation is recursive :-)
At 06:24 PM 2010-04-26, Joerg Beekmann, DeepCove Labs \(YVR\) wrote: ThatÂ’s what I recall. --
Alan Knight [|], Engineering Manager, Cincom Smalltalk
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Free forum by Nabble | Edit this page |