Hacker News new | ask | show | jobs
by timvdalen 778 days ago
Hmm, the process segfaults right after, so I assumed this was the cause. Looking at the output again, I think there's another unrelated issue that happens at the same time, where Vulkan is unable to start due to ERROR_INCOMPATIBLE_DRIVER.

EDIT: Yes, I was missing a driver. I had a driver installed (amdvlk), but that apparently didn't work, and vulkan-radeon does.

1 comments

I was able to reproduce the segfault in a project with millions of files. It spat out a JSON blob saying something about

    Could not start watcher on parent directory: Error { kind: MaxFilesWatch, paths: <my path>
It works well for smaller projects though.