Confirmed users
1,067
edits
Platform/InfallibleMalloc: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
=== Outcome === | |||
We don't have enough data to support inflicting a potential schedule slip with the additional work required for infallible malloc at this time. We decided that we should first fix the breakpad issues on windows so we get dumps in out of memory situations. This breakpad issue is keeping us from gathering the data to determine how we should prioritize infallible malloc. Once we have that data, we will then decide what to do in a future release, after Firefox 4. | |||
Best, | |||
Damon | |||
Dec 1, 2010 | |||
=== Meeting Notes === | |||
General Agenda: | General Agenda: | ||
* Discuss infallible malloc risks and payoffs. | * Discuss infallible malloc risks and payoffs. | ||
| Line 33: | Line 47: | ||
** have evidence that suggests it might not be dealing well with low memory | ** have evidence that suggests it might not be dealing well with low memory | ||
*** {{bug|615798}}: No symbols from OOM-abort backtrace | *** {{bug|615798}}: No symbols from OOM-abort backtrace | ||
*** {{bug| | *** {{bug|527095}}: Breakpad produces zero-byte or malformed dumps for some crashes | ||
** ergo, need to test breakpad in low-memory environments | ** ergo, need to test breakpad in low-memory environments, and might need {{bug|493779}}, {{bug|587729}} | ||