https://bugzilla.wikimedia.org/show_bug.cgi?id=51769
--- Comment #38 from [email protected] --- before restarting the java process, could you trace it with: * jps -l to find out the process id * strace to see if it excessivly calls into the operating system * jstack * kill -QUIT <p> to print the stacktrace * jmap -heap <p> to find memory usage * jmap -histo:live <p> | head to find excessivly used classes * if you have ui, you might try jconsole or http://visualvm.java.net as well you might want to set the java -XX:+HeapDumpOnOutOfMemoryError parameter when starting, so it writes a heap dump early enough. it can be analyzed with jhat. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
