> Bill Pringlemeir wrote: >> I finally have a good trace of a crash when searching. I think >> this is a high load situation.
On 13 Nov 2006, [EMAIL PROTECTED] wrote: > Were you close to any memory limit? No, it is a CPU load. The memory system might be using swap. However, I am definitely not running out of swap. It is possible that GUI code within gtkg had been paged out as it would not be active. > If those crashes are reproducible you could try > export G_SLICE=always-malloc I guess that this will result in a slow down? It is not reproducible. As a matter of fact, it is far less common for the last few months. However, who knows how many different variables have changed in that time [I have new kernels, glib, gtk, gcc, and of course gtkg]. It was sensible in that it traced back to the main() routine. Many of the previous cores seemed to have incomplete stack traces. Will dmalloc check glib's slice allocator? Is there a slice debug mode for detecting over-writes, use of free memory, etc. has occurred? fwiw, Bill Pringlemeir. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Gtk-gnutella-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
