[Bug]: Closing the Standalone plugin gives a Violation Access error

[bryfa]

trafficstars

Detailed steps on how to reproduce the bug

Just build a plugin with a standalone version. Run the standalone version for debugging Close the plugin

What is the expected behaviour?

Should handle this without any issue when closing

Operating systems

Windows

What versions of the operating systems?

Windows 11 Pro Version 10.0.22621 Build 22621

Architectures

x86_64

Stacktrace

No response

Plug-in formats (if applicable)

No response

Plug-in host applications (DAWs) (if applicable)

No response

Testing on the develop branch

The bug is present on the develop branch

Code of Conduct

• [X] I agree to follow the Code of Conduct

[bryfa]

[bryfa]

Tried this in the DEV branch and got the critical error when closing the standalone test app

[Anthony-Nicholls]

@bryfa are you able to reproduce this issue using one of the example plugin projects?

[bryfa]

Will try that, the thing is that is not consistent..

[Anthony-Nicholls]

The best way for us to take a look is with an example that demonstrates the issue. My best guess is that you are accessing an object that has already been deleted. You could also try enabling the address santizer to see if this provides any useful information.

[bryfa]

I didnt got the error lately and maybe your right about the deleted object. Happened only when closing the standalone app. I enabled the sanitizer, hope it will help finding the issue. Thanks for the tip.