All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 75279] New: XCloseDisplay() takes one minute around nouveau_dri.so, freezing Firefox startup
Date: Thu, 20 Feb 2014 20:45:32 +0000	[thread overview]
Message-ID: <bug-75279-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 75279
          Assignee: dri-devel@lists.freedesktop.org
           Summary: XCloseDisplay() takes one minute around
                    nouveau_dri.so, freezing Firefox startup
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: bjacob@mozilla.com
               URL: https://bugzilla.mozilla.org/show_bug.cgi?id=973192
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: XOrg CVS
         Component: DRM/other
           Product: DRI

Hi, I'm just forwarding to you a bug report originally made against Firefox:
https://bugzilla.mozilla.org/show_bug.cgi?id=973192

The symptom is Firefox freezing on startup. The cause (see around comment
39--42 on that bug) is that a XCloseDisplay() call takes about one minute to
return.

The original reporter of the bug has recorded a profile which shows time spent
in nouveau_dri.so (see comments 50, 51 on the mozilla bug)

If you want to see what the application code triggering this bug looks like,
it's all self-contained in this file:

http://hg.mozilla.org/mozilla-central/file/tip/toolkit/xre/glxtest.cpp

   228   glXMakeCurrent(dpy, None, nullptr);
   229   glXDestroyContext(dpy, context);
   230   XDestroyWindow(dpy, window);
   231   XFreeColormap(dpy, swa.colormap);
   232   XCloseDisplay(dpy);  // <--- this XCloseDisplay call takes 1 minute
   233   dlclose(libgl);

Is there some more information that you need, that isn't already on the mozilla
bug?

Is this application code doing something evil here?

Is this a known issue? Do you have a guess as to whether it might affect many
users (i.e., should we try working around it)?

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

[-- Attachment #1.2: Type: text/html, Size: 3423 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-02-20 20:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20 20:45 bugzilla-daemon [this message]
2014-02-20 23:37 ` [Bug 75279] XCloseDisplay() takes one minute around nouveau_dri.so, freezing Firefox startup 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-75279-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 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.