<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [NV30/gallium] Mozilla apps freeze on startup with nouveau-dri-10.2.1 libs on dual-screen" href="https://bugs.freedesktop.org/show_bug.cgi?id=79823#c33">Comment # 33</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [NV30/gallium] Mozilla apps freeze on startup with nouveau-dri-10.2.1 libs on dual-screen" href="https://bugs.freedesktop.org/show_bug.cgi?id=79823">bug 79823</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>(In reply to <a href="show_bug.cgi?id=79823#c31">comment #31</a>) > Created <a href="attachment.cgi?id=101350" name="attach_101350" title="GDB log with "dup fd..." patch">attachment 101350</a> <a href="attachment.cgi?id=101350&action=edit" title="GDB log with "dup fd..." patch">[details]</a> > GDB log with "dup fd..." patch > > It works! Great! Also I just figured out why this is happening to you and not to anyone else. It's the dual screens! (Who uses separate screens anyways...) src/glx/glxext.c allocates a screen per... screen. And then when it cleans up, it deletes the screens in the same order it created them. So it's precisely the scenario I outlined, where by the time the second screen goes to be destroyed, the fd it relies on (which is the first one) has already been closed. I'll push this patch out and tag it for 10.2.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>