[NEEDS INFO] Atlas hangs when started under Fraps

[vts]

On my machine, Atlas' game window seems to hang when started while Fraps is active. The UI is visible, but the game window doesn't load and causes a stall. I'm running Fraps 2.9.4 on Windows Vista 32-bit SP2 with a GeForce GTS 250 1GB with ForceWare 285.62 drivers.

If I first start Atlas and then Fraps, then everything's fine and the Fraps counter shows up as expected. Loading the main game under Fraps also works fine.

Interrupting a debug build during the hang yields the following stack trace (dumped from VS2010):

>	pyrogenesis_dbg.exe!OglTex_reload(OglTex * ot=0x05a01380, const boost::shared_ptr<IVFS> & vfs={...}, const Path & pathname={...}, __int64 h=1900573)  Line 477 + 0x11 bytes	C++
 	pyrogenesis_dbg.exe!call_init_and_reload(__int64 h=1900573, H_VTbl * type=0x01b90bd8, HDATA * hd=0x05a01340, const boost::shared_ptr<IVFS> & vfs={...}, const Path & pathname={...}, char * * init_args=0x0496fad8)  Line 446 + 0x21 bytes	C++
 	pyrogenesis_dbg.exe!alloc_new_handle(H_VTbl * type=0x01b90bd8, const boost::shared_ptr<IVFS> & vfs={...}, const Path & pathname={...}, unsigned int key=2228584406, unsigned int flags=17, char * * init_args=0x0496fad8)  Line 489 + 0x21 bytes	C++
 	pyrogenesis_dbg.exe!h_alloc(H_VTbl * type=0x01b90bd8, const boost::shared_ptr<IVFS> & vfs={...}, const Path & pathname={...}, unsigned int flags=17, ...)  Line 536 + 0x1d bytes	C++
 	pyrogenesis_dbg.exe!ogl_tex_load(const boost::shared_ptr<IVFS> & vfs={...}, const Path & pathname={...}, unsigned int flags=17)  Line 545 + 0x1c bytes	C++
 	pyrogenesis_dbg.exe!CTextureManagerImpl::LoadTexture(const boost::shared_ptr<CTexture> & texture={...}, const Path & path={...})  Line 177 + 0xf bytes	C++
 	pyrogenesis_dbg.exe!CTextureManagerImpl::TryLoadingCached(const boost::shared_ptr<CTexture> & texture={...})  Line 266	C++
 	pyrogenesis_dbg.exe!CTextureManagerImpl::MakeProgress()  Line 381 + 0x11 bytes	C++
 	pyrogenesis_dbg.exe!CTextureManager::MakeProgress()  Line 638	C++
 	pyrogenesis_dbg.exe!RendererIncrementalLoad()  Line 97 + 0x13 bytes	C++
 	pyrogenesis_dbg.exe!RunEngine(void * data=0x0023fa20)  Line 218	C++
 	pyrogenesis_dbg.exe!thread_start(void * param=0x00279078)  Line 624 + 0x9 bytes	C++
 	msvcr100d.dll!_callthreadstartex()  Line 314 + 0xf bytes	C
 	msvcr100d.dll!_threadstartex(void * ptd=0x02ebfc38)  Line 297	C

Where pathname = "cache/art/textures/animated/water/default/normal21.dds.f954ed5b3acbdfc1.dds" in the last stack frame, should it matter.

[historic_bruno]

Can you interact with the Atlas UI? How does its call stack look?

[historic_bruno]

Hmm I'm testing with FRAPS 3.4.7 on Windows 7 64-bit and Atlas seems to start up correctly, and works fine, unless the canvas gets resized, then I get an error like this:

 First-chance exception at 0x7728f9d2 in pyrogenesis_dbg.exe: 0xC0000008: An invalid handle was specified.

 ntdll.dll!7728f9d2() 	
 [Frames below may be incorrect and/or missing, no symbols loaded for ntdll.dll]	
 ntdll.dll!7728f9d2() 	
 KernelBase.dll!74f2b9f2() 	
 fraps32.dll!57b83bb0() 	
 fraps32.dll!57b7e6c7() 	
 fraps32.dll!57b7eed4() 	
 fraps32.dll!57b7eef0() 	
 gdi32.dll!75165a20() 	
 > AtlasUI_dbg.dll!wxGLCanvas::SwapBuffers()  Line 543	C++
 AtlasUI_dbg.dll!Atlas_GLSwapBuffers(void * canvas)  Line 66	C++
 pyrogenesis_dbg.exe!AtlasViewGame::Render()  Line 262 + 0x12 bytes	C++
 pyrogenesis_dbg.exe!RunEngine(void * data)  Line 227 + 0x15 bytes	C++
 pyrogenesis_dbg.exe!thread_start(void * param)  Line 624 + 0x9 bytes	C++
 msvcr100d.dll!_callthreadstartex()  Line 314 + 0xf bytes	C
 msvcr100d.dll!_threadstartex(void * ptd)  Line 297	C
 kernel32.dll!751c339a() 	
 ntdll.dll!772a9ef2() 	
 ntdll.dll!772a9ec5() 	

It doesn't matter which I start first. Seems like a conflict between wxWidgets and FRAPS, which is not surprising really. At least it's better than hanging completely during startup.