-
Notifications
You must be signed in to change notification settings - Fork 988
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
Lapce crashes on startup (Windows 11) #3114
Comments
Same issue on windows 10 64-bit |
Seems to be fixed. I still get the white rectangle for like a second, but Lapce opens afterwards. I recently had to reinstall graphics drivers, so that might've been the issue. Latest nightly (nightly-39ef70d) works fine as well. Will leave the issue open for now since somebody else seems to have the same issue in the comments. |
The issue is back, but I still think it might be a driver issue. Also, just found out that I need to run Lapce with "-w" if I want to keep in running in the terminal. Therefore, the previous log is not correct. A relevant portion of the new log is:
@SeleDreams would you be willing to post a log to see if we're having similar issues? Since you're using NVIDIA, it won't be an amdvlk64.dll problem, but it might help devs figure this out. Thanks! |
In my case, it can be fixed by setting WGPU_BACKEND= |
I get this:
GPU: Intel HD4400 |
Could you post the backtrace? Or if you have a gdb log could you post the relevant portion? Also please try the different WGPU_BACKEND options to see if it's actually a Vulkan issue. If not you might need to create a separate issue. |
GDB output says nothing useful, please don't post it as it only clutters the issue |
I see. At least in my case it helped me identify it as a Vulkan problem. Thanks for the input! |
Lapce Version
v0.3.1
System information
Windows 11
AMD GPU, Adrenaline v24.3.1
Describe the bug
Application crashes during startup. A white rectangle shows up for a few seconds, then closes without any errors.
Additional information
Also tried with latest nightly, same issue. Attached GBD and didn't get any helpful information.
GDB log:
Screenshot of behavior (White rectangle on top left of screen):
The text was updated successfully, but these errors were encountered: