Pulsar crashes after syncing to 100%

Issue Report

I finally managed to sync the full chain. Howver, Pulsar crashes as it tries to move to the next step (plotting?). I have seen this happen with both the Legacy and Skylake+ versions (running AMD Ryzen 5 3600, so not sure which version I should be using).


  • Operating System:
    Windows 10 Pro, 22H2 (19045.3930)
    running Pulsar from boot drive (NVMe) via Command Prompt, attempting to plot to SATA SSD S:\
  • Pulsar/Advanced CLI/Docker:
    Pulsar 0.7.2-alpha


Starting farmer …
Farmer started successfully!
The application panicked (crashed).
Message: A Tokio 1.x context was found, but it is being shutdown.
Location: C:\Users\Administrator.cargo\registry\src\index.crates.io-6f17d22bba15001f\tokio-1.34.0\src\runtime\time\entry.rs:556

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
0: Failed to get farmer into
1: Failed to get farm summary at `“S:\\”’
2: The process cannot access the file because another process has locked a portion of the file. (os error 33)


Someone told me on Discord that pulsar isn’t working. I tried the advanced and now it’s syncing but I can’t tell you if works yet.