Random suspend with FileMenu Tools?

Discussion related to "Everything" 1.5 Alpha.
Post Reply
NottMee
Posts: 19
Joined: Tue Jun 27, 2023 6:43 pm

Random suspend with FileMenu Tools?

Post by NottMee »

Before some while I have posted a thread about random suspend:
viewtopic.php?p=58578
Now I've found out this may be some bug related to FileMenu Tools.

Sometimes the items of FileMenu Tools in Everything will turn black(see the pic below), and if I delete something at this time, the Everything programm will suspend. I must restart it manually, but this bug comes out again after every 10-15 minutes. Strangely, this bug never happens in Windows Explorer.
Snipaste_230906-153122.png
Snipaste_230906-153122.png (5.06 KiB) Viewed 1027 times
I'm using the latest version (8.2) of FileMenu Tools, together with Everything 1.5.0.1355 on Windows 11 22H2.
Here is the debug info when the suspend happened, don't know if it can help :cry:

Code: Select all

processed 2 usn records in 0.000083 seconds
DB_WAIT: _db_journal_notification_event_proc waited 0.003237 seconds
update m 1 0000000016b81400
update index D:
USN DATA_TRUNCATION history_traffic.dat
USN DATA_EXTEND DATA_TRUNCATION history_traffic.dat
USN CLOSE DATA_EXTEND DATA_TRUNCATION history_traffic.dat
read usn journal D: in 0.000998 seconds
updated D: in 0.000223 seconds
resume ntfs monitor 1
DB_WAIT: _db_journal_notification_event_proc waiting for _db_monitor_ntfs_process_fd_update_events_thread_proc...
processed 2 usn records in 0.000142 seconds
DB_WAIT: _db_journal_notification_event_proc waited 0.014213 seconds
update m 0 0000000016b802d0
update index C:
USN DATA_OVERWRITE UsrClass.dat.LOG2
read usn journal C: in 0.001143 seconds
updated C: in 0.000147 seconds
resume ntfs monitor 0
processed 1 usn records in 0.000044 seconds
DB_WAIT: _db_monitor_finished_process_fd_update_events_event_proc waiting for _db_monitor_ntfs_process_fd_update_events_thread_proc...
DB_WAIT: _db_monitor_finished_process_fd_update_events_event_proc waited 0.001651 seconds
update m 0 0000000016b802d0
update index C:
USN DATA_EXTEND MM_20230906.xlog
USN CLOSE DATA_EXTEND MM_20230906.xlog
read usn journal C: in 0.003594 seconds
updated C: in 0.000176 seconds
resume ntfs monitor 0
DB_WAIT: _db_journal_notification_event_proc waiting for _db_monitor_ntfs_process_fd_update_events_thread_proc...
processed 1 usn records in 0.000099 seconds
DB_WAIT: _db_journal_notification_event_proc waited 0.006233 seconds
update m 0 0000000016b802d0
update m 1 0000000016b81400
I've send a email to the developer of FileMenu Tools, but got no answer. Can you please also check the bug and try to fix it? If you need further help such as dump files, I'm willing to do it.
This bug bothers me a lot but I really can't give up any of the two softwares, both have been many years with me. Thanks.
therube
Posts: 4985
Joined: Thu Sep 03, 2009 6:48 pm

Re: Random suspend with FileMenu Tools?

Post by therube »

[filemenu tools] Blank context entry.

[suspend] Winmerge Modal Dialog Holds "Thread" Open.

Now, perhaps neither or one or the other or both may have some relevance (or not ;-)).
harryray2
Posts: 1104
Joined: Sat Oct 15, 2016 9:56 am

Re: Random suspend with FileMenu Tools?

Post by harryray2 »

I also have a problem with filemenutools on the context menu in the sidebar of Everything.. On the context menu it just shows as a series of blank spaces.
Void is looking into the problem.

I like filemenutools but it can be unstable at times.
NottMee
Posts: 19
Joined: Tue Jun 27, 2023 6:43 pm

Re: Random suspend with FileMenu Tools?

Post by NottMee »

harryray2 wrote: Wed Sep 06, 2023 6:34 pm I also have a problem with filemenutools on the context menu in the sidebar of Everything.. On the context menu it just shows as a series of blank spaces.
Void is looking into the problem.

I like filemenutools but it can be unstable at times.
Just an update for you and others who may need it:

Recently, Everything suspends more and more often because of the bug of FileMenu Tools, and I've finally had enough of the constant restarting.

After several attempts (which took me a lot of time...), I found the ultimate solution: uninstall the new version of FileMenu Tools and install version 8.0.2. The bug seems to have appeared from 8.0.3 onwards.

By the way, it's quite disappointing that I contacted the developer of FileMenu Tools (I believe he's alone, not a team), but his response was rather rude. Instead of addressing the bug, they simply asked me: "Since this bug never occurs in Explorer, why do you think it's a bug related to FileMenu Tools and not Everything?" I'm kind of regretting purchasing the software license...
Post Reply