Petals SE POJO

Memory leak on installation/uninstallation

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: 2.2.2
  • Fix Version/s: None
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    When installing, uninstalling the SE POJO several times, an OOM exception occurs after some installation.

    This OOM is due to a memory leak occurring on the uninstallation. The component classloader is not unloaded when uninstalling the compoent. The most probably cause is that a Singleton is loaded from the component classloader

    A workaround was applied by svn#15445. It should be completely replaced by a free of the Singleton.

    Show
    When installing, uninstalling the SE POJO several times, an OOM exception occurs after some installation. This OOM is due to a memory leak occurring on the uninstallation. The component classloader is not unloaded when uninstalling the compoent. The most probably cause is that a Singleton is loaded from the component classloader A workaround was applied by svn#15445. It should be completely replaced by a free of the Singleton.
  • Environment:
    -

Activity

Roland Naudin made changes - Wed, 3 Nov 2010 - 10:38:27 +0100
Field Original Value New Value
Status New [ 10000 ] Open [ 10002 ]
Priority Major [ 3 ]
Christophe DENEUX made changes - Thu, 22 Mar 2012 - 14:23:43 +0100
Assignee Admin [ rnaudin ]
Description When installing, uninstalling the SE POJO several times, an OOF exception occurs after some installation.

This OOP is due to a memory leak occuring on the uninstallation. The component classloader is not unloaded when uninstalling the compoent. The most probably cause is that a Singleton is loaded from the component classloader

A workaround was applyed by svn#15445. It should be completly replaced by a free of the Singleton.
When installing, uninstalling the SE POJO several times, an OOF exception occurs after some installation.

This OOF is due to a memory leak occuring on the uninstallation. The component classloader is not unloaded when uninstalling the compoent. The most probably cause is that a Singleton is loaded from the component classloader

A workaround was applyed by svn#15445. It should be completly replaced by a free of the Singleton.
Christophe DENEUX made changes - Thu, 22 Mar 2012 - 14:24:46 +0100
Description When installing, uninstalling the SE POJO several times, an OOF exception occurs after some installation.

This OOF is due to a memory leak occuring on the uninstallation. The component classloader is not unloaded when uninstalling the compoent. The most probably cause is that a Singleton is loaded from the component classloader

A workaround was applyed by svn#15445. It should be completly replaced by a free of the Singleton.
When installing, uninstalling the SE POJO several times, an OOM exception occurs after some installation.

This OOM is due to a memory leak occurring on the uninstallation. The component classloader is not unloaded when uninstalling the compoent. The most probably cause is that a Singleton is loaded from the component classloader

A workaround was applied by svn#15445. It should be completely replaced by a free of the Singleton.
Victor NOËL made changes - Mon, 5 Oct 2015 - 12:01:12 +0200
Resolution Won't Fix [ 2 ]
Status Open [ 10002 ] Resolved [ 10004 ]
Assignee Victor NOËL [ vnoel ]

People

Dates

  • Created:
    Thu, 29 Jul 2010 - 11:03:26 +0200
    Updated:
    Mon, 5 Oct 2015 - 12:01:12 +0200
    Resolved:
    Mon, 5 Oct 2015 - 12:01:12 +0200