tasfe / crawler4j

Automatically exported from code.google.com/p/crawler4j
0 stars 1 forks source link

Memory leakage in crawler4j caused by database environment #231

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Consecutive execution of crawlers one after the other in a single 
application.

What is the expected output? What do you see instead?
The shutdown method should release all resources. Instead, a memory leak occurs.

What version of the product are you using?
3.5

Please provide any additional information below.
The database environment of crawler4j (com.sleepycat.je.Environment) is never 
closed. This is causing memory leaks. Closing it after pageFetcher is shut down 
in monitorThread (line 235 of CrawlController.java) solves the problem. Any 
further comments or recommendations regarding this issue are welcome.

Original issue reported on code.google.com by a.o.ma...@gmail.com on 1 Aug 2013 at 12:22

GoogleCodeExporter commented 9 years ago
did you turn env into an instance variables in then used env.close(); on line 
235?

Original comment by jeger...@gmail.com on 1 Jun 2014 at 7:44

GoogleCodeExporter commented 9 years ago
Fixed.

Leak is closed.

Revision hash: 9efaeef20c30 

Original comment by avrah...@gmail.com on 11 Aug 2014 at 8:27