Skip to content
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

Open
lpaulino07 opened this issue Mar 26, 2024 · 9 comments
Open

Lapce crashes on startup (Windows 11) #3114

lpaulino07 opened this issue Mar 26, 2024 · 9 comments
Labels
C-bug Category: bug - something isn't working as it's supposed to

Comments

@lpaulino07
Copy link

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:

Starting program: C:\Program Files\Lapce\lapce.exe
[New Thread 12816.0x5540]
[New Thread 12816.0x59c8]
[New Thread 12816.0x2d40]
[New Thread 12816.0x538]
[Thread 12816.0x538 exited with code 0]
[Thread 12816.0x2d40 exited with code 0]
[Thread 12816.0x59c8 exited with code 0]
[Thread 12816.0x5540 exited with code 0]
[Inferior 1 (process 12816) exited normally]

Screenshot of behavior (White rectangle on top left of screen):
image

@lpaulino07 lpaulino07 added the C-bug Category: bug - something isn't working as it's supposed to label Mar 26, 2024
@SeleDreams
Copy link

Same issue on windows 10 64-bit
i3 3217u
nvidia gt720m

@lpaulino07
Copy link
Author

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.

@lpaulino07
Copy link
Author

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:

Thread 108 received signal SIGSEGV, Segmentation fault.
0x00007ffa38a25dcc in vk_icdGetInstanceProcAddrSG ()
   from C:\Windows\System32\DriverStore\FileRepository\u0401413.inf_amd64_997830838cb299a9\B401180\amdvlk64.dll

@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!

@lpaulino07
Copy link
Author

In my case, it can be fixed by setting WGPU_BACKEND=dx12 or gl, so it's definitely a Vulkan issue. Unless SeleDreams's crash is also Vulkan related, I will close this issue.

@asik
Copy link

asik commented Apr 5, 2024

I get this:

2024-04-05T02:57:06.441305Z ERROR lapce_app::keypress: Failed to load from "C:\\Users\\******\\AppData\\Roaming\\lapce\\Lapce-Stable\\config\\keymaps.toml": no keymaps
2024-04-05T02:57:09.654119Z ERROR wgpu_hal::auxil::dxgi::result: Buffer creation failed: 0x887A0005
2024-04-05T02:57:09.654363Z ERROR wgpu::backend::direct: Handling wgpu errors as fatal by default
thread 'main' panicked at C:\Users\runneradmin\.cargo\registry\src\index.crates.io-6f17d22bba15001f\wgpu-0.18.0\src\backend\direct.rs:3111:5:
wgpu error: Validation Error

Caused by:
    In Queue::write_buffer
    Parent device is lost


note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

GPU: Intel HD4400

@lpaulino07
Copy link
Author

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.

@panekj
Copy link
Collaborator

panekj commented Apr 5, 2024

Or if you have a gdb log could you post the relevant portion?

GDB output says nothing useful, please don't post it as it only clutters the issue

@panekj
Copy link
Collaborator

panekj commented Apr 5, 2024

@asik your issue is #2809

@lpaulino07
Copy link
Author

lpaulino07 commented Apr 5, 2024

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: bug - something isn't working as it's supposed to
Projects
None yet
Development

No branches or pull requests

4 participants