XenThePybroBlakout74dxlevel 80
macs run on openGL, all this will do is change a few commands.
The most common source of mac crashes are lack of memory and thats what your error code is so have you tried opening activity monitor and monitoring your memory (ram) or getting a third party app such as memory clean to monitor your memory while tf2 loads
Setting mac_picmip to anything but 1 or 2 will also cause a crash due to a memory leak bug that has been around since the mac update so turn that down if you have it up.
A restart may also help to clear your caches and possibly free up some more memory.
Thanks! I may have downloaded a mod before that rendered in ultra low textures, but have deleted it; I'm going to mess around with my configs and launch options and see if I can get rid of that setting.
Meanwhile, I've started up TF2 again and monitored the memory usage up to the crash. The thing steadily skyrockets from 40~ mb to 400 mb. Funny thing is, the app I'm using to monitor memory quickly jumped up to 4 GB before jumping back down. At the time of this sentence TF2 has crashed and the application was at around 600~ mb.
2nd Trial -
Upon launching the game, hl2_osx climbs up to 130 mb of usage before "(Not Responding)." Physical memory is at 8 GB and memory used is only at 3.2 GB. TF2 has gone up to 260. And remember, I'm running Steam and Chrome at the same time as TF2, and the memory used is only at around 3.5 GB. TF2 has climbed up to 450 mb. Still not the largest memory hog - but now it is, surpassing kernel_ask at 680~ or so. And it crashes.
3rd Trial -
Launched tf2, climbs up to 3rd place in a matter of seconds, not repsonding. 170 mb. it's climbed to 220, and is slowly climbing at maybe a rate of 20 per 3 seconds. 300 mb, 2nd place on the memory hog list. Climbing still to 353.9 mb. kernel_task is at 673. 400 mb for tf2 now, memory used is 3.6. 480, then 640, and now 660 is tf2, then it reached 683 and crashes. perhaps if it surpasses kernel_task in usage, it's considered too big? there's that large jump from 480 to 660 in 3 seconds, maybe that's what causes the crash?