789012 - Add-on : Grab and drag "TypeError: can’t access dead object"

Status: RESOLVED WORKSFORME

(Firefox :: Untriaged, defect)

Description

[Zack]

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

Steps to reproduce:

This bug usually happens when i'm reading manga at http://mangafox.me/. It is one of the site on which i use the grab and drag add-on the most.


Actual results:

I don't know if it the fact to have made it uses my wheel click to enter grab and drag mode, or if it is because i made the click on ads or scrolling a bit at the same time but sometimes, all of my click doesn't work anymore on the pages, although i can still click on my all-in-one sidebar.

Comment 1

[Cork]

This is most likely a dup of bug 786577. Read bug 786577 comment 1 for why this happens, and look through your extensions for the one causing the dialog.

Comment 2

[Zack]

Yes it is. But i thought Nicholas Nethercote wanted us to report this kind of add-on's problem on a different report than this global one.
Anyway, i looked at my error console which was telling me this : "TypeError : can't access dead object" (chrome://grabanddrag/content/grabanddrag.js).

Comment 3

[Zack]

(In reply to Zack from comment #2)
> Yes it is. But i thought Nicholas Nethercote wanted us to report this kind
> of add-on's problem on a different report than this global one.
> Anyway, i looked at my error console which was telling me this : "TypeError
> : can't access dead object" (chrome://grabanddrag/content/grabanddrag.js).

Ah, I forgot to mention that the line of the javascript was the 779.

Comment 4

[Zack]

Well, so far, i've only noticed problems with this site : http://mangafox.me/.
The last time i had one, it dit with the line 1106 of the chrome://grabanddrag/content/grabanddrag.js.
I'll try again with other websites and understand the pattern which lead to this.

Comment 5

[[:Aleksej]]

What does this have to do with [MemShrink]?

Comment 6

[Zack]

(In reply to Aleksej [:Aleksej] from comment #5)
> What does this have to do with [MemShrink]?

I wonder.

"If you have any additional add-ons that you think have been adversely affected by Firefox 15, open the error console and use the “filter” search box in the top right-hand corner to look for a message that says “TypeError: can’t access dead object” — that’s the message that indicates an add-on is trying to access memory via a reference that Firefox 15 has pre-emptively cut.  Please report any problems in Bugzilla and put “[MemShrink]” in the whiteboard field." - Nicholas Nethercote (https://blog.mozilla.org/nnethercote/2012/09/05/memshrink-progress-week-63-64/)

Maybe it could be because the huey's fix is related to memshrink project ?
And so maybe it could be that this new behaviour of Firefox, related to this fix, create some new kind of problem ?

Comment 7

[Zack]

Anyway, Ian Weiner (the add-on's creator) reacted promptly and came with a fix which seems to resolve everything.
I'll wait a bit before closing this report to see if anything new happens.

Comment 8

[[:Aleksej]]

(In reply to Zack from comment #6)
> (In reply to Aleksej [:Aleksej] from comment #5)
> > What does this have to do with [MemShrink]?
…
> And so maybe it could be that this new behaviour of Firefox, related to this
> fix, create some new kind of problem ?

Oh, indeed.