YaCy-Bugtracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000782YaCy[All Projects] Generalpublic2018-10-31 17:352018-11-08 08:13
ReporterSubversor 
Assigned To 
PriorityurgentSeveritymajorReproducibilityalways
StatusnewResolutionopen 
ETAnone 
PlatformPCOSWindowsOS Version10
Product VersionYaCy 1.9 
Target VersionFixed in Version 
Summary0000782: YaCy becomes unresponsive
DescriptionHTTP ERROR 500
Problem accessing /. Reason:

    Server Error
Caused by:
java.lang.OutOfMemoryError: GC overhead limit exceeded
Powered by Jetty:// 9.4.12.v20180830
Steps To ReproduceLet YaCy run. YaCy ALWAYS becomes slow, then eventually completely unresponsive.
Additional InformationYaCy 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
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
(0001501)
luc (reporter)
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.

- Issue History
Date Modified Username Field Change
2018-10-31 17:35 Subversor New Issue
2018-11-08 08:13 luc Note Added: 0001501


Copyright © 2000 - 2018 MantisBT Team
Powered by Mantis Bugtracker