Close everything and reboot. Check if the modification persists and
launchctl limit maxfiles
now shows a larger than 256 value after you did
sudo launchctl limit maxfiles 999 unlimited
it should.
Close everything and reboot. Check if the modification persists and
launchctl limit maxfiles
now shows a larger than 256 value after you did
sudo launchctl limit maxfiles 999 unlimited
it should.
I ran the above line in Terminal re-started and it reverted to 256
The other interesting thing is now a different line is throwing the error.
Sigh My app that finds weird errors.
Is there a way to add this line to code?
Before going that route, try making a new account on your machine and see if the problem persists and also try it on someone elseās computer. You really shouldnāt be changing these values on a machine you donāt own.
You know, I guess he has some kind of bug instantiating TextInputStreams or whatever, opening files, probably in loop, not releasing them and exhausting the maxfiles.
Not really a system problem.
I solved my problem. Cmd R Option P
Thank you for help.
What?
Good to know. Very unusual problem and solution. I would never look where you looked at and find it.
What I find interesting is that I canāt think on how that affected the case, as Command-Option-P-R just resets:
Selected startup disk, speaker volume, screen resolution, and time zone.
From the Parameters NVRAM.
But⦠whatever if it worked for the user
I finally found the actual cause of the above problem. The basic problem was I had an instance of variable of type BoxMssage that I hadnāt declared as in
Var Bmsg As BoxMssage
The analyzer didnāt find it back in 2020 (because it was isn TargetWindows) and still hadnāt. The suspect code above was above this code and Mac didnāt like it. I havenāt ran my PC in 3 years.
I hope this makes a little sense. I can partly forgive the analyzer as I have well over a MB of code.