[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: cannot allocate memory running mame
On Thu, Oct 01, 2020 at 08:15:00AM -0400, Greg Troxel wrote:
> Thomas Klausner <wiz%NetBSD.org@localhost> writes:
> >> > /*
> >> > * Virtual memory related constants, all in bytes
> >> > */
> >> > #define MAXTSIZ (256*1024*1024) /* max text size */
> >> AFAICT for amd64 the limit is arbitrary, if you only need it temporarily for
> >> debugging purposes, just bump it to 512 MB (or bigger) and rebuild your kernel.
> > Thanks for the analysis.
> > Actually, that is the size of mame stripped, so yes, I need this bigger :)
> > Should we bump it in general?
> While 256M of text seems big, I find it really surprising to have a
> compiled limit that low.
> For me, the biggest installed program is mongod at 32M, in terms of text
> as reported by size(1).
> So I would support bumpming that to 512M for sure, maybe 1G.
> It also seems like this belongs in ulimit, as something a sysadmin would
> reasonably want to set along with data size limits.
Just to confirm, bumping the limit made mame start.
How do we proceed? Joerg seems to think the limit should just be
removed completely (though I don't know what the arguments are, either
Main Index |
Thread Index |