YaCy-Bugtracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000524YaCy[All Projects] Generalpublic2015-01-19 14:052015-01-20 02:23
Reporteroyvinds 
Assigned To 
PrioritynormalSeverityminorReproducibilityalways
StatusnewResolutionopen 
ETAnone 
PlatformOSOS Version
Product VersionYaCy 1.8 
Target VersionFixed in Version 
Summary0000524: YaCy somehow runs out of memory when it's got 4gb and about 2gb free
DescriptionW 2015/01/19 13:46:05 ConcurrentLog java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException
        at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at net.yacy.kelondro.workflow.InstantBlockingThread.job(InstantBlockingThread.java:101)
        at net.yacy.kelondro.workflow.AbstractBlockingThread.run(AbstractBlockingThread.java:82)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask.run(FutureTask.java:262)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.OutOfMemoryError: Java heap space
        at java.awt.image.DataBufferInt.<init>(DataBufferInt.java:75)
        at java.awt.image.Raster.createPackedRaster(Raster.java:467)
        at java.awt.image.DirectColorModel.createCompatibleWritableRaster(DirectColorModel.java:1032)
        at java.awt.image.BufferedImage.<init>(BufferedImage.java:331)
        at net.yacy.document.parser.images.bmpParser$IMAGEMAP.<init>(bmpParser.java:149)
        at net.yacy.document.parser.images.bmpParser.parse(bmpParser.java:69)
        at net.yacy.document.parser.images.genericImageParser.parse(genericImageParser.java:116)
        at net.yacy.document.TextParser.parseSource(TextParser.java:307)
        at net.yacy.document.TextParser.parseSource(TextParser.java:214)
        at net.yacy.search.Switchboard.parseDocument(Switchboard.java:2569)
        at net.yacy.search.Switchboard.parseDocument(Switchboard.java:2526)
        ... 10 more
W 2015/01/19 13:46:05 ConcurrentLog java.lang.OutOfMemoryError: Java heap space
Steps To Reproduce1) start yacy
2) watch log
Additional InformationI don't know what kind of hardware you guys expect people to run YaCy on but it really should be able to do with 4GB of RAM without running out of memory after running less than 5 minutes.
TagsNo tags attached.
Attached Fileslog file icon memoryproblemz.log [^] (1,048,644 bytes) 2015-01-19 14:05

- Relationships

-  Notes
(0000991)
BuBu (developer)
2015-01-20 01:05

On a Windows System I've noticed that the internal Memory monitoring "Generation Memory Strategy" works better to prevent out of mem exceptions.
That will not Change the mem usage during crawling but will better Monitor Memory usage and earlier try to free some of it.

You may try this.
- goto /PerformanceMemory_p.html
- Switch off Checkbox "use Standard Memory Strategy"
(0000992)
oyvinds (reporter)
2015-01-20 01:23

I don't have a Windows infection. If your computer is infected with Windows then you can get a fix here: http://www.gentoo.org/ [^]
(0000993)
oyvinds (reporter)
2015-01-20 02:23

Thank you BuBu

http://blog.gmane.org/gmane.network.peer-to-peer.yacy.cvs/page=25 [^]

"Implementation of strategies for controlling memory resources.
You can toggle between previous (standard) and new (generation) strategy at PerformanceMemory_p.html.
The generation memory strategy is implemented with the objective of running more robust but with the cost of early stopping some tasks (eg. dht) while running low on memory.

This new strategy does respect the generational way a heap is organized on most used jvms.

These changes run fine on my 3 peers for weeks now, but as I'm human, I may fail.

Please be carefull using generation memory strategy and report errors by naming
OS, jvm and java_args."


It sounds like this could help when using yacy under icedtea on GNU/Linux too.

- Issue History
Date Modified Username Field Change
2015-01-19 14:05 oyvinds New Issue
2015-01-19 14:05 oyvinds File Added: memoryproblemz.log
2015-01-20 01:05 BuBu Note Added: 0000991
2015-01-20 01:23 oyvinds Note Added: 0000992
2015-01-20 02:23 oyvinds Note Added: 0000993


Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker