Pseudo-random at best
<3 … love it. Sounds like you started where I did; and HEX with a black hat to truly understand how memory works, disassembly, dll injection, and assembly language for those pesky TI calculators.
Congrats, you’ve completely missed the point. If you’ve paid attention to the context (what post I’ve replied to and the related aspects of the video) you’d see the point was to illustrate what someone perceives as randomness or not might be completely different from what actually is, or in other words people’s expectations of what random should be like might not align with what is random. ![]()
No more downtime?
they’ve not done an experiement for a while on that one.. i wonder if they will do another one anytime soon.
Asked and got an answer back, that its not something they are currently considering. just too much stuff going on with Downtime.
As far as I knew, a big South American snake. However apparently it is a programming language. I thought everyone uses Visual C++ or something else I have heard of before. I Googled it, it is open source ( AKA FREE ) so they don’t have to pay for it. The real odd thing I am reading on this page “plays well with others” and digging deeper, that means it works on Windows, Linux, and Mac OS. So why don’t they use this to make a native Linux client?

they only had one dev who used linux while the others used windows. that dev is now gone..
I am experiencing a significant increase in memory usage on macOS since the latest update, and I am wondering if this could be related to the memory leak / memory management issues mentioned here.
System:
- MacBook Pro
- Apple M2 Pro
- 16 GB Unified Memory
- macOS Tahoe 26.6.2
- Native EVE Online macOS client
- Usually running up to 7 EVE Online clients simultaneously
Before the latest update:
My EVE clients normally used around 2–2.5 GB of RAM per client. I was able to run multiple clients simultaneously without major memory issues.
Since the latest update:
Each EVE client now uses approximately 5–5.5 GB of RAM, sometimes even more.
This means the memory requirement per client has effectively more than doubled immediately after the update.
With multiple clients running, macOS very quickly runs out of physical memory and starts using large amounts of swap memory. Running my usual 7 clients is therefore no longer realistically possible on my 16 GB MacBook.
The important part is that this behavior only started after the latest EVE update. I did not have this issue before.
I have already tried:
- Clearing the EVE client cache
- Setting all graphics options to the absolute minimum
- Using the lowest possible graphics / “Potato Mode”
- Restarting the clients
- Restarting macOS
- Testing different graphics settings
Unfortunately, none of these steps have significantly reduced the memory consumption.
What I find particularly strange is that even with graphics settings reduced to minimum, a single client still consumes roughly 5–5.5 GB, compared to approximately 2–2.5 GB before the update.
In my case, I am not yet sure whether this is a traditional memory leak where RAM usage continuously increases over time, or whether the client simply allocates significantly more memory immediately after launch since the update.
I will also test whether opening specific UI windows (Skill window, Opportunities, etc.) or changing Upscaling/FSR-related settings has any effect on the memory usage, similar to what has been reported by Linux/Wine users.
If other macOS users, especially users with Apple Silicon (M1/M2/M3/M4), could check their Activity Monitor and compare the memory usage per EVE client, that would be very helpful.
For me, the difference is very clear:
Before update: ~2–2.5 GB RAM per client
After update: ~5–5.5+ GB RAM per client
Same MacBook, same accounts, same general configuration.
This change occurred directly after the latest update.
As a fellow Mac user, I wanted to get you some feedback. I’m running a Mac Mini M4 with 16GB RAM under Tahoe 26.5.2. The five (5) EVE clients I have running atm are using the following in Active Monitor:
• EVE … 3.25GB
• EVE … 2.93GB
• EVE … 2.83GB
• EVE … 2.68GB
• EVE … 2.66GB
Hopefully this helps you in your efforts to troubleshoot the high memory usage. Best of luck!