Re: Memory Leak
William Taylor <[email protected]> Thu, 25 Feb 2010 23:53:24 -0800
| Newsgroups | gmane.comp.db.mysql.java |
|---|---|
| Message-ID | <[email protected]> |
On Feb 25, 2010, at 11:44 PM, Christopher G. Stach II wrote: > I'm not a MySQL developer, but... >=20 >> Has this issue ever been resolved?=20 >> http://bugs.mysql.com/bug.php?id=3D10954 >=20 > It's not a bug. WTF? That is from 2005. >=20 Yep oldies are goodies.. It also says "Will not fix!" so... >> Working on some code where I select 4 million rows and store the >> results in a short array. >=20 > Don't do that. >=20 Why? What is your reasoning behind *not* doing that ?=20 Perhaps you understand my application better then I ? >> java grows to 455M and never lets go of the memory. >=20 > Never? Do you have a test case that shows that *proper* code doesn't = allow the JVM to GC? If you select 4M rows and store them in memory, do = you expect them to be stored in fairy dust? Do you have profiler output? = If you have a negative test case and you still have a bunch of RAM = unaccounted for, that's a bug report for Sun or whoever makes your JVM. >=20 Yes I added extra fairy dust to the server so it shouldn't be a problem. Statement gets closed, Result set gets closed, connection gets closed. ram never goes down. I can write up a test case latter.= -- MySQL Java Mailing List For list archives: http://lists.mysql.com/java To unsubscribe: http://lists.mysql.com/[email protected]