Closed Bug 580375 Opened 14 years ago Closed 14 years ago

Land Breakpad patch from r626 in mozilla-central

Categories

(Toolkit :: Crash Reporting, defect)

x86
macOS
defect
Not set
critical

Tracking

()

RESOLVED WONTFIX
Tracking Status
blocking2.0 --- -

People

(Reporter: joduinn, Assigned: ted)

Details

Attachments

(1 file, 1 obsolete file)

In https://bugzilla.mozilla.org/show_bug.cgi?id=577431#c30, jimb got upstream fixes in place for better memory usage.

We need to pickup these upstream patches to get 10.6 build symbols.
Blocks: 571367, 576053
blocking2.0: --- → ?
This was last done in bug#567424 by Ted. He's out right now - anyone else who can do this?
Severity: normal → critical
Assignee: nobody → joshmoz
Ted's coming back tomorrow (Wed July 21).
Assignee: joshmoz → ted.mielczarek
I'm backed up from vacation and this is important, so I think we should land just Jim's patch in m-c. It's not as bad as taking a local patch since it's already upstreamed. I've got all our other local patches in the issue tracker, but not actually landed upstream, so there's still a little pain involved.
Assignee: ted.mielczarek → joshmoz
Summary: update Breakpad to include upstream Breakpad fixes → Land Breakpad patch from r626 in mozilla-central
Attached patch fix v1.0 (obsolete) — Splinter Review
Attachment #459069 - Attachment is obsolete: true
(In reply to comment #5)
> Created attachment 459070 [details] [diff] [review]
> fix v1.0 (against mozilla tree)

r=me if you need it.
I ran this through the try server with the patch from bug 576053 to enable crashreporter and we had the same problem. This wasn't enough to fix it.

We need to find out if upping the RAM to 2 GB fixes the problem. If it does then we at least know for sure that we're dealing with a memory shortage which causes things to run so slowly that we time out.
I found a 10.6 mini with 2G of RAM to test on, but we don't have the pile of other 2G machines to re-purpose I thought we did.
Since this is heading a hardware direction I'm going to continue the discussion over in bug 577431.
blocking2.0- since we now know that this isn't enough to fix our problems with 64-bit make buildsymbols.
blocking2.0: ? → -
I don't know if we still want to do this given comment 7. Reassigning to Ted who can make a decision.
Assignee: joshmoz → ted.mielczarek
We figured out a workaround in bug 577431, so we don't need this immediately. We'll pick it up the next time we sync with upstream.
No longer blocks: support-10.6_x64, 571367, 576053, 577431
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: