<< Weekly Status Report, W29/2012 | The roads I take... | Integration eines Magento-2-Webshops mit FreeFinance und selbstgebautem Warenmanagement >>
Weekly Status Report, W30/2012
Here's a short summary of Mozilla-related work I've done in week 30/2012 (July 23 - 29, 2012):
If you are on Windows 7 or Vista and seeing stability problems with Flash, please update to their newest version (currently 11.3.200.268) and if the issues persist, please try to find reliable steps how to reproduce the problems. Report those to us, we are working with Adobe so they can fix their plugin, but it much easier for them to find solutions if they can reproduce the crashes or hangs themselves.
- CSI:Mozilla / CrashKill:
Once again, had a lot of discussions on Flash 11.3 stability. This continues to be our greatest concern in overall Firefox stability, even though the problems lie entirely on Adobe's side. Several people on our side continue working with people on their side to improve the situation. Adobe released an update with some improvements at the end of the week.
Kept track of another not-so-successful try to switch the system for running regular Socorro jobs.
Discussed how we can improve getting info about Android crashes to developers, and filed a bug on exposing some more info.
Filed a bug on losing browser-side hang specificity again on Firefox 16 and up.
Also continued following B2G crash reporting progress. The basic mechanics have landed, but there's quite a few additional pieces that need to be put together.
As usual, watched new/rising crashes, caring that bugs are filed where needed. - Various Discussions/Topics:
Localizing B2G, crashes with SeaMonkey and Thunderbird mail compose, B2G status bar icons, etc.
If you are on Windows 7 or Vista and seeing stability problems with Flash, please update to their newest version (currently 11.3.200.268) and if the issues persist, please try to find reliable steps how to reproduce the problems. Report those to us, we are working with Adobe so they can fix their plugin, but it much easier for them to find solutions if they can reproduce the crashes or hangs themselves.
Entry written by KaiRo and posted on August 1st, 2012 18:07 | Tags: L10n, Mozilla, SeaMonkey, Status | no comments | TrackBack
Comments
No comments found.