db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manish Khettry (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-912) OutOfMemory error on continuous execution of SQL statement
Date Sat, 18 Feb 2006 02:45:04 GMT
    [ http://issues.apache.org/jira/browse/DERBY-912?page=comments#action_12366875 ] 

Manish Khettry commented on DERBY-912:
--------------------------------------

It looks like elements from the sorts vector in RAMTransaction are never removed. dropSort
merely nulls out the element. If you repeatedly open/execute/close a query that uses a sorter
you will leak one reference every iteration. 

> OutOfMemory error on continuous execution of SQL statement
> ----------------------------------------------------------
>
>          Key: DERBY-912
>          URL: http://issues.apache.org/jira/browse/DERBY-912
>      Project: Derby
>         Type: Sub-task
>     Versions: 10.0.2.0
>  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


Mime
View raw message