Re: Detecting ulimit problem

2005-05-21 Thread Alexandre Julliard
Robert Lunnon <[EMAIL PROTECTED]> writes: > Really we need a better way. Under Solaris I have run into these problems for > well over 2 years and I have a patch in my kit that pre-allocates 64MB for > the heap then lets mmap allocate over the 2 GB limit for everything else, eg > DLLs and so on.

Re: Detecting ulimit problem

2005-05-20 Thread Robert Lunnon
On Sat, 21 May 2005 04:40 am, Eric Frias wrote: > Mike Hearn wrote: > > On Thu, 19 May 2005 17:46:28 -0400, Eric Frias wrote: > >>I'll get a patch ready once I understand a bit more of what is going on > >>that is causing wine to reserve this memory. > > > > It's probably blocking off the top 3rd q

Re: Detecting ulimit problem

2005-05-20 Thread Eric Frias
Mike Hearn wrote: On Thu, 19 May 2005 17:46:28 -0400, Eric Frias wrote: I'll get a patch ready once I understand a bit more of what is going on that is causing wine to reserve this memory. It's probably blocking off the top 3rd quarter of the address space to prevent the kernel allocating memory a

Re: Detecting ulimit problem

2005-05-20 Thread Mike Hearn
On Thu, 19 May 2005 17:46:28 -0400, Eric Frias wrote: > I'll get a patch ready once I understand a bit more of what is going on > that is causing wine to reserve this memory. It's probably blocking off the top 3rd quarter of the address space to prevent the kernel allocating memory above the 2gig

Re: Detecting ulimit problem

2005-05-19 Thread Eric Frias
Daniel Kegel wrote: [EMAIL PROTECTED] wrote: http://bugs.winehq.org/show_bug.cgi?id=2609 [Proposed fix:] struct rlimit address_limits; int required_address_space = 1024 * 1024 * 1400; /* 1400M */ getrlimit(RLIMIT_AS, &address_limits); if (address_limits.rlim_max < required_addre

Re: Detecting ulimit problem

2005-05-19 Thread Daniel Kegel
[EMAIL PROTECTED] wrote: http://bugs.winehq.org/show_bug.cgi?id=2609 [Proposed fix:] struct rlimit address_limits; int required_address_space = 1024 * 1024 * 1400; /* 1400M */ getrlimit(RLIMIT_AS, &address_limits); if (address_limits.rlim_max < required_address_space) WINE_WARN("Your virtual

Detecting ulimit problem

2005-05-19 Thread Eric Frias
I just ran into bug 2609: http://bugs.winehq.org/show_bug.cgi?id=2609 which is that wine fails to initialize when the user has a ulimit for virtual memory (address space) set to less than around 1300MB. This is something wine could test for and issue a warning. I know this isn't technically a