Closed Bug 529622 Opened 11 years ago Closed 11 years ago

JavaScript Error: "gCrashReporter is not defined" with --disable-crashreporter

Categories

(Firefox :: General, defect)

3.6 Branch
defect
Not set
normal

Tracking

()

VERIFIED FIXED
Firefox 3.7a1
Tracking Status
status1.9.2 --- beta4-fixed

People

(Reporter: dao, Assigned: dietrich)

References

Details

Attachments

(1 file)

Bug 526545 defined gCrashReporter depending on MOZ_CRASHREPORTER but uses it unconditionally.
Assignee: nobody → dietrich
Attached patch fixSplinter Review
Attachment #413178 - Flags: review?
Attachment #413178 - Flags: review? → review?(dao)
Attachment #413178 - Flags: review?(dao) → review+
checked in on trunk. blocks a blocker, so carrying over approval from the blockerness.

http://hg.mozilla.org/mozilla-central/rev/f43b6bc2165b
http://hg.mozilla.org/releases/mozilla-1.9.2/rev/a2fa721b5fdd
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: blocking-firefox3.6+
Resolution: --- → FIXED
Target Milestone: --- → Firefox 3.7a1
This is not fixed in 1.9.2 nightly builds like Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2b4pre) Gecko/20091120 Namoroka/3.6b4pre ID:20091120033655

Error: gCrashReporter is not defined
Source File: chrome://browser/content/browser.js
Line: 4183

You can reproduce this error when clicking the home button in the toolbar. Trunk builds don't show that and look ok on all platforms. Verified with Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.3a1pre) Gecko/20091120 Minefield/3.7a1pre ID:20091120030847

Removing final-fixed keyword.
Status: RESOLVED → VERIFIED
Duplicate of this bug: 530266
I don't see how this could possibly have been fixed only on trunk and not branch, given that the patch landed on both and both seem to only have one reference to gCrashReporter.

Are you using your own --disable-crashreporter builds to test or something else?
Ok, looks like bug 530266 has been wrongly duped then. I'm using nightly builds and no self-build Namoroka for daily testing purposes. Same applies for Alice. So it should be independently handled. I'll move over to bug 530266 and leave this as fixed for 1.9.2.
You need to log in before you can comment on or make changes to this bug.