Closed Bug 717265 Opened 13 years ago Closed 12 years ago

Error sanitizing history: [Exception... "Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]" @ sanitize.js :: line 185

Categories

(Firefox for Android Graveyard :: General, defect, P4)

ARM
Android
defect

Tracking

(firefox11 affected, firefox12 affected, fennec-)

RESOLVED WORKSFORME
Tracking Status
firefox11 --- affected
firefox12 --- affected
fennec - ---

People

(Reporter: aaronmt, Unassigned)

Details

(Keywords: regression)

E/GeckoConsole( 1684): Error sanitizing history: [Exception... "Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]"  nsresult: "0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE)"  location: "JS frame :: chrome://browser/content/sanitize.js :: <TOP_LEVEL> :: line 185"  data: no]
E/GeckoConsole( 1684): [JavaScript Error: "count is not defined" {file: "chrome://browser/content/sanitize.js" line: 255}]

STR:

1. Settings -> Clear Private Data

--
Samsung Nexus S (Android 4.0.3)
20120110083323
http://hg.mozilla.org/mozilla-central/rev/46282354b7be
not a priority for simply printing an error message. Please re-nom if there is any user impact.
tracking-fennec: --- → -
Priority: -- → P4
Still occurs : 02-01 11:29:36.397: E/GeckoConsole(6625): Error sanitizing history: [Exception... "Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]"  nsresult: "0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE)"  location: "JS frame :: chrome://browser/content/sanitize.js :: <TOP_LEVEL> :: line 185"  data: no]
02-01 11:29:36.413: E/GeckoConsole(6625): [JavaScript Error: "count is not defined" {file: "chrome://browser/content/sanitize.js" line: 255}]

02/12/12 build of nightly, droid pro, 2.3.3 ; seems to have no impact currently; has occured in XUL for a long time.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.