Bug 857980 - (firefox:4042): Gdk-WARNING **: XID collision, trouble ahead
(firefox:4042): Gdk-WARNING **: XID collision, trouble ahead
Status: CLOSED CANTFIX
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: firefox (Show other bugs)
6.3
All Linux
unspecified Severity medium
: rc
: ---
Assigned To: Red Hat Gecko Maintainer
Desktop QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-09-17 12:43 EDT by xset1980
Modified: 2012-11-16 10:57 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-11-16 10:57:08 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description xset1980 2012-09-17 12:43:13 EDT
Description of problem:

Firefox 10 ESR on Scientific Linux 6.3, hang out (not ever) and i can see this message on terminal (opening firefox from terminal using firefox or firefox -safe-mode), and the cpu usage is 50%

Version-Release number of selected component (if applicable):

Name        : firefox                      Relocations: (not relocatable)
Version     : 10.0.7                            Vendor: Scientific Linux
Release     : 1.el6_3                       
=============================================================

Name        : glibc                        Relocations: (not relocatable)
Version     : 2.12                              Vendor: Scientific Linux
Release     : 1.80.el6_3.5                  
=============================================================

Name        : gtk2                         Relocations: (not relocatable)
Version     : 2.18.9                            Vendor: Scientific Linux
Release     : 10.el6                        
=============================================================
Name        : gtk+                         Relocations: (not relocatable)
Version     : 1.2.10                            Vendor: Scientific Linux
Release     : 70.el6                        


How reproducible:

Always

Steps to Reproduce:
1.Open a gnome-terminal and type firefox and enter taringa.net on URL bar
2.Right click on "top post section" or only open http://www.taringa.net/posts/info/15577126/El-asombroso-caso-de-los-DNI-_truchos_-de-la-AFIP.html
3. Show on console a lot of

(firefox:4042): Gdk-WARNING **: XID collision, trouble ahead

  
Actual results:

Firefox hang out some times and cpu usage of 50%

Expected results:


Additional info:
Comment 1 xset1980 2012-09-17 12:51:32 EDT
Disabling flash plugin, the error is fixed. So?
Comment 3 xset1980 2012-09-17 22:01:38 EDT
Disabling flash or using flashblock on firefox is solved. So, is a bug of flash or firefox + flash or other thing?

flash info:

Name        : flash-plugin                 Relocations: (not relocatable)
Version     : 11.2.202.238                      Vendor: Adobe Systems Inc.
Release     : release                       Build Date: vie 10 ago 2012 22:45:38 ART
Install Date: lun 17 sep 2012 14:12:10 ART      Build Host: frbld_lnx_016.macromedia.com
Group       : Applications/Internet         Source RPM: flash-plugin-11.2.202.238-release.src.rpm
Size        : 18383579                         License: Commercial
Signature   : DSA/SHA1, mar 14 ago 2012 13:06:55 ART, Key ID 3a69bd24f6777c67
Packager    : Adobe Systems Inc.
URL         : http://www.adobe.com/downloads/
Summary     : Adobe Flash Player 11.2
Description :
Adobe Flash Plugin 11.2.202.238
Fully Supported: Mozilla SeaMonkey 1.0+, Firefox 1.5+, Mozilla 1.7.13+
Comment 4 Martin Stransky 2012-11-16 10:57:08 EST
It's a bug in flash-plugin. Flash plugin is run in external process (plugin-container or nspluginwrapper) so we don't care if it crashes or not. It should not affect firefox itself.

If firefox hangs, please attach a bactrace (http://fedoraproject.org/wiki/Debugging_guidelines_for_Mozilla_products#Application_freeze)

Note You need to log in before you can comment on or make changes to this bug.