Bug 478958

It would be great to have backtrace from firefox process when it's running near 100% CPU...please try to attach gdb to the firefox by:

$gdb --pid=xxx where xxx is PID of firefox-bin. Then please run "bt" gdb command and attach output here...

note - you need to install debuginfo packages (xulrunner-debuginfo and firefox-debuginfo)

I have the two packages installed from the updates-debuginfo repo.  When I run Firefox, the only process is "firefox", so I'm assuming you mean that, not firefox-bin ("locate firefox-bin" turns up nothing).

ahh, okay, please try firefox then...

Created attachment 328262 [details]
requested backtrace

I found out how to reproduce the bug: go to

http://www.jigzone.com/puzzles/daily-jigsaw

and "Change Cut" to "247 Piece Triangles".  At this point, there's a good chance you'll see the behavior I've described if you try opening an URL in a new tab.

Should have mentioned that I'm using F10's built-in Java plugin.

(In reply to comment #6)
> I found out how to reproduce the bug: go to
> 
> http://www.jigzone.com/puzzles/daily-jigsaw
> 
> and "Change Cut" to "247 Piece Triangles".  At this point, there's a good
> chance you'll see the behavior I've described if you try opening an URL in a
> new tab.

Sorry, I don't get where I am supposed to type. Moreover, I get the similar behavior in Ekiga (or at least used to while it still worked for me), so I suspect that this might be more Gtk+ issue. However, I would still need a better description of how to reproduce this bug.

1. Go to http://www.jigzone.com/puzzles/daily-jigsaw
2. Wait for the puzzle to load.
3. Change Cut to 247 Piece Triangles.
4. Wait for the new puzzle to load.
5. Type Ctrl-t to open new tab.
5. Type some text for the URL, hopefully see it go in backwards.

I was able to reproduce this on my 32-bit machine, on the first attempt.

t): emit yreve tsomla ,yaw siht skrow i ,sey yllautcA

Meaning, yes I was able to reproduce it with

xulrunner-1.9.0.5-1.fc10.x86_64
firefox-3.0.5-1.fc10.x86_64
java-1.6.0-openjdk-plugin-1.6.0.0-7.b12.fc10.x86_64

[root@viklef ~]# LANG=C update-alternatives --display libjavaplugin.so.x86_64
libjavaplugin.so.x86_64 - status is auto.
 link currently points to /usr/lib/jvm/jre-1.6.0-openjdk.x86_64/lib/amd64/IcedTeaPlugin.so
/usr/lib/jvm/jre-1.6.0-openjdk.x86_64/lib/amd64/IcedTeaPlugin.so - priority 16000
Current `best' version is /usr/lib/jvm/jre-1.6.0-openjdk.x86_64/lib/amd64/IcedTeaPlugin.so.
[root@viklef ~]#

I can partly reproduce this on 64-bit Rawhide running as guest in VirtualBox 2.1.2.  The 100% CPU usage by Firefox is the same.  When I type text into the new tab, only the first character displays, then it won't let me enter any more.  So I can't tell if it would be backwards or not.

xulrunner-1.9.1-0.6.beta2.fc11.x86_64
firefox-3.1-0.4.beta2.fc11.x86_64
java-1.6.0-openjdk-plugin-1.6.0.0-8.b14.fc11.x86_64

the same on i386 client

Yes, can reproduce even with the upstream firefox binary. So, the only suspicion on the Fedora side could be openjdk webplugin.

Reassigning to its maintainers.

After letting the original puzzle load, the same thing happens if any of the other links "Shuffle Pieces", "Auto Solve", or "Start Over" is chosen instead of "Change Cut".

Unchanged with latest updates:

firefox-3.0.6-1.fc10.x86_64
java-1.6.0-openjdk-1.6.0.0-9.b14.fc10.x86_64

Same with latest Rawhide.  The fastest way to reproduce this is to use the "Start Over" button.

I can reproduce the issue with firefox even if Java is disabled. Here are the instructions (taken from http://www.bobafred.com/index.php/archive/firefox-and-google-maps-backwards-typing/):

1. Disable Java 
  - Edit -> Preferences -> Content -> uncheck "Enable Java"
  - double check that it is off through "about:plugins". There should be no entry for "IcedTea Java Web Browser Plugin"
2. Go to maps.google.ca
3. Click the 'Print' link. Wait for a new browser window and a print dialog to pop up (I didnt click anything in this window) 
4. Go back to the original firefox window. Try typing text in the address bar.

Given the above, I dont think this bug is caused by the IcedTea Plugin itself. Reassigning to firefox.

Reproduced with:
firefox-3.0.6-1.fc10.i386

I see the same with firefox-3.0.6-1.fc10.x86_64.  The behavior is the same with maps.google.com.  Unlike the other way, this does not trigger 100% CPU usage (whether Java is enabled or not), and if the 2 new windows are closed, the original window goes back to normal behavior without having to restart Firefox.

The behavior in Rawhide with firefox-3.1-0.6.beta2.fc11.x86_64 is similar to what it was on Jigzone - it only allows me to type one character, so I can't tell if it would be backwards or not.  As above, there is no 100% CPU usage, and if I close the extra windows, the original window goes back to normal without restarting Firefox.  So Firefox 3.1 is still buggy but in a slightly different way.

Martin, any idea here?

Behavior in F10 same with firefox-3.0.7-1.fc10.x86_64.

Bug #490257 also involves characters being inserted backwards in a text field (in xfig-plain).  Any connection?

Bug 490257 doesn't seem to be related to this issue...firefox uses GTK widgets there.

Behavior unchanged with firefox-3.0.10-1.fc10.x86_64 in F10, or firefox-3.5-0.20.beta4.fc11.x86_64 in rawhide.

In F11 with firefox-3.5.2-2.fc11.x86_64, it does the same thing it did in F11 Rawhide - it lets you type only one character.  The first time I tried it, this didn't happen, so I thought it was fixed, but trying it again I now see the bug consistently.  This is by going to maps.google.com and clicking the Print link.

The same bug also exists in F12 Rawhide with firefox-3.5.2-3.fc12.x86_64.  I reported it as bug #516371 against Rawhide.

*** Bug 516371 has been marked as a duplicate of this bug. ***

This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Seems fixed in Rawhide.  Can anyone verify?

firefox-3.6.1-0.2.b3.fc13.x86_64
xulrunner-1.9.2.1-0.3.b3.fc13.x86_64

I am not seeing this any more in cleanly installed and updated x86_64 F13.  Can anyone still reproduce it in F12?

This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.