If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Planet Mozilla crashes and then later throws a personalize.js modal-dialog error (repeatable)

RESOLVED INVALID

Status

Firefox OS
Gaia::Browser
--
critical
RESOLVED INVALID
5 years ago
4 years ago

People

(Reporter: stephend, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
Created attachment 716938 [details]
adb logcat

Build: b2g-18, 9e25bd41032f
v1-train: 1c1b29bf0dec
Gecko: 83c0b7f12fd4226209c259288c671bb939a1ef03
Gaia: 2a062d9775ac92f3d34845611ce79ee43600005d

STR:

1. Flash using today's https://pvtbuilds.mozilla.org/pub/mozilla.org/b2g/nightly/mozilla-b2g18-unagi/2013/02/2013-02-21-07-02-02/unagi.zip build (21-Feb-2013 08:08)
2. Turn on Remote Debugging, Wi-Fi Debug logging, Console
3. Connect to a password-protected Wi-Fi network (in this case, I was at CloudFlare's HQ)
4. Launch the browser
5. In the URL bar, type "planet mozilla" and search using Bing
6. Click on the 1st result, and wait

Expected:

Planet Mozilla loads and renders

Actual:

It loads a bit, but then crashes, and later also throws an exception that I can't close, about Planet's "personalize.js" JavaScript include:

E/GeckoConsole(  108): [JavaScript Error: "TypeError: evt is undefined" {file: "app://browser.gaiamobile.org/js/modal_dialog.js" line: 178}]

(Similar to bug 830010, but here I'm chiefly concerned with the crash.)

(Sorry for the verbose log.)
Crash or process abnormally killed?

Crash = crash report dialog shows up.

Process abnormally killed = App process abruptly closes, no crash report dialog shows up.

If it's a crash, can you provide a link to a crash report?
Sending to browser first for the errors we are seeing. Maybe Ben has some ideas on what we are seeing here.
Component: Gaia → Gaia::Browser
QA Contact: nhirata.bugzilla
(Reporter)

Comment 3

5 years ago
(In reply to Jason Smith [:jsmith] from comment #1)
> Crash or process abnormally killed?
> 
> Crash = crash report dialog shows up.
> 
> Process abnormally killed = App process abruptly closes, no crash report
> dialog shows up.

The latter; I forgot we made that distinction :-)  Also, I mean to cross-link with bug 827955
; might even be a straight-up dupe with more up-to-date info and STR.
See Also: → bug 827955
Resolving INVALID as per bug 827955
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.