From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@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 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0479280840==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 875FBF9DD5 for ; Thu, 20 Feb 2014 12:45:32 -0800 (PST) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces@lists.freedesktop.org Errors-To: dri-devel-bounces@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0479280840== Content-Type: multipart/alternative; boundary="1392929132.B73Bc0.779"; charset="us-ascii" --1392929132.B73Bc0.779 Date: Thu, 20 Feb 2014 20:45:32 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" 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. --1392929132.B73Bc0.779 Date: Thu, 20 Feb 2014 20:45:32 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"
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.
--1392929132.B73Bc0.779-- --===============0479280840== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============0479280840==--