Created attachment 97706 [details] Apitrace While trying to play Call Of Duty 4 under Wine using the mesa driver the game crashes while loading a saved level. I have tried to get an ApiTrace of the game starting, looks like there's a memory leak in some part of Mesa because when I use the Catalist driver the game starts correctly. I'm using Wine 1.7.17, Mesa from Git and Ubuntu 14.04. 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5730 / 6570M] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device 1594 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 45 Region 0: Memory at b0000000 (64-bit, prefetchable) [size=256M] Region 2: Memory at c4000000 (64-bit, non-prefetchable) [size=128K] Region 4: I/O ports at 4000 [size=256] Expansion ROM at c4040000 [disabled] [size=128K] Capabilities: <access denied> Kernel driver in use: radeon
That apitrace doesn't contain much useful I'm afraid. Please attach any relevant terminal output from the game as well as the /var/log/Xorg.0.log file and the output of dmesg (preferably from after the problem occurred) and glxinfo.
Created attachment 97748 [details] glxinfo
Created attachment 97749 [details] dmesg
Created attachment 97750 [details] Wine Console Output
Created attachment 97751 [details] Xorg.0.log
Is there any way I can create a more useful apitrace? Let me know if there's something else I can attach to help fix this issue.
Is this a regression, i.e. did it work with an older snapshot of Mesa Git? If yes, can you bisect which commit introduced the problem?
It used to work a long time ago but I'm using Xorg edgers ppa, I'm not able to bisect it. But actually it might be related to bug 44647, because it starts to crash around the same time the videos started to show only garbage.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/505.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.