After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 620850 - npviewer.bin uses 100% CPU when visiting gmail with epiphany, browser becomes unresponsive on close
npviewer.bin uses 100% CPU when visiting gmail with epiphany, browser becomes...
Status: RESOLVED NOTGNOME
Product: epiphany
Classification: Core
Component: General
2.30.x
Other Linux
: Normal major
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-06-07 15:11 UTC by Jeremy Nickurak
Modified: 2011-02-01 17:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jeremy Nickurak 2010-06-07 15:11:51 UTC 
Steps to reproduce:

- Open gmail in the epiphany, on a 64-bit machine using 32-bit flash.
- Observer npviewer.bin taking a lot of CPU (bad, but not fatal)
- Open a new tab, and then close the tab hosting gmail

Expected results:

- CPU usage decreases, browser continues working right


Observed results:

- CPU usage increases, browser becomes unresponsive.

Other notes:

- Firefox with the same plugin configuration is unaffected
- When using 64-bit flash without npviewer.bin, epiphany segfaults.

Downstream bug: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/508980
Comment 1 Diego Escalante Urrelo (not reading bugmail) 2011-02-01 17:54:23 UTC 
Thanks for taking the time to report this bug.
However, this application does not track its bugs in the GNOME Bugzilla. We kindly ask you to report the bug to the application authors. For a selective list of other bug tracking systems please consult http://live.gnome.org/Bugsquad/TriageGuide/NonGnome.

If the affected third party application has a bug tracking system you should investigate whether a bug for the reported issue is already filed in this system. If it has not been filed yet please do so. Also ensure that both bug reports contain a link to each other.
Thanks in advance!