Ok, I know this is an old thread, but thought it might help someone if I come back on this issue!
I have found since then, one of the cause of the issue. For us, it was the "html tips"! Since I think version 13, the default parameter for 'TC' was changed, so that it automatically shows tips as html. I=On our main menu, we had a bunch of small buttons that had a decription containing the symbol "<" which was detected as html markup. SO, everytime we would mouse over, it would open a chromium object and at some point, would generate a "memory access violation". I'm not sure if this was resolved in the latest version or not though. We are still only running version 19...
I must say, that error came back recently and not sure the cause yet. I'm suspecting the use of an "animated gif" for a loader. That is the only recent change we did that would explain this. I have removed that gif in most programs and the error is less frequent since.
I have found since then, one of the cause of the issue. For us, it was the "html tips"! Since I think version 13, the default parameter for 'TC' was changed, so that it automatically shows tips as html. I=On our main menu, we had a bunch of small buttons that had a decription containing the symbol "<" which was detected as html markup. SO, everytime we would mouse over, it would open a chromium object and at some point, would generate a "memory access violation". I'm not sure if this was resolved in the latest version or not though. We are still only running version 19...
I must say, that error came back recently and not sure the cause yet. I'm suspecting the use of an "animated gif" for a loader. That is the only recent change we did that would explain this. I have removed that gif in most programs and the error is less frequent since.