GMod VERY Unstable (...more crashing) - Help

I know I've posted here a few time about how my game has been crashing a lot while I've been trying to load L4D2 models spawn icons. That stopped happening after I stopped using those specific models due to them being incompatible with Garry's Mod's engine. Well, just now I was playing with some combine soldier NPC's with some addon weapons. I was constantly checking the console to see if I was getting any errors and everything was fine. I was standing on a ragdoll when a soldier throws a grenade in my general direction. I hear it explode and a frame of the explosion is seen and then my game crashes. I was able to get a crash report and here it is: [CODE]Process: hl2_osx [28126] Path: /Users/hoytfelton/Library/Application Support/Steam/steamapps/common/GarrysMod/hl2_osx Identifier: hl2_osx Version: ??? (???) Code Type: X86 (Native) Parent Process: steam [28091] Date/Time: 2014-04-12 12:38:27.656 -0400 OS Version: Mac OS X 10.6.8 (10K549) Report Version: 6 Interval Since Last Report: 80073 sec Crashes Since Last Report: 15 Per-App Crashes Since Last Report: 2 Anonymous UUID: 8B53C3ED-84AB-4053-9BFE-55A952F721C6 Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Exception Codes: 0x0000000000000001, 0x0000000000000000 Crashed Thread: 0 AwesomiumBrowserMain Dispatch queue: com.apple.main-thread Thread 0 Crashed: AwesomiumBrowserMain Dispatch queue: com.apple.main-thread 0 Awesomium 0x2bc52ce1 mac_plugin_interposing::GetPluginWindowHasFocus(void*) + 1676113 1 libSystem.B.dylib 0x906cde40 szone_error + 287 2 libSystem.B.dylib 0x905d88c0 allocate_pages + 243 3 libSystem.B.dylib 0x905e91f2 large_malloc + 1093 4 libSystem.B.dylib 0x905daa42 szone_malloc_should_clear + 3656 5 Awesomium 0x2bc536d1 mac_plugin_interposing::GetPluginWindowHasFocus(void*) + 1678657 6 libSystem.B.dylib 0x905d9ba8 malloc_zone_malloc + 81 7 libSystem.B.dylib 0x905d7c78 malloc + 50 8 libstdc++.6.dylib 0x9a393617 operator new(unsigned long) + 36 9 libstdc++.6.dylib 0x9a393703 operator new[](unsigned long) + 17 10 vguimatsurface.dylib 0x15dead91 CMatSystemTexture::SetMaterial(IMaterial*) + 321 11 vguimatsurface.dylib 0x15deb6df CTextureDictionary::BindTextureToMaterial(int, IMaterial*) + 63 12 vguimatsurface.dylib 0x15de2591 CMatSystemSurface::DrawSetTextureMaterial(int, IMaterial*) + 33 13 vguimatsurface.dylib 0x15dda84e CFontTextureCache::CreateFontMaterials(CFontTextureCache::Page_t&, ITexture*, bool) + 286 14 vguimatsurface.dylib 0x15ddac7a CFontTextureCache::AllocatePageForChar(int, int, int&, int&, int&, int&, int&) + 682 15 vguimatsurface.dylib 0x15dda15d CFontTextureCache::GetTextureForChars(unsigned long, vgui::FontDrawType_t, wchar_t const*, int*, float**, int) + 733 16 vguimatsurface.dylib 0x15dd9e72 CFontTextureCache::GetTextureForChar(unsigned long, vgui::FontDrawType_t, wchar_t, int*, float**) + 66 17 vguimatsurface.dylib 0x15de3a35 CMatSystemSurface::DrawGetUnicodeCharRenderInfo(wchar_t, vgui::CharRenderInfo&) + 261 18 vguimatsurface.dylib 0x15de3910 CMatSystemSurface::DrawUnicodeChar(wchar_t, vgui::FontDrawType_t) + 48 19 client.dylib 0x2ae6f265 CHudTexture::DrawSelf(int, int, int, int, Color const&) const + 133 20 client.dylib 0x2ae6f1d7 CHudTexture::DrawSelf(int, int, Color const&) const + 71 21 client.dylib 0x2ae5ecd7 CHudWeaponSelection::DrawLargeWeaponBox(C_BaseCombatWeapon*, bool, int, int, int, int, Color, float, int) + 551 22 client.dylib 0x2ae5e985 CHudWeaponSelection::Paint() + 789 23 client.dylib 0x2ae5ef94 non-virtual thunk to CHudWeaponSelection::Paint() + 20 24 client.dylib 0x2affa2d7 vgui::Panel::PaintTraverse(bool, bool) + 1111 25 vgui2.dylib 0x15f946b3 VPanelWrapper::PaintTraverse(unsigned int, bool, bool) + 51 26 client.dylib 0x2affa36a vgui::Panel::PaintTraverse(bool, bool) + 1258 27 vgui2.dylib 0x15f946b3 VPanelWrapper::PaintTraverse(unsigned int, bool, bool) + 51 28 engine.dylib 0x13aa4e0e vgui::Panel::PaintTraverse(bool, bool) + 750 29 vgui2.dylib 0x15f946b3 VPanelWrapper::PaintTraverse(unsigned int, bool, bool) + 51 30 vguimatsurface.dylib 0x15de53fa CMatSystemSurface::PaintTraverseEx(unsigned int, bool) + 570 31 engine.dylib 0x139d61cb CEngineVGui::Paint(PaintMode_t) + 795 32 engine.dylib 0x139e885a CVRenderView::VGui_Paint(int) + 26 33 client.dylib 0x2af03528 CViewRender::RenderView(CViewSetup const&, int, int) + 6632 34 client.dylib 0x2aeef814 CViewRender::Render(vrect_t*) + 3156 35 client.dylib 0x2acc68f4 CHLClient::View_Render(vrect_t*) + 308 36 engine.dylib 0x139e7edf V_RenderView() + 287 37 engine.dylib 0x138c1ec9 SCR_UpdateScreen() + 281 38 engine.dylib 0x138d3480 _Host_RunFrame_Render() + 400 39 engine.dylib 0x138d4ad8 _Host_RunFrame(float) + 3352 40 engine.dylib 0x138edf4b CHostState::State_Run(float) + 267 41 engine.dylib 0x138ed23c CHostState::FrameUpdate(float) + 380 42 engine.dylib 0x138ed0b5 HostState_Frame(float) + 37 43 engine.dylib 0x139c5269 CEngine::Frame() + 969 44 engine.dylib 0x139c21f9 CEngineAPI::MainLoop() + 345 45 engine.dylib 0x139c2c50 CModAppSystemGroup::Main() + 208 46 engine.dylib 0x13a0a63e CAppSystemGroup::Run() + 46 47 engine.dylib 0x139c2549 CEngineAPI::RunListenServer() + 105 48 launcher.dylib 0x001c4c1a CSourceAppSystemGroup::Main() + 26 49 launcher.dylib 0x001d064e CAppSystemGroup::Run() + 46 50 launcher.dylib 0x001da5fb CSteamApplication::Main() + 43 51 launcher.dylib 0x001d064e CAppSystemGroup::Run() + 46 52 launcher.dylib 0x001d77bd MainFunctionThread(void*) + 77 53 launcher.dylib 0x001d7ac4 ValveCocoaMain + 452 54 launcher.dylib 0x001c52d6 LauncherMain + 1078 55 hl2_osx 0x00001d95 start + 53 Thread 1: Dispatch queue: com.apple.libdispatch-manager 0 libSystem.B.dylib 0x905fc382 kevent + 10 1 libSystem.B.dylib 0x905fca9c _dispatch_mgr_invoke + 215 2 libSystem.B.dylib 0x905fbf59 _dispatch_queue_invoke + 163 3 libSystem.B.dylib 0x905fbcfe _dispatch_worker_thread2 + 240 4 libSystem.B.dylib 0x905fb781 _pthread_wqthread + 390 5 libSystem.B.dylib 0x905fb5c6 start_wqthread + 30 Thread 2: 0 libSystem.B.dylib 0x90603aa2 __semwait_signal + 10 1 libSystem.B.dylib 0x9060375e _pthread_cond_wait + 1191 2 libSystem.B.dylib 0x906032b1 pthread_cond_timedwait$UNIX2003 + 72 3 libtier0.dylib 0x000536c0 CThreadSyncObject::Wait(unsigned int) + 288 4 libtier0.dylib 0x00053968 CThreadEvent::Wait(unsigned int) + 24 5 filesystem_stdio.dylib 0x1317eb2d CFileTracker2::ThreadedProcessMD5Requests() + 653 6 filesystem_stdio.dylib 0x1317e891 ThreadStubProcessMD5Requests(void*) + 17 7 libtier0.dylib 0x00053301 ThreadProcConvert(void*) + 33 8 libSystem.B.dylib 0x90603259 _pthread_start + 345 9 libSystem.B.dylib 0x906030de thread_start + 34 Thread 3: 0 libSystem.B.dylib 0x90603aa2 __semwait_signal + 10 1 libSystem.B.dylib 0x9060375e _pthread_cond_wait + 1191 2 libSystem.B.dylib 0x906032b1 pthread_cond_timedwait$UNIX2

The problem is probably from the vphysics. If ragdolls suddenly go from none to a very high velocity, it has a chance of causing a crazy physics crash.

Strangely enough it crashed in the web browser thingy GMod uses, not GMod itself.

[QUOTE=Robotboy655;44527206]Strangely enough it crashed in the web browser thingy GMod uses, not GMod itself.[/QUOTE] Where do you see that in the dump log?

[QUOTE=code_gs;44527216]Where do you see that in the dump log?[/QUOTE] Uh, [code] Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Exception Codes: 0x0000000000000001, 0x0000000000000000 Crashed Thread: 0 AwesomiumBrowserMain Dispatch queue: com.apple.main-thread Thread 0 Crashed: AwesomiumBrowserMain Dispatch queue: com.apple.main-thread[/code] ???

This a very common crash bug on OS X. Been there for over a year. Exact stack trace varies a bit but 0-6 seems to be the common factor. I somewhat doubt it'll ever be fixed unfortunately. Garry seemed to ignore it, yet reported all other Awesomium bugs to them. Maybe it's already fixed in Awesomium but GMod isn't up-to-date? I don't know what version GMod is using right now. Perhaps _Kilburn could investigate. Could even be an issue with GMod's implementation. [QUOTE=Robotboy655;44527225]Uh, [code] Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Exception Codes: 0x0000000000000001, 0x0000000000000000 Crashed Thread: 0 AwesomiumBrowserMain Dispatch queue: com.apple.main-thread Thread 0 Crashed: AwesomiumBrowserMain Dispatch queue: com.apple.main-thread[/code] ???[/QUOTE] That's actually the thread name. Awesomium seems to rename the main thread to their own. Really doesn't make much a difference. There's a crash on quit bug on OS X related to CRopeManager and that's nothing to do with Awesomium. This case it does seem to be Awesomium as that's where the stack trace ends up: [code]0 Awesomium 0x2bc52ce1 mac_plugin_interposing::GetPluginWindowHasFocus(void*) + 1676113[/code]