Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [inIDOMUtils.setContentState] @ content.js :: _cancelTapHighlight

NEW
Unassigned

Status

8 years ago
7 years ago

People

(Reporter: xti, Unassigned)

Tracking

Trunk
ARM
Android

Details

Attachments

(1 attachment)

(Reporter)

Description

8 years ago
Created attachment 532991 [details]
error screenshot

Build id : Mozilla/5.0 (Android;Linux armv7l;rv:6.0a1)Gecko/20110517
Firefox/6.0a1 Fennec/6.0a1
Device: HTC Desire
OS: Android 2.2

Result:
uncaught exception: [Exception... "Component returned failure
code: 0x80004003 (NS_ERROR_INVALID_POINTER)
[inIDOMUtils.setContentState]" nresult: "0x80004003
(NS_ERROR_INVALID_POINTER)" location: "JS frame ::
chrome://browser/content/content.js ::  _cancelTapHighlight ::
line 612" data:no]

Updated

8 years ago
Summary: Uncaught exception [inIDOMUtils.setContentState] → Uncaught exception [inIDOMUtils.setContentState] - NS_ERROR_INVALID_POINTER
I'm seeing this after load of http://news.google.ae
I have also hit this a few times but seems to be random for the moment. I'm unsure on the way to reproduce it correctly.
Mozilla/5.0 (Android;Linux armv7l;rv:7.0a1)Gecko/20110622 Firefox/7.0a1 Fennec/7.0a1

I can hit this very easily by going to www.hardocp.com and tapping on any of the top motherboard reviews. Checked my console after and it was flooded with the NS_ERROR_INVALID_POINTER exceptions.
I also get flooded with the same error on http://ftp.mozilla.org/pub/mozilla.org/, so many that scrolling locks up my error console.
(Reporter)

Updated

7 years ago
Summary: Uncaught exception [inIDOMUtils.setContentState] - NS_ERROR_INVALID_POINTER → Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [inIDOMUtils.setContentState] @ content.js :: _cancelTapHighlight
(Reporter)

Comment 5

7 years ago
This issue still occurs on the latest Nightly build.

--
Build ID: Mozilla/5.0 (Android;Linux armv7l;rv:9.0a1)Gecko/20110907
Firefox/9.0a1 Fennec/9.0a1
Device: Samsung Galaxy S
OS: Android 2.2
You need to log in before you can comment on or make changes to this bug.