PB x86 on Win 8.1 - driving me crazy

[Thunder93]

Tested out your new version but with the two disabled lines re-enabled. w/PB 5.22 LTS (x86) running on Win7 x64 and testing with or without the PB Debugger, it causes crash. Running test with Debugger and Purifier enabled, seems very difficult to produce a crash. However, I'm only giving it a limit period of time to produce.

[Thunder93]

Seems the combo of the two is required, not one or the other to reproduce.

[said]

Tested out your new version but with the two disabled lines re-enabled. w/PB 5.22 LTS (x86) running on Win7 x64 and testing with or without the PB Debugger, it causes crash. Running test with Debugger and Purifier enabled, seems very difficult to produce a crash. However, I'm only giving it a limit period of time to produce.

on win 7 as well !

Thank you Thunder93, yup i have just done some test, you are right it is crashing on win7 x64 too .... getting more fun i had never any issue with original application on win7 that's why i didnt bother to check properly on 7

Seems the combo of the two is required, not one or the other to reproduce.

yes, same here


Edit: I have re-done the tests on win7 x64, it is crashing when reaching ~ 2GB memory which normal for a 32 process! Isn't the same happening at your end ?
Whether from the IDE or the exe it crashes when reaching approx 2GB, we can expect more from wow64! I changed the title back to win 8.1 ...

[Thunder93]

I would never see app crashes as normal. There should be safe-guards in-place, or this to be documented.

Like you've observed, ... crashes when reaching approx. 2GB.

Now I see why it didn't happen with the use of Purifier mode.. Like I said previously, only giving it a certain limit of time but with Purifier enabled you have to let it go a long while before It'll reach approx. 2GB.

[Danilo]

I would never see app crashes as normal. There should be safe-guards in-place, or this to be documented.

Like you've observed, ... crashes when reaching approx. 2GB.

What happens if you check all pointers for 0 before accessing them, and also check
return values of commands like AddElement, SelectElement, InsertElement, LastElement, etc.?

[Thunder93]

The error-line points to the following

• Code: Select all

  AddElement(*H\lstTCs())

The pointer is returning non-zero before last AddElement() process. I ran out of ideas, perhaps there's something that could be done by a user-check?