1130610 - Error: Route error: message sent to unknown actor ID

Status: UNCONFIRMED

(Core :: Graphics: Layers, defect)

Description

[John Nagle]

Attachment: Diffs between "widget" version and "ui" version of add-on.

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0
Build ID: 20150122214805

Steps to reproduce:

Updating a Firefox add-on to use "sdk/ui" instead of "widget" for a preferences panel brought up by a toggle button. Followed the directions at
"https://developer.mozilla.org/en-US/Add-ons/SDK/High-Level_APIs/panel#Attaching_panels_to_buttons".  Used SDK 1.17 and "cfx run" to test.


Actual results:

###!!! [Child][DispatchAsyncMessage] Error: (msgtype=0xAA0001,name=PTexture::Msg___delete__) Route error: message sent to unknown actor ID

appears running under "cfx run" when drop-down menu in panel is released.

Completely reproduceable.


Expected results:

No error message. This worked fine with the "widget" API, but fails with the "ui" API.

Possibly related: https://bugzilla.mozilla.org/show_bug.cgi?id=952404
It's a race condition at GUI object close. Closed as "Fixed"

Possibly related: https://bugzilla.mozilla.org/show_bug.cgi?id=1078134
Open bug, postdates above "fixed" bug.

Report on StackOverflow of a similar problem appearing with SDK 1.17 but not seen with SDK 1.16: http://stackoverflow.com/questions/26641074/weird-error-in-ff-addon-sdk-1-17-when-running

Comment 1

[Matthias Versen [:Matti]]

http://mxr.mozilla.org/mozilla-central/source/ipc/glue/MessageChannel.cpp#1567

Comment 2

[John Nagle]

Notes: Functionally, the panel works fine; it appears and disappears when it should, and the toggle button shows the correct icon, with and without the "pushed" look. The elements of the panel all work. The checkboxes and buttons do not cause that error message.  Only the drop-down menus do.

Historical note: the "Widget" module had a lot of trouble with drop-down menus in its early days.

Comment 3

[John Nagle]

Per the discussion at Bug 1118364, "Remove widget module from SDK", this bug may be a block for that bug. The "widget" module is deprecated, but its replacement, the "ui" module, is still experimental, and per this bug, doesn't work right yet.

Comment 4

[Matteo Ferretti [:zer0] [:matteo]]

Could you explain how to reproduce the issue?

I tried on Firefox Nightly, just using the code provided in the documentation, open the panel and close it, no message on `cfx` terminal. It could be either an old bug fixed already – it doesn't seems related strictly to SDK, more on the platform – or maybe I'm not following your same steps.

If you're able to reproduce it, it would be helpful if you could isolate the problem to one component: in that scenario, it seems that the issue could be related to panel, not to "ui" module (ToggleButton). And as you can see from the example, there is no really any auto-magical wiring between Button and Panel, so if that is happening because the panel, it would probably happen even without the button.

Comment 5

[John Nagle]

Attachment: adlimiter.xpi - add-on version to demonstrate bug

Add-on which demonstrates bug. 

Test by: 

1. Open .xpi file from file menu.
2. Click on add-on's icon in toolbar (checkmark in green circle)
3. Make some change using a drop-down menu.
4. Check browser console for errors.

Error produced: 

TypeError: can't access dead object tab-firefox.js:98

This is different than the error seen under the cfx tool.

Comment 6

[John Nagle]

Re: "I tried on Firefox Nightly, just using the code provided in the documentation, open the panel and close it, no message on `cfx` terminal. It could be either an old bug fixed already – it doesn't seems related strictly to SDK, more on the platform – or maybe I'm not following your same steps."

Per Comment 2 above, it's not opening the panel that causes problems; it's using a drop-down menu within the panel.  A drop-down menu brings up a second GUI element on top of the panel, which is apparently too much for "sdk/ui". 

There were similar drop-down menu bugs back in the early history of "widget". See Bug 701760 and Bug 886329. Drop-down menus in Jetpack add-ons have a long history of trouble.  The "ui" module seems to continue this tradition.

Comment 7

[Benoit Girard (:BenWa)]

(In reply to John Nagle from comment #5)
> TypeError: can't access dead object tab-firefox.js:98

This is a different bug. Using the add-on and using the dropdown from the panel I can't reproduce the gfx IPC error. Can you reproduce using that XPI? If not please attach an XPI that can reproduce the issue.

Comment 8

[Benoit Girard (:BenWa)]

If you can reproduce please see if you can reproduce on Nightly. I tested the following configurations:
Nightly + e10s
Nightly + non e10s
FF 36 + non e10s