Randomly access violation

[bodrusG]

Hi , sometimes when moving objects on the form this error occurs and you have to kill Twinbasic to exit.
Unfortunately I am unable to replicate the behavior which seems random

tb261

[WaynePhillipsEA]

When this next happens, could you check the task manager and see if the twinbasic_win32.exe has reached near the 2GB memory usage (it will usually show about 1.7GB in task manager before failures occur).

[bodrusG]

hi this is a screenshot of taskmanager ,
besides twinbasic only vlc was active playing an mp3

[WaynePhillipsEA]

Thanks, that confirms it is not a memory issue.

Unfortunately, until we can get steps to reproduce the issue, this will be difficult to solve. If you find any pattern to the problem/behaviour, please do let us know.

[bodrusG]

I realize the difficulty, the last time it happened I was doing the resizing of a frame inside another frame, but other times also while writing the code and parsing to attribute the colors. It seems as if the memory slowly fills up until the next operation whatever it is causes the error, but it is clear that mine is only a guess

[bodrusG]

now it happened while the intellisense was listing the members of a udt variable

[WaynePhillipsEA]

I think the auto-restart-on-crash feature may be broken in the latest builds. I will be looking at this tomorrow.

[bodrusG]

who better than you can get the right idea :-)

[WaynePhillipsEA]

The most important part of the problem here is that the compiler should be restarting gracefully automatically when the crash occurs, and this was happening until recent changes (since BETA 259). This should now be fixed in BETA 263.

Please let me know if this resolves the issue for you.

[bodrusG]

ok ,thanks.. i 'll try

[bodrusG]

i think it work .. the error of access violation fire again but the compiler restart correctly

[WaynePhillipsEA]

Thanks for confirming. I'll close this then, as the graceful restart is the most important part for now. Thanks!