How is the stability of Firefox changing in the long run?
The official version was released on March 18Firefox 28But how is the stability of Firefox updating many times a year changed each time? So with regard to the desktop version and the Android version of Firefox beta & official version, the transition of crash rate & freeze rate from 2011 to the present is released.
Home of KaiRo: How Effective is the Mozilla Stability Program?
I surveyed in cooperation with MozillaKaiser RobertMr. In order to investigate the stability of Firefox for desktop version and Firefox for Android, Robert measured on how many times out of 100 requests sent from Firefox the crash occurred on a daily basis.
That is why the crash rate of the desktop version Firefox from October 2011 to March 5, 2014. The horizontal axis shows the elapsed time and the vertical axis shows the crash rate.
Blue graph is browser and content crash rate, red graph is plugin crash rate, yellow graph is plugin freeze rate. The freeze rate is the rate at which the plug-in did not move for more than 45 seconds and the process was interrupted halfway.
The first thing you can see from the graph is that the crash rate on weekends is high. This means that many people use the Internet at weekends, or that ADI data is not as accurate as expected.
In addition, almost everyone who opened Google due to a Google Doodle bug in August 2012 experienced a crash, but the figures at that time are also reflected in the graph firmly. Likewise, when Flash 11.3 is released in June 2012, you can see that the plug-in crash rate and freeze rate are rising as well.
Apart from sudden events, in many cases browser crash rate seems to be kept constant as a line of "one out of 100", but in January 2013 suddenly crash rate of browser I draw a mountain. Firefox 18.0.2 was released to solve this crash, but again in February the graph turned into a mountain. This is a released Firefox 19.0AMDBecause it triggered a bug in the CPU of Firefox 19.0.1 was released soon.
Overall, the graph keeps a line of 1.0, which did not change when Firefox 26 was released in December 2013. In other words, even if you add a lot of code to support new features, you can say that the Mozilla Stability Program works properly so that it does not crash.
Next, FirefoxBeta versionLet's see the data.
Firefox strives to increase the stability of the beta version from 2012, but looking at the graph, the stability is still lower than the official version.
To make sure that there is no problem for the official release in the beta version, it is natural that the graph is swaying greatly. For example, in December of 2013 the stability was slightly lower, but since it was restoring slowly, it is not so noticeable on the graph. But Firefox 28, released in February 2014, was once again less stable and after a restoration saw a bigger recession. This was released in mid-February Beta 4. About two weeks have passed since the recession peaked, and it finally approached the line of 1.0. In this way in the beta many timesRegression testSo when Firefox 28 was officially released, no major problems occurred.
Next, I will look at the Android version of Firefox.
Although it is a high crash rate that is not comparable with the desktop version at the beginning of the release, it gradually stabilizes as the days go by. A new version was released about every 6 weeks, and in September of 2013 I improved the stability considerably, but the stability became low again in the months ahead. As a result, in January 2014 Mozilla started a new attempt to improve stability, and stability was improved slightly from the time Firefox 27 was released. However, compared with the desktop version, there is still room for improvement.
And this is about the beta version of Firefox for Android. The vertical axis has changed greatly, while the highest value of the official version was 4, the beta version is 11.
The stability of Firefox officially released compared with the desktop version of Firefox which keeps only one crash in ADI 100 is low, but the beta version is more amazing than that. The retreat of Firefox officially released in late 2013 was quite big, but it is still not much worse than the beta version. However, after 2012 regression tests have been carried out many times, and the graph continues to calm down gradually by continuing repairing the bug. Again, a cycle of six weeks has been seen, and a new stability improvement effort that began in 2014 has been successful and we are getting the highest stability ever. If you predict from the graph, you should expect the numerical value of Firefox 28 for Android.
in Software, Posted by logq_fa