Cleaning up plugin resources

[bgowland]

What does PVRX2 do with plugins when it exits? I've had situation when I've exited PVRX2 with my DVB-T radio plugin still playing music. The external exe doesn't get shutdown by PVRX2 (obviously) so carries on merrily producing an ever-growing mp3 buffer file. :eek:

I've tried adding a destructor to the plugin but it doesn't seem to be working - it's either not being called or the cleanup isn't being given time to complete.

What's the best way to cleanup this sort of thing?

Cheers,
Brian

[sub]

I'm not really sure. As you've already found, .net doesnt guarantees it'll call the destructor when the app exits.

You could get the two apps to share a mutex or something similar (with the plugin acquiring it immediately and holding on to it, and the exe trying to acquire it. If it manages to acquire it, then the plugin process has gone away).

[sub]

I'll add a ShuttingDown event to the IEventNotification interface for the next release. I cant provide this as a patch though, since it'll break if a user doesnt get both PVRX2.exe and GBPVRPublic.dll...which complicates things if I need to provide any patches before the next release.

[bgowland]

Thanks for the replies - I'm sure the shutting down event would be useful for developers in the future and worth adding.

I was thinking of some sort of 'keep alive' mechanism although hadn't thought of a mutex.

I'll probably add the equivalent of a Remoting 'ping'. Every 60 seconds say, source just sends a dummy command which returns some (any) sort of response. Useful for both ends - the source does whatever it needs to if it gets no response and the destination does whatever it needs to if it doesn't get 'pinged' for a certain amount of time.

Cheers,
Brian