Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-4432

Memory leak when attempting to boot non-existing database with the in-memory back end

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 10.5.3.0, 10.6.1.0
    • 10.5.3.1, 10.6.1.0
    • Store
    • None
    • In-memory back end and large amount of boot attempts of non-existing databases.
    • Release Note Needed

    Description

      When attempting to boot a non-existing database with the in-memory back end, a DataStore is created and referenced by a map. Since the database doesn't exist, Derby won't use the DataStore again and it will hang around indefinitely in VFMemoryStorageFactory (or until the same database is actually created, in which case the data store will be used).

      FYI, storage factory instances are instantiated liberally, including for the same service (i.e. six instances of VFMemoryStorageFactory may be created to boot "jdbc:derby:memory:myDB").

      Attachments

        1. derby-4432-1a-mem_leak_fix.diff
          7 kB
          Kristian Waagan
        2. derby-4432-1a-mem_leak_fix.stat
          0.2 kB
          Kristian Waagan
        3. releaseNote.html
          4 kB
          Kristian Waagan

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            kristwaa Kristian Waagan
            kristwaa Kristian Waagan
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment