Stack-overflow crash in 1.5.0.1361a

Discussion related to "Everything" 1.5 Alpha.
Post Reply
Spire
Posts: 7
Joined: Thu Dec 15, 2022 1:25 am

Stack-overflow crash in 1.5.0.1361a

Post by Spire »

I've been getting frequent stack-overflow crashes (multiple times a day) in Everything version 1.5.0.1361a (x64). They seem to happen when an Everything window has been sitting idle in the background for some unpredictable amount of time.

This morning I decided to run Everything in a debugger (WinDbg) to catch the crash. Not too long afterwards, I caught it!

At the time of the crash, this was the last line in the Everything verbose debug log:

Code: Select all

2023-12-02 07:47:59.682: COM msg 1030
And these were the last few lines of the WinDbg log:

Code: Select all

Sat Dec  2 07:47:38.299 2023 (UTC - 8:00): onecoreuap\base\appmodel\search\querydll\ifilt\regacc.cxx(93) ERROR : [Index] RtlQueryRegistryValues (...\\Registry\Machine\Software\Classes\.pdf\PersistentHandler  ) returned 0xc0000034
Sat Dec  2 07:47:38.300 2023 (UTC - 8:00): (d1c8.15d84): C++ EH exception - code e06d7363 (first chance)
Sat Dec  2 07:47:38.302 2023 (UTC - 8:00): onecoreuap\base\appmodel\search\querydll\ifilt\regacc.cxx(93) ERROR : [Index] RtlQueryRegistryValues (...\\Registry\Machine\Software\Classes\CLSID\{B801CA65-A1FC-11D0-85AD-444553540000}\PersistentHandler  ) returned 0xc0000034
Sat Dec  2 07:47:38.304 2023 (UTC - 8:00): (d1c8.15d84): C++ EH exception - code e06d7363 (first chance)
Sat Dec  2 07:47:59.969 2023 (UTC - 8:00): (d1c8.1cce0): Stack overflow - code c00000fd (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
ntdll!RtlpAllocateHeap+0x31:
I've also attached the stack trace — it's over 6,768 levels deep!

Please let me know if there's anything else I can do to help track this down.
Attachments
Stack trace.zip
(47.18 KiB) Downloaded 40 times
void
Developer
Posts: 16735
Joined: Fri Oct 16, 2009 11:31 pm

Re: Stack-overflow crash in 1.5.0.1361a

Post by void »

This stack-overflow crash is caused by the COM (Windows_Media) outside of Everything.

It may have been triggered by Everything from reading a property from a file.

What properties are you indexing under Tools -> Options -> Properties?
What columns are visible in Everything?
Did you notice this crash occur in other versions -or only in 1361a?



I wonder if there's a particular file triggering the crash when gathering a property..
Spire
Posts: 7
Joined: Thu Dec 15, 2022 1:25 am

Re: Stack-overflow crash in 1.5.0.1361a

Post by Spire »

void wrote: Sun Dec 03, 2023 1:20 am What properties are you indexing under Tools -> Options -> Properties?
Album, Album Artist, Artist, Authors, Composer, Hard Link Count, Title, Total Alternative Data Stream Size, Year.

Most of the above are indexing lists of specific file types.
void wrote: Sun Dec 03, 2023 1:20 am What columns are visible in Everything?
Name, Extension, Path, Type, Size, Allocation Size, Total Alternative Data Stream Size, Run Count, Date Created, Date Modified, Hard Link Count.
void wrote: Sun Dec 03, 2023 1:20 am Did you notice this crash occur in other versions -or only in 1361a?
I think I first noticed it in 1358a, but I'm not 100% sure.
void wrote: Sun Dec 03, 2023 1:20 am I wonder if there's a particular file triggering the crash when gathering a property..
Is there an easy way for me to determine that within Everything? The verbose log doesn't show anything of interest.

Or would you like me to use something like Process Monitor to log all of the files Everything is opening? Would probably be very slow.
void
Developer
Posts: 16735
Joined: Fri Oct 16, 2009 11:31 pm

Re: Stack-overflow crash in 1.5.0.1361a

Post by void »

Please try disabling the Windows Property System to see if the issue is caused by a shell extension:
  • In Everything 1.5, from the Tools menu, click Options.
  • Click the Advanced tab on the left.
  • To the right of Show settings containing, search for:
    system
  • Select property_system.
  • Set the value to: false
  • Click OK.
Does this prevent the crash?



Everything will gather property values with the Windows property system first, if that fails Everything will fall back to a built-in property handler.
Please check if Everything is still correctly loading properties for recent files.



If a shell extension is causing the crash, there's very little I can do.
You might be able to locate the problem file or extension causing the crash.

Property shell extensions can be toggled with ShellExView.
Post Reply