public inbox for dri-devel@lists.freedesktop.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 77745] New: [r600g] Call of Dutty 4 crashes under Wine due to running out of memory
Date: Mon, 21 Apr 2014 20:57:59 +0000	[thread overview]
Message-ID: <bug-77745-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1862 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=77745

          Priority: medium
            Bug ID: 77745
          Assignee: dri-devel@lists.freedesktop.org
           Summary: [r600g] Call of Dutty 4 crashes under Wine due to
                    running out of memory
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: jaimerave@gmail.com
          Hardware: Other
            Status: NEW
           Version: git
         Component: Drivers/Gallium/r600
           Product: Mesa

Created attachment 97706
  --> https://bugs.freedesktop.org/attachment.cgi?id=97706&action=edit
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

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3297 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2014-04-21 20:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-21 20:57 bugzilla-daemon [this message]
2014-04-22  0:06 ` [Bug 77745] [r600g] Call of Duty 4 crashes under Wine due to running out of memory bugzilla-daemon
2014-04-22  6:22 ` bugzilla-daemon
2014-04-22 14:04 ` bugzilla-daemon
2014-04-22 14:04 ` bugzilla-daemon
2014-04-22 14:05 ` bugzilla-daemon
2014-04-22 14:08 ` bugzilla-daemon
2014-04-22 14:08 ` bugzilla-daemon
2014-04-23  7:57 ` bugzilla-daemon
2014-07-30 18:22 ` bugzilla-daemon
2019-09-18 19:15 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-77745-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox