[
https://issues.apache.org/jira/browse/DERBY-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-2480:
-----------------------------------
Priority: Minor (was: Major)
Derby Info: [Regression]
Environment:
Windows Vista, JDK 1.4.2_13
Solaris 10, Sun JDK 1.4.2 & 1.5.0
was:Windows Vista, JDK 1.4.2_13
Affects Version/s: 10.3.0.0
I tried the repro on Solaris 10 with both Java 1.4.2 and Java 1.5. Both failed
with Derby 10.2.2.0 and with trunk.
However, I was not able to reproduce the bug with Derby 10.1.3.1, so this seems
like a regression. I stopped the test after a little over 500'000 iterations.
We could maybe add the repro to the test suite, as doing the connect a
reasonable number of times (say 20-50000 repetitions) doesn't take long when
the memory leak is not around. 50000 iterations with 10.1.3.1 took around 25
seconds on my machine. The problem is that we have to run this in a separate
VM, and I don't know how good support we have for that currently?
I also lowered the priority, as I consider this use-case a bit "on the edge"
compared to common practice.
Thank you for the report :)
> DriverManager.getConnection leaks memory using EmbeddedDriver on non-existent
> database
> --------------------------------------------------------------------------------------
>
> Key: DERBY-2480
> URL: https://issues.apache.org/jira/browse/DERBY-2480
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.2.2.0, 10.3.0.0
> Environment: Windows Vista, JDK 1.4.2_13
> Solaris 10, Sun JDK 1.4.2 & 1.5.0
> Reporter: Jeff Clary
> Priority: Minor
> Attachments: testOpenOfMissingDatabase.java
>
>
> Repeated calls to
> java.sql.DriverManager.getConnection("jdbc:derby:C:\\DOES_NOT_EXIST") leak
> memory and eventually lead to an OutOfMemoryError.
> This bug is similar to DERBY-1947 in that ContextManager objects are not
> getting removed from the HashSet. The attached test program demonstrates the
> issue. When run with VM options -Xms8m -Xmx8m, it throws an OutOfMemoryError
> after 19022 calls to DriverManager.getConnection.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
