Access violation using DebugMode.dat in v.1.8.0.455

tullik

Access violation using DebugMode.dat in v.1.8.0.455

I tried turning on Debug mode with DebugMode.dat becacause of this post by jepe .

It produced the empty main window phenomenon, but also looped, filling the message box with a continuous stream of access violation messages. I had to terminate PT2008 to stop it. The jv16PT_Debuglog.txt (zipped) is attached. It shows once the first access violation message below. Then, a few lines down, it has the continuously produced second access violation message shown below.

Edit: this is repeatable (same thing the two times I did it).

*** Exception *** Access violation at address 00570DC1 in module 'jv16PT.exe'. Read of address 00000160

*** Exception *** Access violation at address 645C717E. Read of address 645C717E

In case anyone is wondering, turning on Debug mode with the "Ctrl/Shift" procedure worked with no problems.

Access violation debug log.zip

jepe

Hello,

tullik wrote
In case anyone is wondering, turning on Debug mode with the "Ctrl/Shift" procedure worked with no problems.

I started the Debug mode with Ctrl/Shift and got so this blue window. The first time the message box gave me just the normal messages: .... started in Debug mode ... and ... all tests passed ... !

I closed PT by killing the process jv16PT.exe by Process Explorer.

I started a second time - same blue window, but this time PT went in an neverending loop with the following message:

*** Exception *** Access violation at address E8EDE5ED. Read of address E8EDE5ED

Process Explorer indicated me constant CPU activity of jv16PT.exe from more than 90% - with peaks over 98 %.

Even just now a did some more runs and there I got, after 3 times "blue window" 2 normal main windows and then again 1 "blue window". The error message, at "blue window" start, is allways the same, as above.

I hope Jouni could catch this "phenomenon" soon.

Good night

Jean-Paul