Jonathan Armani writes: > Hi, > > Works smoothly on my amd64 too but need an ulimit -d bump to not segfault > at start. > > Maybe the launcher could be adjusted like chrome to handle it ? Or a readme > ?
I sympathize but I really don't think this is practical. It would take a lot of effort to shim in wrapper scripts for every app in the ports tree that needs bumped limits to use--openttd, supertuxkart, widelands... and who's going to keep the necessary memory values up to date? Do we provide a wrapper for firefox since it lasts a lot longer without crashing if you bump limits (but not too high or it hits swap eventually)...? We used to do something similar with VMEM_WARNING for builds, but in the end it was just more practical to assume a builder has set appropriate limits for the task at hand, and I think that's the way to go for playing games as well. -- Anthony J. Bentley
