Were you doing something special or did this happen out of the blue? I found the line of code that must have caused it but it doesn't make much sense to me yet. It would be way more logical if you had just switched between compressor modes for example. (But then you wouldn't have noticed the hiccup).
Only thing changed in this session is to turn on Immersive base, then about an hour later relocate it from before AGC to after AGC. It was running this way for about 30mins, popped up, I grabbed a copy of it to send to you and then acknowledged it.
O, and has this ever happened before/how long was it running, has it happened since. I'm trying to figure out if this is something that's new in this build (which is unlikely because I haven't touched the compressor code in quite a while) or something that happens very very occasionally and might have been there for a long time already.
First time I have seen it. Here are the last couple of lines of the logfile -:
EXCEPTION OCCURRED IN release_ss: ss_inuse[index]
EXCEPTION OCCURRED IN ProcessingChain Thread (Exception 0xc0000005 at address 0x7ff60b8554da, read/write=1, r/w location=0x7a80). Offset-info: 0x7ff60bdcd809
EXCEPTION OCCURRED IN release_ss: index >= 0 && ss[index] == s
EXCEPTION OCCURRED IN ProcessingChain Thread (Exception 0xc0000005 at address 0x7ff76ce6492e, read/write=0, r/w location=0x0). Offset-info: 0x7ff76fbba2b9
The first one I have multiple entries for before that one (same offset, different address) but I do not know how old these are...
EXCEPTION OCCURRED IN ProcessingChain Thread (Exception 0xc0000005 at address 0x7ff60b8554da, read/write=1, r/w location=0x8780). Offset-info: 0x7ff60bdcd809
Could we add a date/time stamp to the log file entries perhaps?