I doubt the public will tolerate an impaired Facebook experience, and a very large demographic still uses computers with only 1 gig of RAM.
Given Facebook's extreme and growing popularity (second only to Google) I suggest using older (real world) computers with less RAM to test this properly. His string of attempts to contact me only worsened the problem, and after about 3 minutes I was finally able to reply, but he was already gone. When I finally started hearing the much delayed notification "pop" Facebook uses, I remembered the familiar pattern was all too well.
Firefox 40.0.3 facebook crash full#
A friend's attempt to chat with me locked up everything for a full 30 seconds before I discovered what was going on. The worst system freeze occurred while working in another program (Word) with FF running only 6 tabs, 3 of which were Facebook pages. Using 3.6 RC1 today and this problem was an unmitigated disaster - similar to my earlier experience - only worse. If anyone else here has time, it would be great to get some help with that. Next steps i was going to try is finding a regression range on the nightlies between Fx3.5.5 and Fx3.5.6. WARNING: refusing to set request header: file /work/mozilla/builds/1.9.1/mozilla/content/base/src/nsXMLHttpRequest.cpp, line 2910 WARNING: Broadcasting loop!: file /work/mozilla/builds/1.9.1/mozilla/content/xul/document/src/nsXULDocument.cpp, line 1034 Not sure if this helps, but Tomcat notes the following warnings thrown:
Firefox 40.0.3 facebook crash mac os x#
On the receiving chat end (tomcat), he's running a 1.9.1 debug build on Mac 10.6: Mozilla/5.0 (Macintosh U Intel Mac OS X 10.6 en-US rv:1.9.1.8pre) Gecko/20100111 Firefox/3.5.8pre Result: the lagging stops and the CPU % dips under 50%Ģ) Switching to Fx3.5.5, and jit.content=TRUE. Using the same steps i've done back in comment 12.ġ) on Fx3.5.6, jit.content=FALSE. Tried again today on mac 10.6, and it's only repro'ing with Fx3.5.6 and jit.content enabled. Another is that the high CPU usage got slightly worse in 3.5.6 for some reason, enough to put some users over the lag threshold. One possibility is that the bug users are seeing is not what I laid out above. The hypothesis above doesn't explain the fact that this problem seems to have started in FF 3.5.6. But once it reaches 100%, things can start lagging and get worse and worse.) (As long as you are strictly below 100% CPU usage it should be OK. But if you are doing multiple chats, have open other FF tabs that use substantial amounts of CPU with JS or Flash, or have other apps running that are using CPU, then I can imagine the problem getting a lot more severe.
If your machine isn't doing too much else, it will probably not use up enough CPU to cause problems. If it is true that everyone else is seeing a variant of what I see, then I think what is happening is that FF uses a relatively high amount of CPU on the chat feature. If we stop typing, after several seconds the lagged messages areįinished, and then CPU usage goes back down to 20-40%. Messages are still being caught up on, FF will be unresponsive. If we keep typing while CPU is at 100%, the screen starts laggingīehind our typing. If it's just me typing, it maxes out around 70-80%. This happens much more easily if both parties are typing at Results: CPU usage starts at 20-40% and FF responds fine.Īs we keep typing messages rapidly, CPU usage rises past 80% toġ00%. Procedure: Open up FB chat with someone, and have both of us type lots of If anyone who has this bug can compare their symptoms to mine in detail, that would be greatly appreciated. I'll describe what I can get to happen below. We can make FF get kind of unresponsive by doing Facebook chat, but I'm not sure the detailed symptoms match. I may have spoken too soon when I said we can repro this. It seems that this problem started after Beta 5 or perhaps Beta 4. Specifics on the symptoms match those described elsewhere in this discussion, with the addition of the Facebook chat notification sound getting stuck repeating in a loop, which didn't used to happen. Still, Chrome is immune under the same conditions. Then again, over time I end up with a lot of tabs and other programs open too. Furthermore, if either machine runs Chrome and chats with the other running Firefox, the problem persists in the one running Firefox, but Chrome shows no symptoms.Īs for the amount of time before effects are felt, it's noticeable right away, but does seem to worsen over time. Neither has been upgraded to 3.5.6 at any time. Each also has 3.5.5 installed although they are never used.
Each machine experiences the FB chat lag while running 3.6b5. I'm getting the problem on two Dell laptops, one with 2 gigs of ram, the other with 768 megs. > Daniel: how long before the effects are felt? Al, Tony: can we get someone from QA looking into this, please?
0 kommentar(er)
