Closed
Bug 1226040
Opened 10 years ago
Closed 2 years ago
[e10s] dragging images sometimes works, sometimes doesn't
Categories
(Core :: DOM: Copy & Paste and Drag & Drop, defect, P2)
Tracking
()
RESOLVED
WORKSFORME
| Tracking | Status | |
|---|---|---|
| e10s | + | --- |
People
(Reporter: bugzilla.mozilla.org, Unassigned)
Details
Attachments
(2 files)
Dragging images from a webpage to windows explorer ceases to work without apparent cause.
Even when starting to drag the image it doesn't show the half-transparent version that gets dragged along.
Opening a new tab and dropping a file from the explorer into it somehow seems restore the functionality until it fails again at a later point in time.
These messages popped in the browser console, maybe related:
00:55:08.220 TypeError: sourceDocument.defaultView is null contentAreaDropListener.js:123:11
00:55:13.735 Security Error: Content at moz-nullprincipal:{bb0c7097-22ca-4e70-95a9-ec3e920d05f4} may not load or link to file:///<anonymized>
Is there any additional debug information I can gather when this happens?
Comment 1•10 years ago
|
||
Hey The 8472, the error you've brought up is being fired when you drop an image onto the browser, but your report is about dragging images out of the browser.
Can you help clear up what this bug is about by recording a short screencast of yourself demonstrating the bug, and posting it in here?
Flags: needinfo?(bugzilla.mozilla.org)
The issue is about dragging things out of the browser. Like I said I simply tried dropping things into the browser to see whether that is or isn't working either. I guess that must have triggered the log message then and thus probably isn't related to my issue.
I'll record a video when the problem occurs again.
You can't see my mouseclicks but the video shows the following:
1. several attempts to drag an image out of the browser. note that the partially transparent drag-overlay does not appear
2. drop from explorer into the browser in a new tab
3. drag suddenly works again
I hope that clarifies the symptoms i'm seeing.
Flags: needinfo?(bugzilla.mozilla.org)
Updated•10 years ago
|
Assignee: nobody → jmathies
tracking-e10s:
--- → m8+
Now i'm seeing the following error message on the console:
NS_ERROR_NOT_IMPLEMENTED: Component returned failure code: 0x80004001 (NS_ERROR_NOT_IMPLEMENTED) [nsIHandlerInfo.description] nsHandlerService.js:320:0
There is one for each drag attempt and it happens on different websites, so it's unlikely to caused by a website's JS.
Comment 5•10 years ago
|
||
Do you have addons installed? If so can you try reproducing with addons disabled to see if it helps?
Flags: needinfo?(bugzilla.mozilla.org)
Comment 6•10 years ago
|
||
I also see this when dragging an image, but it doesn't interfere with the drag -
08:46:24.207 NS_ERROR_NOT_IMPLEMENTED: Component returned failure code: 0x80004001 (NS_ERROR_NOT_IMPLEMENTED) [nsIHandlerInfo.description]1 nsHandlerService.js:320:0
> Do you have addons installed?
Yes
> If so can you try reproducing with addons disabled to see if it helps?
Since the behavior is fairly intermittent, I do not know how to reliably trigger it and I don't drag images all day long I can only observe it occasionally when attempting to drag something in my regular browsing session, which I am not willing to use for a prolonged time without addons.
If I had a way of reproducing it quickly then I would try without addons of course.
----
Some possibly related behavior I'm seeing is that when I drag something into a browser it replaces the current tab's content with some recently visited or closed tab instead of the drop either loading the image or triggering a drop handler in the current page. This only happens during the transition from the broken state into the working-as-expected state. Subsequent drops work as expected.
Flags: needinfo?(bugzilla.mozilla.org)
Comment 8•10 years ago
|
||
Can you hook me up with your about:support?
Flags: needinfo?(bugzilla.mozilla.org)
Comment 10•10 years ago
|
||
I tried adding Abuction and uMatrix locally. Didn't run into any issues. Greasemonkey is a likely culprit. Are you running a lot of gm scripts?
| Reporter | ||
Comment 11•10 years ago
|
||
A bunch of site-specific ones, but non-greased sites are affected too. Is there any particular component in GM that would affect drag?
As far as I can tell from the GM source it only installs a on-drop event handler in the chrome, not a drag handler.
Comment 12•10 years ago
|
||
blake offered to take a look at this.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(mrbkap)
Comment 13•9 years ago
|
||
I haven't had much time for this and probably won't until the new year. I think this is extension related though (possibly greasemonkey related) as I have not been able to reproduce without extensions installed. Kicking this back out to triage to find a new owner.
Assignee: jmathies → nobody
| Reporter | ||
Comment 14•9 years ago
|
||
> as I have not been able to reproduce without extensions installed.
Were you able to reproduce it at all?
If not, is there anything I gather on my end?
Comment 15•9 years ago
|
||
(In reply to The 8472 from comment #14)
> > as I have not been able to reproduce without extensions installed.
>
> Were you able to reproduce it at all?
>
> If not, is there anything I gather on my end?
No I wasn't able to reproduce. There's another bug related to this too, bug 1231429, which is non-e10s.
Comment 16•9 years ago
|
||
This is probably related to bug 1226040.
| Reporter | ||
Comment 17•9 years ago
|
||
(In reply to Blake Kaplan (:mrbkap) (please use needinfo!) from comment #16)
> This is probably related to bug 1226040.
I'm experiencing infinite recursion here ;)
Comment 18•9 years ago
|
||
(In reply to The 8472 from comment #17)
> (In reply to Blake Kaplan (:mrbkap) (please use needinfo!) from comment #16)
> > This is probably related to bug 1226040.
>
> I'm experiencing infinite recursion here ;)
Erm, bug 1183915. Sorry about that! I hope you break out before your stack overflows.
Comment 19•9 years ago
|
||
I'm hoping the patch in bug 1183915 fixes this. The 8472, can you try your STR with one of the builds produced by the try push at [1] when they're available?
[1] https://treeherder.mozilla.org/#/jobs?repo=try&revision=a3fa9c8d9602
Flags: needinfo?(mrbkap) → needinfo?(bugzilla.mozilla.org)
| Reporter | ||
Comment 20•9 years ago
|
||
Sure, i'll give it a try. It'll take a while to confirm though since I'm not seeing it frequently.
| Reporter | ||
Comment 21•9 years ago
|
||
Ah, actually, there is no windows x64 build. I can't test with 32bit due to virtual address space exhaustion.
Flags: needinfo?(bugzilla.mozilla.org)
Comment 22•9 years ago
|
||
I've triggered a 64-bit Windows debug build on the same push. Should be available in a few hours.
| Reporter | ||
Comment 24•9 years ago
|
||
There only is a logfile for the x64 build on archive.mozilla.org, no binaries.
Maybe I should just wait until bug 1183915 makes its way into nightly?
Flags: needinfo?(bugzilla.mozilla.org)
Comment 25•9 years ago
|
||
Yeah, that's fine.
| Reporter | ||
Comment 26•9 years ago
|
||
The issue is still occurring in Build ID 20160224030246, does that contain the patch from the other bug?
Comment 27•9 years ago
|
||
The patch missed that build by 2 minutes, today's nightly has it.
| Reporter | ||
Comment 28•9 years ago
|
||
Ok, it's still happening in build 20160225030209
Updated•9 years ago
|
Flags: needinfo?(jmathies)
| Reporter | ||
Comment 29•9 years ago
|
||
During a more intense image-hunting session I have observed a whole cluster of symptoms which I suspect of having a common cause:
- dragging picks up an image that's not under the current mouse pointer
- something on the same page, but different scroll position
- something from a different tab
- something from a previously-visited page on the same tab
- dropping from the file manager into a browser form element causes erratic effects
- loads a previously visited page, possibly from a different tab
- loads a previously dragged image, possibly from a different tab, as top-level URL
- dragging from the browser doesn't work at all until something gets dropped into the tab [the initially reported issue]
- dropping from file manager doesn't work, shows the "can't drop here" mouse icon, reloading the page solves that [potentially not a browser bug, could be something with the JS on the page, I'm still listing it since it fits into the cluster]
Those symptoms only occur intermittently, only affect some tabs and either only occur once or go away by performing a specific action. So my guess is that some internal state relating to DnD gets desynchronized/glitched and the next action puts it into a well-defined state again.
I don't have precise STR since I exercise a fairly broad set of browser features while hunting for images.
Non-exhaustive list, in no particular order:
- spawning background tabs via middle-click
- aborting drags via the ESC key
- back-forward navigation
- dragging images from gallery pages into the file manager [pages have some dynamic gallery features like inline-expansion and infinite scroll]
- switching tabs
- dropping images from file manager into a form [form is dynamic, showing image previews, uploading via XHR, actually has drop handler installed on the whole page, not just the form field itself]
Updated•9 years ago
|
Flags: needinfo?(twalker)
Comment 30•9 years ago
|
||
Firefox: 48.0a1, Build ID: 20160328030215
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:48.0) Gecko/20100101 Firefox/48.0
Hi,
I have tested this issue on the latest Nightly (48.0a1) build and I have manged to reproduce it a few times, but I don't know which are the exact steps to reproduce it. It seems that it is randomly reproducible. Mostly I have reproduced it when I opened some large images with middle click in new tabs and rapidly zooming in and out a few times. Then switching tabs or opening a new image is causing the problem. Sometimes I can not use drag and drop on all tabs, util I drop an image from my computer or reset Firefox.
Also, I have reproduced it when I returned on a old opened tab with an image, but still I am not sure what are the exact steps.
I have also tested this on windows 8 x32 and Ubuntu 14.04 and managed to reproduce it randomly.
Thanks,
Cosmin.
Comment 31•9 years ago
|
||
I've messed around with this quite a bit now in attempt to dial in some reproducible steps. I think I have steps that one could use to eventually reproduce a form of drag and drop corruption on Windows.
STR:
0) have a largish image on the desktop. (I used one 740Kb)
1) drag the image from the desktop to tab 1
2) Open a new tab, then Drag the image from the desktop to tab 2
3) Rapidly zoom in and out by clicking in the image 5 times to leave it zoomed in
4) quickly DnD the image from tab 2 to the desktop (choose to replace the existing image)
5) reload tab 1
Test results: The image is corrupted; only the top 25-30% of the original image is displayed. (note: speed in steps 3 and 4 do seem to be a factor. if you do these steps slowly, the bug doesn't repro)
If you continue to DnD the image from the desktop to a tab, zoom in and out, then quickly DnD the image back to the desktop, eventually, randomly the DnD wipes the image from the desktop and the image is not found on tab reload. This last effect is very bad as it is data loss.
I tested with recent versions of Nightly on (update is not currently working)
Win 7, Nightly 48.0a1 20160324030447 - Reproduced image corruption and occasionally lost desktop image.
Mac, Nightly 48.0a1 20160328030215 - can't reproduce as the OS automatically makes a copy of the image instead of offering an option to replace
Ubuntu, Nightly 48.0a1 20160325030241 - same as Mac, the OS automatically makes an image copy.
Flags: needinfo?(twalker)
Updated•9 years ago
|
Priority: -- → P2
Comment 32•9 years ago
|
||
Given that this reproduces on Linux, I'm wondering if someone could try catching it under rr with the steps provided.
Updated•3 years ago
|
Severity: normal → S3
| Reporter | ||
Comment 33•2 years ago
|
||
Closing since I haven't seen the issue for quite some town.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•