[Bug 9252] Far Cry: Segmentation fault on startup when using Direct3D

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=9252





--- Comment #31 from byteframe <byteframe at yahoo.com>  2009-07-26 01:20:21 ---
I was finally able to reproduce the bug, I think. I set my VideoMemortSize to
64, and when I loaded a large farcry level, and set r_hdrrendering 1 in the
console, I got it to crash. I got the same error dialog box as the previous
screenshot submitted by mcpaul.

It's seemingly an out of memory issue. If true, then I think bug 13165 is a
dupe of this one. Also, The "on startup" in the bug description is misleading.
I grepped a verbose (+d3d) log when reproducing the crash for
"GetAvailableTextureMem", and it seems my 320 MB 8800GTS was being accurately
questimated : trace:d3d:IWineD3DDeviceImpl_GetAvailableTextureMem (0x15a6e8) :
simulating 320MB, returning 291MB left.

I should also note that a previous session of testing and screenshot collecting
(going back and forth between opengl and d3d, and starting the game many times
over), after I while I couldn't even start the game. I got a GLXBadDrawable
Error, even after killing wine. I was seemingly out of memory, and had to
restart X. So it seems, FarCry might leak a fair amount of memory, or it might
be related this being spit out a few hundred times upon quitting the game
normally: fixme:d3d:dumpResources Leftover resource 0x329a4a0 with type
3,WINED3DRTYPE_TEXTURE,

Debug attachment of crash to follow.

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.