Closed Bug 360431 Opened 19 years ago Closed 19 years ago

drag and drop of plain text MAY cause unresponsive script and memory leak

Categories

(Firefox :: Address Bar, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 317770

People

(Reporter: lisandro, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-AR; rv:1.8.0.8) Gecko/20061025 Firefox/1.5.0.8 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-AR; rv:1.8.0.8) Gecko/20061025 Firefox/1.5.0.8 Dropping plain text onto the location bar (or onto the document body) from at least one particular plain text editor causes Firefox to hang up and yield an "Unresponsive script" message and a memory leak that is not recovered after stopping the script. Sometimes it wouldn't stop at all and had to be shutdown through Windows Task Manager. By comparison, dropping from other plain editors or from Microsoft Word makes Firefox perform a web search-and-go as expected. Only once out of some 12 attempts I could get to see some text in the location bar after dropping: it was and endless string made out of repeating my original text string. The editor I was using is Notepad2, by Florian Balmer (http://www.flos-freeware.ch/np2intl.html, I use the Spanish-Argentine 1.0.11 version). Since the problem might be caused by something being wrong with the editor's output, I tried to see what the difference between Notepad2's and the others' transferrables could be using a Java DnD testcase: no differences showed up at all. Sorry, no clues from me. Hard to tell the extent to which this is something to worry about, but I think FF should reject this input if wrong instead of hanging. I really looked for this in the "already filed bugs" database and didn't find it. Doesn't seem so likely to happen, anyway. Reproducible: Always Steps to Reproduce: 1. Open Firefox. 2. Run Notepad2 (might happen with some others), type some word in it (for example, hello). 3. Select, drag and drop the word hello onto Firefox's location bar Actual Results: Memory leak, unreponsive script; sometimes hang up. Expected Results: Should navigate to given web address or to web search first result Checking against a single instance of FF with only one window/tab open, FF's memory usage jumped from about 20 Mb to about 58 Mb before (and when) the "Unresponsive script" appeared. Theme: default. Installed extensions: FireBug (disabled), View Source Charts, Venkman (tested both loaded and unloaded).
*** This bug has been marked as a duplicate of 317770 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.