Here's a hs_err file after a crash I had yesterday. We turned off some things in our code without restarting and the crashes have virtually stopped but we do still get the off one here and there where the application has not been restarted, could be that the problem lingers and builds up in time, who knows.
It's a sigsegv in GCTaskThread. From the occupation in eden it looks like it happened during a scavenge (ParNew). Maybe an expert in some dark cave could shed some more light on it. On Tue, 2010-03-16 at 22:00 +0100, André Warnier wrote: > Carl wrote: > > My approach is to get something (a JVM) that works and then gradually > > change until it breaks. Then, I know what is causing the problem. To > > date, I haven't been able to get a JVM that works. > > > I think we understand that, and agree. > Our remarks were "tongue in cheek", if that is the right expression. > > At the bottom of things, finding a bug in the most recent JVM would be > much more globally important than finding it in your applications, > particularly a bug that can cause the JVM to segfault. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
