Constant Periodic Task Error

[Savi-on]

Quite frequently, and sometimes for minutes straight I keep getting the errors "Periodic task error: Exception: FetchEditor error." and "Periodic task error: Exception: FetchAll error." Making the visualizer pretty much impossible for me to use. I try refreshing or restarting and sometimes it takes 3+ restarts. Or sometimes I need to close the editor, close the visualizer, open the visualizer and the open the editor again for it to start working. But sometimes after doing that it also just freezes permanently again. Is there anything I can try to fix this, it's really hard to map with this issue lol.

I have tried releases 20260820.1, 20260808.1, and 20251102.1

Below I sent a log of yesterday as an example, but it has been happening the moment i started using it 5 months ago.

log_20260902.log

[Exsper]

Could you help pin it down?

1. Settings → Log: enable Editor Reader (and Log Level = Debug), reproduce, and send the log. The log you attached only contains the throttled summaries; the useful lines (ReadProcessMemory failed …, scan aborted after 30000 ms, blocked at region N/M, Fetched data is invalid.) are behind that switch.
2. Do the errors cluster around test plays / switching maps / map loading / dragging objects? That would confirm the first case.
3. What does the status bar say at the time (Editor is not running, Drawing)? Is osu! running as administrator (the log viewer is not elevated)? Windows or Wine, how much RAM, how large is the map?
4. Things that reliably help right now: leave osu! in song select, start the viewer, then open the map; raise Full read / Low-freq read in the settings (e.g. 100 / 200 ms) and the Idle interval; when it gets stuck, restart only the viewer and re-open the map (no need to restart osu!).

If you are using other tools like Mapping Tools and work fine
Mapping Tools does use the same Editor_Reader library (by Karoo13), but it reads once per user action, and on failure it catches the exception, writes editor_reader_error.txt and silently falls back to the .osu on disk; it also drops invalid objects instead of failing the whole snapshot. It never polls at 20 ms, so its failures are invisible.