No expert here- I downloaded pluginval to find the code issue for the plugins immediate crash.
Heres the error code. Maybe this is fixable in some fasion? I updated to Big Sur and this suddenly stopped working despite every other plugin working fine.
Code:
pluginval v0.2.9 - JUCE v6.0.1
Started validating: /Library/Audio/Plug-Ins/VST/iZotope Insight.vst
Random seed: 0x439b480
Validation started: 22 Nov 2020 6:35:31pm
Strictness level: 5
Starting test: pluginval / Scan for known types: /Library/Audio/Plug-Ins/VST/iZotope Insight.vst…
Num types found: 1
Have you tried testing both debug and release builds of the same plugin? If so, do they crash in the same place?
If the debug version of the plugin crashes during validation, you could try running the validator under a debugger with --validate-in-process. It could be that the plugin will trigger some jasserts before crashing, which might point to the cause of the problem.
Im using the GUI version and so unsure how to run codes within the testing platform ! I can say however this is a release build of the plugin and not a debug [don’t have access to one]
But it seems to me that you should contact iZotope and file a bug report with them. To tell them that their plugin crashes, when loaded in a DAW under Big Sur.
Pluginval is a tool especially for plugin developers, designed to trigger as much possible sources of crashes to put your plugin under some kind of stress test during development. If a test fails, you usually try running a debug build with a debugger attached which will hopefully give you some insight about where in your code the error happens, so you can fix it there.
Now obviously you are not working at Izotope and therefore have no possibility of running a debug build. You still can trigger a fail, but with a release build with stripped symbols the crash report is useless. And even if you could see what’s wrong there, you could never fix it without having access to the plugins source code.
So what are you trying to achieve here? You say that it works fine in Ableton Live, so I guess that you had a problem with some other host? If so, all you can do is send a detailed crash report to Izotope, mentioning all steps to reproduce the crash in a DAW and tell them that it’s also reproducible with Pluginval. Trust me, this is a by far more detailed bug report then most users send in, so it could be really helpful to them But if your goal was to fix it on your own, I have to disappoint you, this won’t be possible for you without access to the source code
When I updated to Big Sur, some things broke. A couple of key plugins stopped working; and the first thing I did was look to see if there was anything I could do.
It functions great on Catalina, but Big Sur is where that variable changed. No I don’t work at Izotope, however when bringing this issue up they mentioned they discontinued support for this plugin so anything there is useless. I’m not versed in Pluginval, its features, or coding. Simply looking for insight on this issue to see what can be done [if anything]
Sorry to resurrect this old thread, but I have some similar issues with a plugin of mine that stopped working on Big Sur. The crash report also points to some native OS UI rendering calls, in my case it’s:
It also works fine on Catalina and previous versions. The weird thing is that on my M1 Macbook Air it also doesn’t crash, however I noticed that a Path that I’m drawing is completely garbled and the user that submitted the bug report could confirm that the crash appears as soon as the Path is supposed to be drawn.
@chrisboy2000 , we have received the same exact call stack from one of our users, which reported it because it crashes on his Big Sur (Intel).
In our case, this is coming from a fairly old plug-in, built with a very outdated version of JUCE, so in our case it’s kinda expected that some problems would arise sooner or later.
Unfortunately, upgrading that product for us would require a substantial effort, therefore I cannot immediately tell you if updating JUCE would solve the issue.
If your user is also getting the crash in a similar scenario (i.e. the product he’s runnign is built with an old JUCE), I think the first thing you could try is to update JUCE and see if that solves the issue