We stop pushing updates for 3.6.14 because it breaks many Java applets (especially Pogo.com games). It was also crashier. We'll be respinning builds soon with those two fixes and pushing out 3.6.15
For Firefox 4:
We have closed the last blockers and unless anything new shows up RCs will start building soon and release in a week. Assuming that no new issues are found, we'll release the RC as final soon after that. The major issue that we've seen is that Hotmail doesn't work. This has been fixed by the Hotmail team and they're rolling out updates to their site this week.
Please ask me if you have any other questions about either of these. I'll try to post updates when I can.
First for 3.6.14:
We stop pushing updates for 3.6.14 because it breaks many Java applets (especially Pogo.com games). It was also crashier. We'll be respinning builds soon with those two fixes and pushing out 3.6.15
For Firefox 4:
We have closed the last blockers and unless anything new shows up RCs will start building soon and release in a week. Assuming that no new issues are found, we'll release the RC as final soon after that. The major issue that we've seen is that Hotmail doesn't work. This has been fixed by the Hotmail team and they're rolling out updates to their site this week.
Please ask me if you have any other questions about either of these. I'll try to post updates when I can.
The crash daily rate is not good: 2.33% in Firefox 4 Beta 12 (2M users) vs. 0.13% in Firefox 3.6.13 (100M users), that is a ratio of 18.
Do you think it will drop for statistical reasons (50 times more users, CDR of 0.18% in Firefox 3.6.3 with 3M users)?
The crash daily rate is not good: 2.33% in Firefox 4 Beta 12 (2M users) vs. 0.13% in Firefox 3.6.13 (100M users), that is a ratio of 18.
Do you think it will drop for statistical reasons (50 times more users, CDR of 0.18% in Firefox 3.6.3 with 3M users)?
There are lots of complaints on the support forum regarding pogo.com from users with 3.6.14.
Any time estimate on 3.6.15 to correct the problem?
See my post in the support forum: https://support.mozilla.com/en-US/questions/788623#answer-142538
I have been testing 3.6.15 release candidate build 1 on a couple of pogo games and so far it looks OK. It appears Mozilla are on course for another quick turn around with this fix.
I have been testing 3.6.15 release candidate build 1 on a couple of pogo games and so far it looks OK. It appears Mozilla are on course for another quick turn around with this fix.
After the first complaints about pogo.com and 3.6.14, I went to pogo as a "guest" and experienced no problems with 3.6.14. I wonder if some of the complaints are being caused by a conflict with something else users have installed or perhaps need to update Java?
Thanks TonyE.
After the first complaints about pogo.com and 3.6.14, I went to pogo as a "guest" and experienced no problems with 3.6.14. I wonder if some of the complaints are being caused by a conflict with something else users have installed or perhaps need to update Java?
The support forum is being flooded with users experiencing the same problem with pogo.com. Is there a way to get this issue mentioned on the support home page (http://support.mozilla.com) or in the AAQ wizard so that users know that a fix is on the way?
The support forum is being flooded with users experiencing the same problem with pogo.com. Is there a way to get this issue mentioned on the support home page (http://support.mozilla.com) or in the AAQ wizard so that users know that a fix is on the way?
Is there a way to get this issue mentioned on the support home page (http://support.mozilla.com) or in the AAQ wizard so that users know that a fix is on the way?
Put a reference to bug 629030 in support questions with this issue.
''Is there a way to get this issue mentioned on the support home page (http://support.mozilla.com) or in the AAQ wizard so that users know that a fix is on the way?''
Put a reference to [https://bugzilla.mozilla.org/show_bug.cgi?id=629030 bug 629030] in support questions with this issue.
Put a reference to bug 629030 in support questions with this issue.
Since this is such a widespread problem, I was actually hoping to proactively inform the users about it and reduce their sense of dissatisfaction with this upgrade. As a bonus, the contributors would be freed up to answer other posts.
''Put a reference to bug 629030 in support questions with this issue.''
<BR><BR>Since this is such a widespread problem, I was actually hoping to proactively inform the users about it and reduce their sense of dissatisfaction with this upgrade. As a bonus, the contributors would be freed up to answer other posts.
Thanks Michael. I see that this article now shows up on the support home page. It really helps to alleviate the pain for users and contributors to a great extent.
Thanks Michael. I see that this article now shows up on the support home page. It really helps to alleviate the pain for users and contributors to a great extent.
The Java problem is not fixed in 3.6.15 RC1. See https://bugzilla.mozilla.org/show_bug.cgi?id=629030#c38.
See also this [https://support.mozilla.com/en-US/forums/knowledge-base-articles/705154?#post-10089 Pogo article thread post].
You get the same problem with the STR from comment 38 on other browsers. I tested it on Safari, Chrome, Opera and IE and had the same problem with the bottom half being grey. That one appears to be a problem with the site rather than this bug.
scoobidiver wrote:<blockquote>The Java problem is not fixed in 3.6.15 RC1. See https://bugzilla.mozilla.org/show_bug.cgi?id=629030#c38. </blockquote>
You get the same problem with the STR from comment 38 on other browsers. I tested it on Safari, Chrome, Opera and IE and had the same problem with the bottom half being grey. That one appears to be a problem with the site rather than this bug.
The crash daily rate is not good: 2.33% in Firefox 4 Beta 12 (2M users) vs. 0.13% in Firefox 3.6.13 (100M users), that is a ratio of 18.
The Firefox 3.6 figure was wrong because there was a throotle of 10%.
The last data gives a crash daily rate of 2.61% in 4.0 vs. 1.79% in 3.6.16. In 4.0, lots of crashes are caused by malwares, some specific extensions, peer-to-peer and anti-virus softwares.
''The crash daily rate is not good: 2.33% in Firefox 4 Beta 12 (2M users) vs. 0.13% in Firefox 3.6.13 (100M users), that is a ratio of 18.''
The Firefox 3.6 figure was wrong because there was a throotle of 10%.
The last data gives a crash daily rate of 2.61% in 4.0 vs. 1.79% in 3.6.16. In 4.0, lots of crashes are caused by malwares, some specific extensions, peer-to-peer and anti-virus softwares.
