Our QA is reporting an occasional case where, when loading a session with our plug-in instantiated and open in it, the plug-in comes up as de-activated. Doesn’t happen all the time, or even often, but sometimes it just happens, with no error window or anything. Any idea what might cause this? My only guess was that something (copy protection?) was taking too long to respond while instantiating. Not a major issue, but it does make me wonder if there is something in our code causing this…?
Does this only happen for specific plugin formats, hosts, operating systems, etc? If so, it would be helpful to know which ones are affected.
Are you able to attach a debugger while loading the project or add some logging output with timestamps? That might help you find out whether the plugin is being correctly loaded in the first place, and whether any parts of the initialisation are taking a suspiciously long time.
Oh, sorry, forget to mention this was in Pro Tools only.
1 Like
Debugging doesn’t work because you can’t save from a Developer build and can’t debug from a non-Developer build. 
Use FileLogger
Rail
I haven’t been able to replicate the problem myself. Maybe their iLok was taking too long, or perhaps they had a cloud-based license and the internet outage caused this? Gonna de-prioritize this, but might send Avid a direct query as to what might cause this.