Yuri Konotopov Reporter
	Description • 7 years ago

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.98 Safari/537.36

Steps to reproduce:

Installed GNOME Shell integration [1] browser extension on Ubuntu 16.04



Actual results:

Firefox consumes a lot of CPU and crash on exit.


Expected results:

No crash should occure.

This was twice [2][3] repored against GNOME Shell integration browser extension. However I can not reproduce this by myself.

Debugging in [2] we found that native host messaging app exits normally. Also there are no problems with Chromium.

I attached Firefox console output provided by users.

This may be related to [4] or [5].

[1] https://addons.mozilla.org/firefox/addon/gnome-shell-integration
[2] https://github.com/nE0sIghT/chrome-gnome-shell-mirror/issues/49
[3] https://github.com/nE0sIghT/chrome-gnome-shell-mirror/issues/53
[4] https://bugzilla.mozilla.org/show_bug.cgi?id=1337799
[5] https://bugzilla.mozilla.org/show_bug.cgi?id=1342850

	Yuri Konotopov Reporter
	Comment 1 • 7 years ago

Crash log from another user

	Yuri Konotopov Reporter
	Comment 3 • 7 years ago

I'm clearing duplicate state since this issue is reproducible with my fully updated Gentoo system.
I reproduced this issue both with current stable and developer versions.

Steps to reproduce:

1. Install GNOME Shell integration browser extension [1]
2. Install native host messaging connector [2]
3. Open browser with "-jsdebugger" option. Without this option issue occurs from time to time.
4. Close browser

Expected results:
Browser closed normally.

Actual results:
Browser process consumes a lot of CPU cycles and crash.

	Yuri Konotopov Reporter
	Comment 4 • 7 years ago

Attached crash report

	Yuri Konotopov Reporter
	Comment 5 • 7 years ago

Also there are 274 same crash reports was submitted: https://crash-stats.mozilla.com/signature/?product=Firefox&signature=AsyncShutdownTimeout%20%7C%20profile-before-change%20%7C%20Native%20Messaging%3A%20Wait%20for%20application%20org.gnome.chrome_gnome_shell%20to%20exit%2CNative%20Messaging%3A%20Wait%20for%20application%20org.gnome.chrome_gnome_shell%20to%20exit%2CNative%20Messaging%3A%20Wait%20for%20application%20org.gnome.chro...&date=%3E%3D2017-01-01T17%3A28%3A00.000Z&date=%3C2017-04-25T17%3A28%3A00.000Z&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&_columns=install_time&_sort=-date&page=1#summary

	Yuri Konotopov Reporter
	Comment 7 • 7 years ago

Updated steps to reproduce:

1. Install GNOME Shell integration browser extension [1]
2. Install native host messaging connector [2]
3. Open browser with "-jsdebugger" option. Without this option issue occurs from time to time.
4. Close browser

Expected results:
Browser closed normally.

Actual results:
Browser process consumes a lot of CPU cycles and crash.

[1] https://addons.mozilla.org/firefox/addon/gnome-shell-integration/
[2] https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome/Installation

	Yuri Konotopov Reporter
	Comment 8 • 7 years ago

Last month there were > 1000 crash reports with Native messaging (and about 50% of them are GNOME Shell integration WebExtension).

https://crash-stats.mozilla.com/search/?signature=~Native%20Messaging%3A%20Wait%20for%20application&date=%3E%3D2017-05-20T16%3A06%3A26.000Z&date=%3C2017-06-20T16%3A06%3A26.000Z&_sort=-date&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#crash-reports

	fermulator
	Comment 9 • 7 years ago

What can I do to help? This bug is a doozey; it's wasting so many CPU cycles and power in the world for anyone using this plugin (most people aren't probably noticing anything is wrong until they see the crash upon trying to close Firefox)

	fermulator
	Comment 10 • 7 years ago

(In reply to fermulator from comment #9)
> What can I do to help? This bug is a doozey; it's wasting so many CPU cycles
> and power in the world for anyone using this plugin (most people aren't
> probably noticing anything is wrong until they see the crash upon trying to
> close Firefox)

FYI I have some OS data here https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1576581
(although Yuri's report is far more useful with the technical crash data and logs)

	Paul [pwd]
	Comment 11 • 6 years ago

IS this on anyone from Mozilla's radar?

	Yuri Konotopov Reporter
	Comment 12 • 6 years ago

Looks like this issue was fixed around version 55.
Only 52 ESR users are affected.