Closed Bug 1160748 Opened 10 years ago Closed 10 years ago

Video DownloadHelper (5.2.0) causes tabs of Blogger blogs to crash with e10s

Categories

(Firefox :: Extension Compatibility, defect)

40 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1151848
Tracking Status
e10s ? ---

People

(Reporter: nyuszika7h, Unassigned)

References

()

Details

(Keywords: addon-compat)

User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:40.0) Gecko/20100101 Firefox/40.0 Build ID: 20150501030205 Steps to reproduce: 1. Make sure e10s is enabled. 2. Install Video DownloadHelper 5.2.0 from addons.mozilla.org. 3. Visit a Blogger blog, such as: - http://rajzfilmovezet.blogspot.hu/ - http://tinitv.blogspot.hu/ - http://gyerek-vilag.blogspot.hu/ Actual results: The tab crashed after it finished loading. Expected results: It shouldn't crash, obviously.
The issue goes away if the tab is opened in a non-e10s window or the addon is disabled.
tracking-e10s: --- → ?
Also, this seems to be a regression in the latest nightly (the one I'm running right now).
(In reply to nyuszika7h from comment #2) > Also, this seems to be a regression in the latest nightly (the one I'm > running right now). Can you try to find the regression range? http://mozilla.github.io/mozregression/
Blocks: e10s-addons
Component: Untriaged → Extension Compatibility
I could not reproduce the problem on any of the 3 URLs using 5.2.0. However, with the latest nightlies VDH 5.2 does not work anymore (this is due to the "remote" attribute not being set anymore when in e10s). The upcoming 5.3.0 fixes that last issue. Can you give a try with 5.3.0rc3 ( http://www.downloadhelper.net/install-beta.php?version=5.3.0rc3 ) to see if it also fixes that blogger issue ?
Works for me but made my own crash (on another page) that later stopped happening after restart with just this add-on. Possibly dupe of Bug 1151848 Go to about:crashes, open a crash report. If it contains SendGetCurrentScreenConfiguration then it's the same bug.
Indeed, it contains that. The latest crash ID is 556b153c-693d-42c4-ae53-76c4a2150503.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.