[jira] [Closed] (SLING-4783) The JavaScript scripting engine can generate classloader leaks

[ https://issues.apache.org/jira/browse/SLING-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu closed SLING-4783. --- The JavaScript scripting engine can generate classloader leaks

[jira] [Updated] (SLING-4783) The JavaScript scripting engine can generate classloader leaks

[ https://issues.apache.org/jira/browse/SLING-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-4783: Attachment: heap dump analysis.png The JavaScript scripting engine can generate classloader leaks

[jira] [Created] (SLING-4783) The JavaScript scripting engine can generate classloader leaks

Radu Cotescu created SLING-4783: --- Summary: The JavaScript scripting engine can generate classloader leaks Key: SLING-4783 URL: https://issues.apache.org/jira/browse/SLING-4783 Project: Sling

[jira] [Resolved] (SLING-4783) The JavaScript scripting engine can generate classloader leaks

=r1684189]. The JavaScript scripting engine can generate classloader leaks -- Key: SLING-4783 URL: https://issues.apache.org/jira/browse/SLING-4783 Project: Sling Issue Type: Bug

Re: Classloader leaks ?

Hi Ian, I implemented the proposed approach in [1]. Can you give it a try and let me know if it works for you. Chetan Mehrotra [1] https://github.com/chetanmeh/sling-leak-detector On Wed, Jan 29, 2014 at 5:43 PM, Felix Meschberger fmesc...@adobe.com wrote: Hi Agreed, this sounds like an

Re: Classloader leaks ?

Hi Chetan I like this very much. Cool work +1 to get this into Sling, if you will :-) Two comments: * There is a stray pom.xml in the src folder * I suggest to use BundleTracker which takes aways the burden of initial bundle scan from you. Regards Felix Am 31.01.2014 um 11:17 schrieb Chetan

[jira] [Created] (SLING-3360) Bundle to detect classloader leaks

Chetan Mehrotra created SLING-3360: -- Summary: Bundle to detect classloader leaks Key: SLING-3360 URL: https://issues.apache.org/jira/browse/SLING-3360 Project: Sling Issue Type: New Feature

Re: Classloader leaks ?

Hi Chetan, Excellent, works really well. Much easier than transferring GB of heap over a network to do the analysis. To test I: built it, loaded it, restarted my JVM with -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled and refreshed a few bundles I knew to be suspect and they appeared in

Classloader leaks ?

Hi, Is it possible, in code running in a bundle, to detect if the OSGi container has a classloader that is being pinned and should have been garbage collected. I have recently found code (in bundle A) that registered a implementation class with a service outside its own bundle (bundle B) but

Re: Classloader leaks ?

Hi Am 29.01.2014 um 09:53 schrieb Ian Boston i...@tfd.co.uk: Hi, Is it possible, in code running in a bundle, to detect if the OSGi container has a classloader that is being pinned and should have been garbage collected. Well, that bundle would have to analyze class loaders and memory

Re: Classloader leaks ?

Hi, On 29 January 2014 09:16, Felix Meschberger fmesc...@adobe.com wrote: Hi Am 29.01.2014 um 09:53 schrieb Ian Boston i...@tfd.co.uk: Hi, Is it possible, in code running in a bundle, to detect if the OSGi container has a classloader that is being pinned and should have been garbage

Re: Classloader leaks ?

Sounds good to me. The bundle will need to be there all the time, but its going to be tiny and its only 1 more thread. Best Regards Ian On 29 January 2014 11:21, Chetan Mehrotra chetan.mehro...@gmail.com wrote: One possible approach can be that 1. Have a custom bundle listener. This would

Re: Classloader leaks ?

Hi Agreed, this sounds like an interesting approach to follow. Regards Felix Am 29.01.2014 um 12:21 schrieb Chetan Mehrotra chetan.mehro...@gmail.com: One possible approach can be that 1. Have a custom bundle listener. This would maintain some structure around bundle 2. Use Java Phantom