Autodesk-Fusion-360-for-Linux: Fusion 360 is unusable and I get a lot of QtWebEngineProcess.exe errors *solved*
Describe the bug
After login/launching Fusion 360 I get a lot of errors saying: The program QtWebEngineProcess.exe has encountered a serious problem and needs to close. After closing all the errors, I can see the UI but several parts of the UI are missing and/or black. This is after a fresh installation using the script.
To Reproduce Steps to reproduce the behavior:
- Do a fresh install using the install.sh script.
- Select DMVK option.
- Leave all other defaults.
- Launch app after installing
- login. (During login the same error will popup but it will allow to continue with login)
Expected behavior Fusion 360 loads normally.
Screenshots
Desktop (please complete the following information):
- Fusion 360 Version: Can’t verify as the GUI is not responsive. But is the one installed as of 25-05-2024.
- GPU & Driver: AMD RX 6950 XT. mesa, xf86-video-amdgpu, vulkan-radeon, amdvlk, vulkan-amdgpu-pro, libva-vdpau-driver, mesa-vdpau, libva-mesa-driver, lib32-mesa, lib32-vulkan-radeon, lib32-amdvlk, lib32-vulkan-amdgpu-pro, lib32-libva-mesa-driver, lib32-mesa-vdpau
- Operating system: Arch Linux
- Desktop environment: KDE Plasma 6.0.4-2 on Wayland
- DXVK or OpenGL Mode: DXVK
Additional context I use Polonium Kwin script for auto tiling, not sure if that could be related. Also, I’m using the zen kernel 6.9.1-zen1-2-zen
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 3
- Comments: 36 (2 by maintainers)
Using Fusion v2.0.19426 for analysis, the INT3 being hit is in Qt6WebEngineCore.dll offset 0x3d81e31:
In summary, this function is using
VirtualProtectto set page protection on a region to 0x02 (PAGE_READONLY).VirtualProtectitself succeeds (nonzero return), since we do perform the JNZ here. Then, the CMP checkslpflOldProtectto see ifVirtualProtectindicated that the region previously had protection 0x04 (PAGE_READWRITE), which it apparently didn’t. The JZ does not jump and we break on the following INT3.Patching that INT3 to a NOP results in Fusion running successfully (patched Qt6WebEngineCore.dll here, which you can just drop in on your own install if you want to see it fully working).
This function is called in just one place for exactly one 4K page. I haven’t had time yet to go through the details of Qt WebEngine to find exactly what it’s doing with that one page, but this procedure didn’t exist in
Qt6WebEngineCore.dllfrom previous Fusion versions. (In previous versions, allVirtualProtectcalls do not check the previous protection value.)Obviously, the next step would be to check what the previous protection actually was (and why it’s “wrong” in Wine).
Yeah, this is not just your system. It’s a new general problem (I see it too, so I’m still running 2.0.18961 - the last good version.)
So far, 2024 has been a very tiring year for Fusion on Linux, with almost every update catastrophically breaking the application albeit with a relatively “easy” fix/workaround once the problem is debugged.
If Autodesk could get one of their many employees to spend just one day testing each release on Wine, they might be able to easily find and quickly address these sorts of things (with their huge knowledge of Fusion’s internals compared to ours). For them this could be a very large user-base return on a small time investment.
Fusion is an example of an application where there are no remaining technical roadblocks to good reliability under Wine - the only roadblock is the organizational one of convincing someone at Autodesk to just keep it in the back of their mind as a platform to test on. It doesn’t need to be officially-supported in writing.
This fix can also be applied by changing
0x3D81231from0xCCto0x90inQt6WebEngineCore.dll. Has worked great so far for me. No more crash popupsYou said you are using virtual desktop
What you can do as a hacky workaround is make the virtual desktop fullscreen (change the resolution to match your screen’s) then open fusion and leave some space around it. After that, the explorer/browser if you clicked should just be behind the window since it becomes uncoupled for some odd reason. Just place it in the space you reserved in the virtual desktop. For most other popups all you have to do is move them to some reserved space and now everytime fusion opens that popup will just appear on that reserved space.
The automated script patch did not seem to work for me. Manually replacing the .dll file with the one from here did. I’m guessing the library was updated as I ran the installation script today from a clean system.
Not sure if relevant but this is what the Program Error has: