All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 75361] freeze in Mass Effect 3 (wine)
Date: Wed, 26 Feb 2014 07:14:25 +0000	[thread overview]
Message-ID: <bug-75361-502-LaJoCvapUW@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-75361-502@http.bugs.freedesktop.org/>


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

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

--- Comment #10 from Michel Dänzer <michel@daenzer.net> ---
(In reply to comment #9)
> apitrace replay freeze w at the end trace when obscure screen with ships and
> planet. Absolutely also as game.

Hmm. I do see a little freeze at the end of the trace, but only for about three
seconds, then it exits normally.


> After kill game process - Xorg 100% working.

So, does the freezing process hog the CPU?

If you don't kill the freezing process, does it remain frozen forever, or does
it recover or fail somehow after a while?

Can you attach gdb to the freezing process and get a backtrace? Probably best
to attempt this from ssh, but switching to console and doing it from there
might be fine as well.


Does it still happen with current LLVM SVN and Mesa Git? What configure options
do you use for building LLVM and Mesa?

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

[-- Attachment #1.2: Type: text/html, Size: 1845 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

  parent reply	other threads:[~2014-02-26  7:14 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-22 10:19 [Bug 75361] New: freeze in Mass Effect 3 (wine) bugzilla-daemon
2014-02-22 10:21 ` [Bug 75361] " bugzilla-daemon
2014-02-23  7:59 ` bugzilla-daemon
2014-02-24  5:59 ` bugzilla-daemon
2014-02-24 12:40 ` bugzilla-daemon
2014-02-24 12:40 ` bugzilla-daemon
2014-02-24 12:41 ` bugzilla-daemon
2014-02-24 12:46 ` bugzilla-daemon
2014-02-24 16:34 ` bugzilla-daemon
2014-02-25  7:26 ` bugzilla-daemon
2014-02-25 17:41 ` bugzilla-daemon
2014-02-26  7:14 ` bugzilla-daemon [this message]
2014-02-26 17:16 ` bugzilla-daemon
2014-02-26 17:16 ` bugzilla-daemon
2014-02-27  7:21 ` bugzilla-daemon
2014-02-27 16:32 ` bugzilla-daemon
2014-03-04  6:51 ` bugzilla-daemon
2014-03-04 15:40 ` bugzilla-daemon
2014-04-17 19:29 ` bugzilla-daemon
2014-04-17 21:48 ` bugzilla-daemon
2014-04-28 20:52 ` bugzilla-daemon
2014-04-29 21:38 ` bugzilla-daemon
2014-04-30 12:44 ` bugzilla-daemon
2014-04-30 12:45 ` bugzilla-daemon
2014-04-30 14:17 ` bugzilla-daemon
2014-05-16 19:29 ` bugzilla-daemon
2014-05-17  3:02 ` bugzilla-daemon
2014-05-24  5:31 ` bugzilla-daemon
2014-05-24  5:32 ` bugzilla-daemon
2014-05-24  5:38 ` bugzilla-daemon
2015-02-06  1:35 ` 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-75361-502-LaJoCvapUW@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.