Closed Bug 595781 Opened 15 years ago Closed 15 years ago

__LOCATION__ not defined for JavaScript modules?

Categories

(Firefox :: Extension Compatibility, defect)

x86
All
defect
Not set
major

Tracking

()

RESOLVED FIXED
Tracking Status
blocking2.0 --- -

People

(Reporter: vladmaniac, Unassigned)

Details

Build ID: Mozilla/5.0 (Windows NT 6.1; rv:2.0b6pre) Gecko/20100912 Firefox/4.0b6pre Litmus Steps to reproduce: 1.Go to the Crashme project page. 2.Download the XPI to your desktop and then drag and drop it on your browser to install the extension and restart. 3.Navigate to Tools menu and select an item from the "Crash me!" sub menu. Behavior: The addons does not crash FF4b6. Tried: 1.Installing with fresh profile, with no other custom AMO extensions installed. 2.Adding the bool extensions.checkCOmpatiblity.4.0b = false in config system page. 3.Tested with all available platforms (Mac OS X 10.6, win7, Ubuntu 10.04) all with 32b platform.
blocking2.0: --- → ?
Component: General → Breakpad Integration
Product: Firefox → Toolkit
QA Contact: general → breakpad.integration
Are you using the newer version? http://crashme.googlecode.com/files/crashme-new.xpi The old version will not work with the 4.0 betas due to some XPCOM changes.
(FWIW, crash reporting works fine for me on all platforms.)
http://ted.mielczarek.org/mozilla/crashme-new.xpi To be sure, I downloaded also from here. On what build have you tested on ?
Flags: in-litmus+
Okay, I just tested in the latest nightly (20100913) on Linux, and I get the following in the error console: Error: __LOCATION__ is not defined Source File: resource://crashme/Crasher.jsm Line: 17 Looks like something broke __LOCATION__ in JavaScript modules, which is breaking "Crash Me Now!".
Component: Breakpad Integration → XPConnect
Product: Toolkit → Core
QA Contact: breakpad.integration → xpconnect
Summary: Breakpad client broken → __LOCATION__ not defined for JavaScript modules?
Oh, I'm an idiot. bug 533038 comment 142 explains it. I need to fix "Crash Me Now!"
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
Okay, I've uploaded a new version which fixes this.
Resolution: INVALID → FIXED
blocking2.0: ? → -
Component: XPConnect → Extension Compatibility
Product: Core → Firefox
QA Contact: xpconnect → extension.compatibility
You need to log in before you can comment on or make changes to this bug.