CrashKill/2013-03-18: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 21: Line 21:


===Trunk===
===Trunk===
Several new topcrashes:
* {{bug|850741}} (js::AutoMaybeTouchDeadZones::AutoMaybeTouchDeadZones)
* {{bug|851806}} (js::ShapeTable::search)
* {{bug|851807}} (JSObject::setLastProperty)
* Already fixed: {{bug|851851}} (nsWindowSH::GlobalScopePolluterNewResolve)


==Mobile==
==Mobile==

Revision as of 16:35, 18 March 2013

General

Socorro

Flash

  • The newest 11.7 beta fixed the most grave crashes of the initial one, a few regressions still remain, mostly bug 849622, bug 851876.

Desktop

  • KaiRo did some investigation on increases of empty dump crashes, see bug 837835, looks like we regressed in 19 and again in 20.

Release

Beta

  • Fix for bug 787158 (SPDY) seems to have worked.
  • bug 798274 (gfxContext::PushGroupAndCopyBackground) is now rising somewhat on beta.
  • bug 836263 (Crossrider) has changed signature as expected and seems to be a bit lower in b5 than previously.

Aurora

  • bug 836951 (nsSecureBrowserUIImpl::MapInternalToExternalState) and bug 837370 (js::types::TypeCompartment::addPendingRecompile) seem to be somewhat declining even though no fix landed.

Trunk

Several new topcrashes:

  • bug 850741 (js::AutoMaybeTouchDeadZones::AutoMaybeTouchDeadZones)
  • bug 851806 (js::ShapeTable::search)
  • bug 851807 (JSObject::setLastProperty)
  • Already fixed: bug 851851 (nsWindowSH::GlobalScopePolluterNewResolve)

Mobile

B2G

  • Remember that we are - by design (mobile data costs) - only sending crash reports via wifi. QA people need to connect to wifi to send reports (queued up ones should all be sent in that case). We know we will not get many crash reports for users in Brazil where wifi is scarce.

Notes