Sahoo wrote:
Our scenarios are likely to be different. In my case, the autostart
property is making the difference. I can clearly see it when I run my
test case in two configurations as described below:
Case 1. I use autostart property to install only the test bundle. In
its Activator.start(), the test bundle installs, starts, stops, and
uninstalls another bundle called foo. After foo is uninstalled, I
force gc to happen. This happens as part of Activator.start() and I
see classes from foo bundle getting garbage collected.
Case 2. I use autostart property to install both the test bundle as
well as aforementioned foo bundle. In its Activator.start(), the test
bundle stops and uninstalls foo bundle. After foo is uninstalled, I
force gc to happen. This happens as part of Activator.start(). In this
case, I don't see class from foo bundle getting garbage collected.
I later on figured out the reason for this as well. The attached patch
solves the issue.
This sounds really odd, since I cannot understand why the autostart
property would have any impact here, but thanks for looking into it. I
will try to investigate it following your instructions above.
-> richard
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
