Access Violation crash when start after several runs I exited.

[ToolmakerSteve]

(EDIT: What the title of the post is trying to say, is that I had run MyDefrag several times before this. Each time, I exited after a few minutes. Was experimenting to see what affected display performance.)

Unfortunately log file says line unknown, but attaching it anyway.

Question: I note that it says "MyDefrag is already running" near the end of the log file, but I checked, and the previous one had exited .. or is that message an artifact of calling Settings.MyD within the main script?

(UPDATE: When I tried to run again after this crash, it ran without crashing.)

[ToolmakerSteve]

I just had a similar crash happen again. It also was Access Violation at unknown line.

But this time, I had NOT started MyDefrag again.

It is just that the crash message did not come up until maybe 30 seconds after I had exited MyDefrag (in the middle of a run).

So I think this is caused by the same problem that others have been reporting (it is related to exiting not to starting).

HYPOTHESIS: MyDefrag doesn't successfully shut down all its threads on exit.

[jeroen]

Thanks for testing and for posting the logfile! I see that you are using the "OtherInstances(ask)" setting in your Settings.MyD script. I have found a bug in that code and will see if I can fix it in the next release. For more information about stopping the program see I have stopped MyDefrag, but it remains running?

[jeroen]

I have just released MyDefrag v4.0b8. The problem should be solved now, could you test it for me please?