NeoTokyo Tips

2009 MacBook (OS X Leopard) with Crossover Games 8.0

The following bugs may be seen on 2009 MacBook (model: MacBook5,2), running the NVIDIA GeForce 9400M GPU.

Bug: In-game vision modes not working

This bug is related to the DirectX libraries. DirectX 8 has issues with correctly rendering the game, especially the shaders used in the vision mode. The solution is to force hl2.exe to use DirectX 9 libraries by adding "-dxlevel 90" in the Set Launch Options string within NEOTOKYO's properties window.

Bug: Unhandled page fault on read access to 0x00000024

This bug may either crop up when you create a server or during spawning. You will see something similar to these error messages just prior to the stack trace output:
  • wine: Unhandled page fault on read access to 0x00000024 at address 0xd4ab423 (thread 002b)
  • wine: Unhandled page fault on read access to 0x00000024 at address 0xd4ab423 (thread 002b)
  • Unhandled exception: page fault on read access to 0x00000024 in 32-bit code (0x0d4ab423).
There are two solutions to this bug:
  1. As Sebastian Ortiz noted, setting your resolution under 1024 x 768 prevents this bug. Either fullscreen and windowed screen modes may be used.
  2. Set hl2.exe to run in Windows 98 mode. This bug will occur in the default Windows XP mode, if the screen resolution is not reduced.

Bug: No memory available for malloc

This bug may crop up randomly, but usually within the first few minutes. You will see something similar to these error messages, probably repeated over and over and over and ..., just prior to the stack trace output:
  • wineloader(2449,0x58147000) malloc: *** mmap(size=2097152) failed (error code=12) 
  • *** error: can't allocate region 
  • *** set a breakpoint in malloc_error_break to debug
  • what():  St9bad_alloc 
What is happening is that with 32-bit registers (e.g., any 32-bit processor) only 2 Gb of continuous memory may be accessed by a process, and all of that is getting gobbled up. I've seen this bug complained about in the Counter-Strike: Source communities and they lay the blame on graphics shaders. Outside of disabling shaders, which leads to undesirable consequences that are explained below, thwarting this bug simply requires lowering memory requirements as much as possible.

There are two solutions to this bug:
  1. As Sebastian Ortiz noted, again, reduce your resolution. Also, try reducing in-game graphics options.
  2. Disable shaders through the Graphics tab of winecfg. While this will significantly reduce out-of-memory errors (I yet to have an out-of-memory with shaders disabled) it also prevents the different in-game vision modes (Night Vision, Motion Vision, and Thermal Vision) due to them all requiring vertex shaders.

by Marshall Reeske on 2009-11-06 22:24:54
Important Information Tips are provided by the CrossOver Community and Advocates. They are not intended to be used for official CodeWeavers Support. For that, please visit our official support pages.
CodeWeavers or its third-party tools process personal data (e.g. browsing data or IP addresses) and use cookies or other identifiers, which are necessary for its functioning and required to achieve the purposes illustrated in our Privacy Policy. You accept the use of cookies or other identifiers by clicking the Acknowledge button.
Please Wait...
eyJjb3VudHJ5IjoiVVMiLCJsYW5nIjoiZW4iLCJjYXJ0IjowLCJ0enMiOi01LCJjZG4iOiJodHRwczpcL1wvbWVkaWEuY29kZXdlYXZlcnMuY29tXC9wdWJcL2Nyb3Nzb3Zlclwvd2Vic2l0ZSIsImNkbnRzIjoxNzA4NjEzODE4LCJjc3JmX3Rva2VuIjoidFN4SGRmZzR1RjU3N3dQbSIsImdkcHIiOjB9