Closed Bug 978961 Opened 11 years ago Closed 11 years ago

[e10s] Adblock Plus addon endlessly logs errors about "cannot ipc non-cpow object. requestNotifier.js:62"

Categories

(Core :: General, defect)

Product:
Core
Component:
General
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla32
Tracking Flags:
Tracking Status
e10s + ---

People

(Reporter: cpeterson, Unassigned)

References

Details

(Keywords: addon-compat)

STR: 1. Install Adblock Plus addon. 2. Open new e10s window. 3. Open Browser Console. 4. Load any web page. RESULT: Firefox endlessly logs CPOW errors: cannot ipc non-cpow object. requestNotifier.js:62 cannot ipc non-cpow object. requestNotifier.js:62 cannot ipc non-cpow object. requestNotifier.js:62 cannot ipc non-cpow object. requestNotifier.js:62 cannot ipc non-cpow object. requestNotifier.js:62 cannot ipc non-cpow object. requestNotifier.js:62
tracking-e10s: --- → +
Blocks: e10s-abp
No longer blocks: e10s-addons
Summary: [e10s] Addblock Plus addon endlessly logs errors about "cannot ipc non-cpow object. requestNotifier.js:62" → [e10s] Adblock Plus addon endlessly logs errors about "cannot ipc non-cpow object. requestNotifier.js:62"
That's the node.setUserData() call. With bug 982561 resolved, the current development builds no longer use it in Firefox 32 - weak maps are used instead. The plan is to have Adblock Plus 2.6.2 released on June 3rd, until then you might want to test the latest development build from https://downloads.adblockplus.org/devbuilds/adblockplus/. For me it seems to work correctly, requests are being tracked and no console spam.
Thanks, Wladimir! I tested Adblock Plus development build 2.6.1.3821 with e10s and I no longer see any log messages about CPOWs.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla32
You need to log in before you can comment on or make changes to this bug.