| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | Pierre Le Mouëllic <pierre(dot)lemouellic(at)xgs-france(dot)com> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Memory leak ? |
| Date: | 2011-04-06 10:50:12 |
| Message-ID: | BANLkTi=+1hshp_HeOBVGUgaHwE6fwB4zig@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
2011/4/6 Pierre Le Mouëllic <pierre(dot)lemouellic(at)xgs-france(dot)com>:
> In eclipse Helios profiler, Jdbc3ResultSet live instances increase (and
> never decrease). Same thing with
> org.postgresql.core.v3.QueryExecutorImpl$ErrorTrackingResultHandler and
> org.postgresql.core.v3.QueryExecutorImpl$1 classes.
When profiling, has a full GC & weak reference collection happened
before you count "live instance"?
Probably those "live" instances are only weakly reachable and will be
cleaned up later.
(The driver uses weak references + a reference queue that is polled
before each query execution to clean up server-side allocated
resources corresponding to JDBC statements / resultsets that were not
properly closed, just discarded)
If that's not the problem, I'd need to know the path from a GC root to
the live instances.
Oliver
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Cottenceau | 2011-04-06 10:52:41 | Re: Memory leak ? |
| Previous Message | Dave Cramer | 2011-04-06 10:47:56 | Re: Memory leak ? |