Closed Bug 1305675 Opened 8 years ago Closed 6 years ago

Crash in shutdownhang | libpthread-2.23.so@0x89cd

Categories

(Core :: Graphics, defect, P2)

52 Branch
Unspecified
Linux
defect

Tracking

()

RESOLVED WONTFIX
Tracking Status
firefox49 --- unaffected
firefox50 --- unaffected
firefox51 --- unaffected
firefox52 --- unaffected
firefox53 --- fix-optional

People

(Reporter: marco, Unassigned)

References

Details

(Keywords: crash, regression, Whiteboard: tpi:+, gfx-noted)

Crash Data

Attachments

(2 files)

This bug was filed from the Socorro interface and is 
report bp-0d3a0452-eccb-4187-a042-547ad2160927.
=============================================================

I'm using an external monitor in a Mozilla office. Firefox is not working
well (sometimes icons are missing from the main menu, new tabs
are not opened, etc.).

Firefox doesn't close cleanly, so there's a shutdownhang.

https://crash-stats.mozilla.com/report/index/0d3a0452-eccb-4187-a042-547ad2160927
https://crash-stats.mozilla.com/report/index/793a0a1a-2994-4812-b197-4cbb32160927

Firefox 49 isn't affected.
This is only reproducible if Firefox is already running before I connect the
external monitor.
Priority: -- → P2
Whiteboard: tpi:+
Are 50/51 affected? Any chance you can try hunting this down via mozregression?
Flags: needinfo?(mcastelluccio)
I'm sorta wondering about bug 1088300 in that range. I guess we can see what happens now that it's been uplifted around.
Please check that disabling "Use hardware acceleration when available" works around the problems.
Component: Widget: Gtk → Graphics
Blocks: 1306912
Yes, it works correctly with hardware acceleration disabled.
Are 50/51 affected?
Flags: needinfo?(mcastelluccio)
Hardware acceleration is a Nightly-only feature for now, so I'll set 50 and 51 as unaffected.
Flags: needinfo?(mcastelluccio)
Blocks: 1317263
(In reply to Marco Castelluccio [:marco] from comment #0)
> This bug was filed from the Socorro interface and is 
> report bp-0d3a0452-eccb-4187-a042-547ad2160927.
> =============================================================
> 
> I'm using an external monitor in a Mozilla office. Firefox is not working
> well (sometimes icons are missing from the main menu, new tabs
> are not opened, etc.).
> 
> Firefox doesn't close cleanly, so there's a shutdownhang.
> 
> https://crash-stats.mozilla.com/report/index/0d3a0452-eccb-4187-a042-
> 547ad2160927
> https://crash-stats.mozilla.com/report/index/793a0a1a-2994-4812-b197-
> 4cbb32160927
> 
> Firefox 49 isn't affected.

During gfxPlatform Shutdown, it tried to post CleanUp Task to vsync thread. But I saw the vsync thread from these crash report was busying for [1]. Therefore, I guess the shutdown task couldn't perform and caused FF hang.

13 	libxul.so 	GLXVsyncSource::GLXDisplay::RunVsync 	gfx/thebes/gfxPlatformGtk.cpp:834
14 	libnspr4.so 	pt_PostNotifies 	nsprpub/pr/src/pthreads/ptsynch.c:106

[1]https://hg.mozilla.org/mozilla-central/annotate/29beaebdfacc/gfx/thebes/gfxPlatformGtk.cpp#l834
Whiteboard: tpi:+ → tpi:+, gfx-noted
Mason, do you have any idea why vsyncthread get stuck in gl::sGLXLibrary.xWaitVideoSync? Or this is driver related bug.
Flags: needinfo?(mchang)
Flags: needinfo?(mchang) → needinfo?(andrew)
Not sure we have the volume to worry about, possibly related to accelerated compositor on Linux.
Flags: needinfo?(andrew)
Closing because no crash reported since 12 weeks.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Closing because no crash reported since 12 weeks.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: