APPCRASH 793b

Found a bug in "Everything"? report it here
Post Reply
therube
Posts: 4580
Joined: Thu Sep 03, 2009 6:48 pm

APPCRASH 793b

Post by therube »

Win7
793

Recent install of 793.
First I was checking out Renamer.
Then I went to cutting & moving some (hundreds at a time) files.

Noticed peculiarities when doing so.
Like it seemed after pasting, the cuts didn't "register" (as in the files were still showing in the particular Everything search when they should not have been).
Now that is not going to be irregular if any of the files cut have a name+path length >259, as it will just fail silently that way.
So then I checked for name+path >259 & that didn't seem to be the issue.
So then I selected a smaller selection of files to cut.
But that too didn't seem right.

Quit Everything & restarted (Everything).

Went back to try again, & then I realized that even though the files (previously) still showed in Everything, they did in fact cut.

So then I went about cutting some more, & that did work as expected.

Some time shortly thereafter, for no apparent reason, it crashed.

Code: Select all

==================================================
Event Time        : 11/05/2016 11:58:27 AM.000
Record ID         : 21586
Event ID          : 1000
Level             : Error
Channel           : Application
Provider          : Application Error
Description       : Faulting application name: Everything.exe, version: 1.4.1.793, time stamp: 0x581dd704
Faulting module name: Everything.exe, version: 1.4.1.793, time stamp: 0x581dd704
Exception code: 0xc0000005
Fault offset: 0x00085646
Faulting process id: 0xca0
Faulting application start time: 0x01d2377c21691ad6
Faulting application path: C:\DEV\Locate\Everything.exe
Faulting module path: C:\DEV\Locate\Everything.exe
Report Id: afe3603c-a370-11e6-9dbe-bc5ff444bb7d
Opcode            : 
Task              : Application Crashing Events (100)
Keywords          : Classic
Process ID        : 
Thread ID         : 
Computer          : RUBEN-W7-X64
User              : 
==================================================
void
Developer
Posts: 15096
Joined: Fri Oct 16, 2009 11:31 pm

Re: APPCRASH 793b

Post by void »

Fault offset: 0x00085646
Thanks for the crash report.

It's an issue with the new debug logger.

Could you please send me your %TEMP%\Everything Debug Log.txt
therube
Posts: 4580
Joined: Thu Sep 03, 2009 6:48 pm

Re: APPCRASH 793b

Post by therube »

Its like a Hillary email server, heavily redacted ;-).
Emailed & noted as "top secret".

Code: Select all

...
2016-11-05 14:49:53.233: WM_DRAWCLIPBOARD 0
2016-11-05 14:49:53.233: WM_DRAWCLIPBOARD 0
2016-11-05 14:49:53.233: WM_DRAWCLIPBOARD 0
2016-11-05 14:50:03.632: update m 1 92638960
therube
Posts: 4580
Joined: Thu Sep 03, 2009 6:48 pm

Re: APPCRASH 793b

Post by therube »

Perhaps unrelated, but I'll note it here...


After these crashes, Everything was taking a VERY long time (at least 1-minute) to update its .db, all the while using VERY high CPU (>50%).

After the X# time of that, I Quit Everything, deleted the .db, then started Everything.
Back to (relatively) minimal CPU & fast .db update.
void
Developer
Posts: 15096
Joined: Fri Oct 16, 2009 11:31 pm

Re: APPCRASH 793b

Post by void »

This is caused by Everything ending up in the clipboard chain with a circular link. (Everything's next clipboard window is pointing to itself).
This of course leads to a stack overflow and crash as you see.

I suspect this is caused by a third party program corrupting the clipboard chain, do you have any other programs running that might be monitoring the clipboard? It could also be Everything causing the corruption, it's just odd that I haven't seen it happen here..

I've added clipboard chain circular link protection to Everything 794b:
http://www.voidtools.com/Everything-1.4.1.794b.x86.zip
http://www.voidtools.com/Everything-1.4.1.794b.x64.zip
After these crashes, Everything was taking a VERY long time (at least 1-minute) to update its .db, all the while using VERY high CPU (>50%).
Most likely a lot of changes occurred before Everything last saved the database to disk. If it keeps happening, check the verbose debug output to see a list of file system changes causing the high cpu usage.
therube
Posts: 4580
Joined: Thu Sep 03, 2009 6:48 pm

Re: APPCRASH 793b

Post by therube »

do you have any other programs running that might be monitoring the clipboard?
I've been running CLCL is clipboard caching utility for about for ever.
therube
Posts: 4580
Joined: Thu Sep 03, 2009 6:48 pm

Re: APPCRASH 793b

Post by therube »

Looks to be much more robust.
void
Developer
Posts: 15096
Joined: Fri Oct 16, 2009 11:31 pm

Re: APPCRASH 793b

Post by void »

Thanks for the reply.

I haven't had any issues with CLCL, I'll just have to keep an eye on it for now.
Post Reply