[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] DefaultVMModelProxyStrategy not being disposed?
|
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Pawel Piech
> Sent: Wednesday, May 11, 2011 12:10 PM
> To: CDT General developers list.
> Subject: Re: [cdt-dev] DefaultVMModelProxyStrategy not being disposed?
>
> It's a bug. We currently dispose model proxies when the
> proxies are not
> active, and there is no cache entries associated with it. But all
> proxies should be disposed when it's owning VM Provider is disposed.
Does that mean when AbstractLaunchVMProvider.dispose() is called in
this case?
I'll open a bug.
>
> Thaks,
> Pawel
>
> On 05/11/2011 03:18 AM, Marc Khouzam wrote:
> > Hi,
> >
> > I'm chasing memory leaks in DSF-GDB and I have a question
> about DSF's DefaultVMModelProxyStrategy.
> > According to the java memory tool, that class is not being
> cleaned-up for DSF-GDB's LaunchVMProvider.
> > I don't see DefaultVMModelProxyStrategy being uninstalled
> for that provider and I've confirmed
> > that DefaultVMModelProxyStrategy.dispose() is not called
> for that case.
> >
> > https://bugs.eclipse.org/238293 says that "the model owning
> the proxy is expected to
> > uninstall itself when it terminating", but I couldn't
> figure out where this was happening (or should be
> > happening).
> >
> > Should DefaultVMModelProxyStrategy be listening for launch
> events and uninstall itself on a terminate
> > or a remove? Like LaunchProxy is doing?
> >
> > Thanks for any guidance.
> >
> > Marc
> >
> >
> > _______________________________________________
> > cdt-dev mailing list
> > cdt-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
