"Windows: Reload" command crashes editor

[GrishaKirilin]

Thanks in advance for your bug report!

• Have you reproduced issue in safe mode?
• Have you used the debugging guide to try to resolve the issue?
• Have you checked our FAQs to make sure your question isn't answered there?
• Have you checked to make sure your issue does not already exist?
• Have you checked you are on the latest release of Pulsar?

What happened?

Starting with Pulsar 1.131.0 (upgraded to Electron 30), the "Windows: Reload" crashes the editor almost every time. I have disabled all community packages, or launched the editor with pulsar --safe, yet the problem persists. I checked that it is not related to this issue, it still happens without any git repository.

Pulsar version

1.132.1

Which OS does this happen on?

🐧 Debian based (Linux Mint, Ubuntu, etc.)

OS details

Ubuntu 22.04.5 LTS x86_64

Which CPU architecture are you running this on?

x86_64/AMD64

What steps are needed to reproduce this?

1. Open editor.
2. Reload window.

reload_window.mp4

Additional Information:

No response

[Daeraxa]

I tried to replicate this but couldn't (Fedora 43, Pulsar 1.132.0).

One thing to maybe have a look at is at ~/.pulsar/nohup.out to see if it has anything recorded in there.

Or if not then one thing you could try is to start the binary directly (normally running pulsar in the shell executes a script that runs Pulsar). It should be at /opt/Pulsar/pulsar but you can check the pulsar.sh script that should be located in usr/bin to see what exactly it is executing. That way we can see if anything gets printed to the terminal when it crashes.

[GrishaKirilin]

I checked ~/.pulsar/nohup.out, and after Windows reloaded, it contained the following:

Starting crash reporter; crash reports will be saved to /home/grisha/.pulsar/crashdumps
[0603/091953.566952:ERROR:elf_dynamic_array_reader.h(64)] tag not found

It is obviously related to the error message I posted in another issue: a non-caught std::logic_error exception.

[savetheclocktower]

@GrishaKirilin, if you do have any crashdumps in your ~/.pulsar/crashdumps folder, place compress the .dmp into a .zip and attach it to this issue for analysis.