Stuck single-threaded loop on unavailable drive

Found a bug in "Everything"? report it here
Post Reply
arkos
Posts: 15
Joined: Mon Apr 13, 2020 8:03 am

Stuck single-threaded loop on unavailable drive

Post by arkos »

Steps to reproduce:
  • Add a separate, Bitlocker-encrypted drive under the "Indexes - Folders".
  • Make sure this volume does not unlock automatically.
  • Reboot with the Anything service running and volume locked.
  • Observe the bug.
Once the volume has been unlocked at least once, using

Code: Select all

manage-bde -lock -ForceDismount V:
does not result in the same loop or an increased CPU usage.
void
Developer
Posts: 17153
Joined: Fri Oct 16, 2009 11:31 pm

Re: Stuck single-threaded loop on unavailable drive

Post by void »

Thank you for the bug report arkos,

What version of Windows?
What version of Everything?

(I have not been able to reproduce the issue on Windows 10 22H2 with Everything 1.4.0.1023 or 1.5.0.1345a)



Could you please send a mini crash dump: Privacy
arkos
Posts: 15
Joined: Mon Apr 13, 2020 8:03 am

Re: Stuck single-threaded loop on unavailable drive

Post by arkos »

void wrote: Wed May 17, 2023 2:50 am Thank you for the bug report arkos,

What version of Windows?
What version of Everything?

(I have not been able to reproduce the issue on Windows 10 22H2 with Everything 1.4.0.1023 or 1.5.0.1345a)

Code: Select all

Everything v1.4.1.1023
Windows 21H2
I am, unfortunately, unable to provide a memory dump, however these two might help:
ev2.png
ev2.png (36.49 KiB) Viewed 5968 times
ev3.png
ev3.png (41.49 KiB) Viewed 5968 times
void
Developer
Posts: 17153
Joined: Fri Oct 16, 2009 11:31 pm

Re: Stuck single-threaded loop on unavailable drive

Post by void »

Thank you for the stack dump.
GetVolumeInformation
Everything will call this function when a new volume is available.

There is an issue with Windows and the global WM_DEVICECHANGE notification.
Calling GetVolumeInformation from this WM_DEVICECHANGE notification can cause more WM_DEVICECHANGE notifications to be sent.
You can probably confirm this from looking at the debug console output.

For Everything 1.4, please disable "Automatically include new volumes":
  • In Everything, from the Tools menu, click Options.
  • Click the NTFS tab on the left.
  • Uncheck Automatically include new fixed volumes.
  • Uncheck Automatically include new removable volumes.
  • Uncheck Automatically remove offline volumes.
  • Click OK.


The issue should be fixed in Everything 1.5.
Everything 1.5 will detect locked volumes and avoid accessing volume information from locked volumes.
Post Reply