db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-912) OutOfMemory error on continuous execution of SQL statement
Date Thu, 19 Oct 2006 21:43:36 GMT
    [ http://issues.apache.org/jira/browse/DERBY-912?page=comments#action_12443651 ] 
Knut Anders Hatlen commented on DERBY-912:

One simple solution is to remove all trailing null elements from the sorts vector on commit.
That should leave the held controllers open and not interfere with the sort ids. While it
does not solve the general case (a held controller may prevent space reclaimation at the start
of the vector), it does solve the most common cases. With that change, the test program completed
without running out of memory (-Xmx10M).

> OutOfMemory error on continuous execution of SQL statement
> ----------------------------------------------------------
>                 Key: DERBY-912
>                 URL: http://issues.apache.org/jira/browse/DERBY-912
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Store
>    Affects Versions:
>         Environment: cygwin, jdk 1.4
>            Reporter: Manish Khettry
> After fixing the original memory leak, I still run into problems on repeated execution
of a sql statement. Take the sample program in the bug and run it with a small heap size (4m).
After around 80-90K executions an outofmemory error is thrown. I took snapshots of the heap
while the program was running but couldn't find anything obviously wrong. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message