Crashes Mac after 34 days of uptime? sometimes excessive memory use?

Just some notes on things I think I've observed using Hex (before I moved to mostly using my own mac stt hotkey thing):

- I think, but can't conclusively prove, having Hex running on a current-OS-release updated Mac causes a system crash after 34 days of uptime. from what I can tell, Hex is live polling the system permissions 10 times per second forever. I think there's a Mac kernel counter bug which overflows and crashes after it hits a limit of those checks for some reason.
- Having Hex just loaded continuously, I had my Mac crash, like hard crash, freeze, clocks 100% stop, nothing works, have to hard power cycle it twice, exactly 34 days apart. the only weird thing I see is Hex doing 10 system permission checks per second continuously just driving up system counters until they stop.
- Other weird bug: when running on an older release of macOS (14.8.2) sometimes Hex uses like 8 gigabytes of RAM and then will randomly crash (while on newer mac releases, it uses a reasonable amount of memory).

Anyway, just some notes if these are interesting to anybody else.

No source file, test, or entry point is identified. Start by reviewing how Hex polls system permissions on macOS and compare behavior after extended uptime on current macOS versus 14.8.2. Done would mean reproducing or narrowing the reported 34-day crash and excessive memory use enough to define a confirmed fix.

Written by the indexing model from the issue text.