User Agent: Mozilla/5.0 (Windows NT 6.1; rv:12.0) Gecko/20100101 Firefox/12.0 Build ID: 20120420145725 Steps to reproduce: Hit "reply" in Gmail. I believe I've done this with the mouse and with the autokey. I believe that the first time I hit "reply" I don't have this problem, but then after hitting reply for a second email, it occurs. Actual results: The window for composing the reply appears, but no box to enter text. And a notice saying "loading rich text fonts..." Then it just hangs. Other tabs in firefox work just fine; i.e., FF is not crashing. Windows also is fine. The problem does not occur in Chrome. Expected results: The compose screen should load. If I close firefox 13.0 and open it, it works once and then the hanging issue occurs again. I have gmelius as a plugin. I have uninstalled firefox 13.0 beta and installed FF 12 on one computer but can test it on two other computers that have firefox 13 installed if I hear from you soon. Otherwise will uninstall FF 13 and install 12 on those computers as well. If you can give detailed instructions on how to collect debugging information (or a link to such information), I can try to do that for you. Thanks.
I tried it in safemode, and the problem still occurred. I also found that the problem occurred with Firefox 12. And I think that I know why it was hanging--I use POP to import email from another account, and there was a file attachment that was larger than 20MB on it. Gmail was giving me an error message for that account. Once I noticed the error message, figured out what it meant, and deleted the large attachment on the email account that I was retrieving messages from, gmail stopped hanging in firefox.
Hello, I just found this 2 years old report, but I'm not sure if your last comment is an information that this should be closed? in my opinion this sounds like the problem was on gmail site? thanks for an short update
Closed -> no feedback from reporter. please feel free to reopen this report if you have new or additional information. thank you for your help.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.