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

Status: RESOLVED WONTFIX

(Core :: Graphics, defect, P2)

Description

[Marco Castelluccio [:marco]]

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.

Comment 1

[Marco Castelluccio [:marco]]

Attachment: Icons missing from main menu

Comment 2

[Marco Castelluccio [:marco]]

Attachment: Firefox doesn't correctly detect the size of the screen?

Comment 3

[Marco Castelluccio [:marco]]

This is only reproducible if Firefox is already running before I connect the
external monitor.

Comment 4

[Ryan VanderMeulen [:RyanVM]]

Are 50/51 affected? Any chance you can try hunting this down via mozregression?

Comment 5

[Marco Castelluccio [:marco]]

It looks like it isn't reliably reproducible, given the result: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=88dd53397d30e1853122f1284de94f103f6e4436&tochange=f514d79fe0679a7c565bacc90b2d21e62cbf8de2

The range for mozilla-central:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=38d0defa2db77fa8bf209cf60bde4232896660cc&tochange=63d190efe42e5e4984180d315e16b70f6d99618c

Comment 6

[Ryan VanderMeulen [:RyanVM]]

I'm sorta wondering about bug 1088300 in that range. I guess we can see what happens now that it's been uplifted around.

Comment 7

[Karl Tomlinson (:karlt)]

Please check that disabling "Use hardware acceleration when available" works around the problems.

Comment 8

[Marco Castelluccio [:marco]]

Yes, it works correctly with hardware acceleration disabled.

Comment 9

[Ryan VanderMeulen [:RyanVM]]

Are 50/51 affected?

Comment 10

[Marco Castelluccio [:marco]]

Hardware acceleration is a Nightly-only feature for now, so I'll set 50 and 51 as unaffected.

Comment 12

[Peter Chang[:pchang]]

(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

Comment 13

[Peter Chang[:pchang]]

Mason, do you have any idea why vsyncthread get stuck in gl::sGLXLibrary.xWaitVideoSync? Or this is driver related bug.

Comment 14

[Milan Sreckovic [:milan] (needinfo for best results)]

Not sure we have the volume to worry about, possibly related to accelerated compositor on Linux.

Comment 15

[Sylvestre Ledru [:Sylvestre]]

Closing because no crash reported since 12 weeks.

Comment 16

[Sylvestre Ledru [:Sylvestre]]

Closing because no crash reported since 12 weeks.