Powertoys Run Crash when searching for folder

[Cubevoid]

Microsoft PowerToys version

0.57.0

Running as admin

• Yes

Area(s) with issue?

PowerToys Run

Steps to reproduce

I was simply searching for a folder on my computer.

Log file:
2022-04-04.txt

✔️ Expected Behavior

The folder should show up in the search menu

❌ Actual Behavior

PowerToys Run crashes and opens multiple error windows telling me to report the bug

Other Software

No response

[htcfreek]

@Cubevoid

• Can you please tell us for which folder you have searched? This can help us on reproducing the issue.
• Can you please download and install to the newer .Net 6.0.3 form here. You have an older version installed.

@jaimecbernardo
It is the dispatcher crash. Might make sense that this plugin is the cause of this crash as we changed something in the plugin. (Unfortunately it didn't crashed on testing the changes for me.)

[2022-04-04 14:11:50.0099] [FATAL]
## Exception

System.InvalidOperationException: Dispatcher processing has been suspended, but messages are still being processed.
   Source: WindowsBase
   TargetAssembly: WindowsBase, Version=6.0.2.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
   TargetModule: WindowsBase.dll
   TargetSite: IntPtr WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

/needinfo

[Cubevoid]

@Cubevoid

• Can you please tell us for which folder you have searched? This can help us on reproducing the issue.
• Can you please download and install to the newer .Net 6.0.3 form here. You have an older version installed.

@jaimecbernardo
It is the dispatcher crash. Might make sense that this plugin is the cause of this crash as we changed something in the plugin. (Unfortunately it didn't crashed on testing the changes for me.)

[2022-04-04 14:11:50.0099] [FATAL]
## Exception

System.InvalidOperationException: Dispatcher processing has been suspended, but messages are still being processed.
   Source: WindowsBase
   TargetAssembly: WindowsBase, Version=6.0.2.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
   TargetModule: WindowsBase.dll
   TargetSite: IntPtr WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

/needinfo

My search query was "find CSC373" (I have the plugin bound to the "find" keyword).

The folder i was looking for was C:\Users\colin\Nextcloud\University\CSC373

I will install the new .Net version and let you know if I experience more crashing. This crash doesn't always happen for me either so it may be hard to reproduce unfortunately.

[htcfreek]

@Cubevoid
Are we talking about 'Windows Search' plugin or 'Folder' plugin?

[Cubevoid]

@Cubevoid Are we talking about 'Windows Search' plugin or 'Folder' plugin?

It's the 'Windows Search' plugin.

[jaimecbernardo]

It's pretty weird that this error resurfaced with 0.57.0, where I don't think we went anywhere near those plugins.
@htcfreek , might this occur on some machines when PTRun takes a bit longer to update the thread? I think the address results from Settings might have this fixed for 0.57.1, but let's see. We have no useful information regarding this bug at this moment.

[htcfreek]

@htcfreek , might this occur on some machines when PTRun takes a bit longer to update the thread? I think the address results from Settings might have this fixed for 0.57.1, but let's see. We have no useful information regarding this bug at this moment.

Don't know. But sounds logical.

[jaimecbernardo]

/dup #17371

Could you please try these instructions in 0.57.2 and post results in that issue?
#17371 (comment)

[ghost]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!