YaCy-Bugtracker - YaCy
View Issue Details
0000782YaCy[All Projects] Generalpublic2018-10-31 17:352018-11-08 08:13
Subversor 
 
urgentmajoralways
newopen 
none 
PCWindows10
YaCy 1.9 
 
0000782: YaCy becomes unresponsive
HTTP ERROR 500
Problem accessing /. Reason:

    Server Error
Caused by:
java.lang.OutOfMemoryError: GC overhead limit exceeded
Powered by Jetty:// 9.4.12.v20180830
Let YaCy run. YaCy ALWAYS becomes slow, then eventually completely unresponsive.
YaCy version: 1.921/9788
Java version: 1.8.0_181

RAM max: 7.11 GB
DISK used: (approx.) 47.45 GB
DISK free: 1,812.78 GB
No tags attached.
Issue History
2018-10-31 17:35SubversorNew Issue
2018-11-08 08:13lucNote Added: 0001501

Notes
(0001501)
luc   
2018-11-08 08:13   
How many documents do you have in your local index ?
Would you like to attach the log file including the error traces?

You can even do more by setting up your peer to generate a heap dump on out of memory errors (with the -XX:+HeapDumpOnOutOfMemoryError JVM parameter, added for example in the JAVA_ARGS of your YaCy start script). Then you will be able to open that dump with a tool like VisualVM to analyze which objects consume the most of the memory and eventually share here the report.