Closed stefanos82 closed 2 years ago
Seems like you don't even need to open it with the keyboard shortcut, opening it through the start menu also works.
Seems like you don't even need to open it with the keyboard shortcut, opening it through the start menu also works.
The discussion I started in Discord was about existing hotkeys found in SerenityOS so I could use Assistant without depending on start menu to open it; thus the bug discovery by accident.
I phrased my comment badly; what I meant was that the crash seems to happen regardless of how you opened Assistant.
I phrased my comment badly; what I meant was that the crash seems to happen regardless of how you opened Assistant.
Ah that's good to know.
After investigating a bit, I think what's happening here is that the background job in FileProvider::build_filesystem_cache()
is still running after the main thread has exited and tries to access the main thread's freed memory. I don't know how to fix that, though.
Thanks to @AtkinsSJ that taught me
Ctrl+Space
Win+Space
to start Assistant, I managed to crash it with a simple step: Open Assistant with the aforementioned hotkeys and don't type anything in it; just left-click on desktop surface with your mouse and you get it crashed immediately.