New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Animation feature causes an internal error in uiautomationcore.dll #116
Comments
Also, I use ExplorerBlurMica and TaskbarX if that matters somehow. |
So can you run the test again with TaskbarX stopped? |
I cannot seem to reproduce the error now. Just right-clicking a few times and hovering over items in the menu would crash the explorer. I stopped TaskbarX and restarted it. But now it seems fine somehow. |
I believe this is an internal issue with UIAutomationCore.dll as the issue has been mentioned by many people. When it tries to read any UI element, if a window is created at that point, then there is a high probability that it will crash. This is because with EnableFluentAnimation enabled TF needs to create an additional window to display the animation, which is exactly the situation described above. And TaskbarX indirectly calls the function in UIAutomationCore.dll through MSAA. The solution for now is to disable the animation, so that basically there will be no crash. |
Sometimes explorer.exe doesn't even create a minidump and just crashes when I use the context menu |
I got you few dump files, if it helps. You already know the uiautomationcore.dll error, but there is an oleacc.dll error now. I got the uiautomationcore.dll error at first and kept getting the oleacc.dll error multiple times after that. oleacc.dll_causing_error.dmp TF v3.1.0 |
They are actually the same error, as they all show uiautomationcore.dll near the call stack, except that the oleacc.dll error comes from uiautomationcore.dll passing it a null pointer. These dump files are the same error described in the dump file you uploaded earlier. Do you get this problem even if you disable |
Disabling Edit: I'm also using Rainmeter, if that matters. |
Oh, I thought explorer was still crashing even though you had I will try to fix this issue, but this is more like something Microsoft should do. |
Got it |
Good news, I have managed to find a way to mitigate this issue, please wait for the next update. |
Fixed. |
Explorer crashes regardless of whether it is being shown or not, i.e. The explore might be in use by the user or it might not even be open. Using the context menu somehow crashes it.
OS: Win10 v19045.4123
Dump Files:
Explorer.EXE-minidump-2024-03-13-17-02-50.dmp
explorer.exe-minidump-2024-03-13-17-06-16.dmp
The text was updated successfully, but these errors were encountered: