You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Øystein Grøvlen (JIRA)" <ji...@apache.org> on 2008/02/12 15:07:09 UTC

[jira] Issue Comment Edited: (DERBY-3354) Select from large lob table with embedded gives OutOfMemoryError

    [ https://issues.apache.org/jira/browse/DERBY-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568123#action_12568123 ] 

oysteing edited comment on DERBY-3354 at 2/12/08 6:05 AM:
-----------------------------------------------------------------

The attached patch makes the repro run without getting an OutOfMemory error.
This is achieved by removing the LOB object from the locator mapping.

I am not setting patch available since test cases should also be added,
and I have not run the regression test suites.

      was (Author: oysteing):
    The attached patch makes the repro run without getting an OutOfMemory error.
This is achieved by removing the LOB object from the locator mapping.

  
> Select from large lob table with embedded gives OutOfMemoryError
> ----------------------------------------------------------------
>
>                 Key: DERBY-3354
>                 URL: https://issues.apache.org/jira/browse/DERBY-3354
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.3.1.4, 10.3.2.1, 10.4.0.0
>            Reporter: Kathey Marsden
>         Attachments: derby-3354.diff, LocLeak.java
>
>
> Retrieving from a large table with lobs gives an OutOfMemoryException, even if free() is explictly called on the lob.   I believe this is because EmbedConnection.addLobMapping is called for every lob creation but is never cleared until commit or rollback, even if the lob is freed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.