search

philbritton / gisgraphy

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

memory leak #10

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. run the bench script 
2. you will get an OutOfMemory error due to a memory leak

Please use labels and text to provide additional information.

Original issue reported on code.google.com by davidmasclet@gmail.com on 15 Feb 2010 at 4:14

GoogleCodeExporter commented 9 years ago 
after analyzing the heap dump with eclipse memory analyzer, i found a memory 
leak in
dbcp due to preparestatement pooling. after some bench i doesn't see 
performance gain
and if i disable the prepareStatement pooling, there is no memory leak anymore.

I disable it !

Original comment by davidmasclet@gmail.com on 15 Feb 2010 at 4:16

GoogleCodeExporter commented 9 years ago

Original comment by davidmasclet@gmail.com on 15 Feb 2010 at 4:17

GoogleCodeExporter commented 9 years ago 
here are the keywords generated by eclipse memory analyzer :

java.util.HashMap$Entry[]
gisgraphy
org.apache.commons.dbcp.BasicDataSource
org.postgresql.jdbc3.Jdbc3PreparedStatement

i put those keywords for people who will search for that keywords

Original comment by davidmasclet@gmail.com on 15 Feb 2010 at 4:20