http://bugs.winehq.org/show_bug.cgi?id=13335
Jörg Höhle hoehle@users.sourceforge.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |hoehle@users.sourceforge.ne | |t
--- Comment #189 from Jörg Höhle hoehle@users.sourceforge.net 2010-05-13 14:39:57 --- Here's another data point: mmap failures on 32bit Mac OS X 10.5.8 + NVidia with wine-1.1.24
After upgrading my Mac from 1GB RAM to 4GB, Lego Star Wars 2 started crashing in Wine-1.1.24 after a variable amount of play time. The error always starts with:
wine(6017,0xa022e720) malloc: *** mmap(size=16777216) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug
This is repeated 6/8/10 times, size always 16MB, followed by a crash like: wine: Unhandled page fault on write access to 0x0000003c at address 0x7305cadb (thread 0018), starting debugger... The backtrace shows nothing particular.
The machine is an "early 2009" Mac mini 2GHz core duo with Nvidia 9400 graphics processor. Using Mac OS X 10.5.8 and XQuartz 2.3.3.2. So this is a strict 32bit system.
The crashes occur sometimes after half an hour, sometime after an hour of game play. I'm pretty confident that the RAM upgrade is the cause because - no SW upgrade of any kind was done around that time (let's hope I got no trojan), - I'm using LSW2 in wine-1.1.24 with a prefix distinct from my git snapshot work, - the app has been very stable in the past (the children played for hours), - another app started failing as well (see next comment), - the crashes appear in levels the children played in the past, not new ones, - such a huge RAM upgrade affects the memory mapping. Among others, the Nidia chip is said to make use of more main memory when the machine has more than 1GB RAM (256MB? instead of 128MB).
Obviously the machine is not running out of memory. It now has more than before. Instead, I believe this confirs the hypothesis about running out of address space, c.f. R. Colenbrander's comment #96.
I have no reasons to believe that the new RAM is faulty. The machine is very stable and only 2 apps in Wine are affected. I'm not going to remove the RAM because of the effort it was to open the Mac mini box (the back sat so tight that you couldn't slide in a putty knife, not even a sheet of paper).
Perhaps somebody knows a SW tool that can simulate a Mac equipped with 1GB RAM only?
Few people ever reported the dependency of the mmap failure on the amount of RAM. http://forums.adobe.com/message/1875853 mentions a perhaps similar failure with native Photoshop.
Because of bug #22029 I cannot test the app in current Wine. It's unfortunate that this mmap issue affects wine-1.1.24 because this release was excellent at 3D games with the 1GB Mac Mini.