Page 1 of 1
Crash in 5.00.0016 when nuking
Posted: 07 Jun 2006 08:34
by pissant
I'm running 5.00.0016 on WinXP Pro SP2. It very often happens that when I select a file (or more than one file) and hit the Nuke toolbar button, XYplorer crashes, if the file(s) are locked by some other process.
I'm not sure what else to say. The crash doesn't happen each and every time I try nuking a locked file, but it happens at least 1 out of every 4 times. I just made a video of the crash occurring--it took a few tries, but it did happen (this is an XviD-encoded file):
http://snipurl.com/nukeme
Re: Crash in 5.00.0016 when nuking
Posted: 07 Jun 2006 09:32
by admin
Are you sure this is specific to nuking (and does not happen with recycling as well)?
EDIT: I tried hard but could not reproduce it.

I even added your 5 separators...

Posted: 07 Jun 2006 16:19
by pissant
It does seem to be strictly nuking related. I normally only ever use the nuke function (mainly because the damned delete function makes my secondary hard drive come out of sleep mode, regardless of where the file being deleted resides).
Just now, though, I could not reproduce the crash using the Delete key, nor with Shift+Delete. And after Delete and Shift+Delete failed to make XYplorer crash after several tries, doing a nuke one time would typically make it crash right away.
I do have the Recycle Bin disabled. I also use
Undelete, but I don't see why that would matter.
Posted: 07 Jun 2006 22:19
by admin
pissant wrote:I do have the Recycle Bin disabled. I also use
Undelete, but I don't see why that would matter.
Well, who knows? I'm using standard shell functions for all of these delete operations including Nuke. If you, me or anybody doesn't find a reliable way to reproduce the crash it is hard to debug.
Posted: 10 Jun 2006 01:53
by pissant
Unless you have changed something in the last build or two that may have fixed this issue, I think the problem may have, after all, been related to Undelete. I say this because I just uninstalled Undelete, and now, running 5.00.0019, can't seem to reproduce this crash.
Sorry for (so far as it seems) a fallacious bug report.
But, technically, I
did have a reliable way to reproduce it...

Posted: 10 Jun 2006 07:05
by admin
Didn't change a bit...