* should we spend time telling users that Safe Mode might fix their problem?
** beltzner felt that we could, but ultimately it's not as satisfying as either the Chrome solution (a crash doesn't take down the entire browser) or having the problem fixed on our side
=== Bugs ===
* cooliris19.dll@0x351f2 - jst {{bug|519039}}
+
-
* nsCycleCollectingAutoRefCnt::decr(nsISupports*) - dbaron {{bug|500879}}
+
-
* nsGlobalWindow::cycleCollection::UnmarkPurple(nsISupports*) - dbaron {{bug|504392}}
+
-
* nsEventListenerManager::Release() - jst {{bug|513334}}
+
-
* UserCallWinProcCheckWow - {{bug|501429}}, - jst
+
-
* PR_MD_SEND - {{bug|489533}} - Jonas
+
-
* RtlpWaitForCriticalSection - Flash - JST {{bug|511757}}
+
-
* RtlpWaitOnCriticalSection - JST - Not Flash, something else. {{bug|511759}}
+
-
* @0x0 - bug {{bug|}} - Needs a tracking bug. Will get Jeff to file.
+
-
* nsStyleSet::FileRules(int (*)(nsIStyleRuleProcessor*, void*), RuleProcessorData*) - {{bug|492675}} - Bug is real, dbaron owns.
+
-
* _woutput_l - {{bug|511756}} - dolske
+
-
* KiFastSystemCallRet {{bug|514589}} - Jonas
+
-
* NPSWF32.dll@0x77bd0 - Farmtown flash - JST
+
-
* GraphWalker::DoWalk(nsDeque&) {{bug|500105}} - peterv
+
-
* nsWindow::GetParentWindow(int) - {{bug|470487}} - jst