@devbotas is correct, and ScottPlot.Plot implements IDisposable so you can call Plot.Dispose() as a control is being removed... but when/how that happens seems to be platform specific.

It's worth noting that disposing this stuff is the job of the garbage collector and it's done automatically. We probably don't need to be managing this ourselves. However, we probably can, so let's look into it:

WinForms: We can call Plot.Dispose() when the OnHandleDestroyed event is invoked

WPF: There doesn't seem to be a similar event or override for WPF controls. There's the Unloaded event which is close, but a control can be unloaded from one thing and loaded into another, so it's not a good idea to manually dispose the plot in response to that event. I'm not sure what to do for WPF.

I'm a bit scared to take any action right now. I think if users want to remove controls programmatically and don't want the garbage collector to dispose of the items, users can manually call things like formsPlot1.Plot.Dispose() and hope no additional render requests come in

Controls: how to dispose properly? #3271

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions