164900 - Crash when copying and pasting between two forms.

Status: VERIFIED DUPLICATE of bug 164771

(Core :: DOM: Editor, defect)

Description

[Daniel Bratell]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1b) Gecko/20020317
Build Identifier: 

If I go to a web page with a form, selects everything in an textarea, copies it,
rewrites the URL to load another form and there pastes Mozilla crashes.

Reproducible: Always

Steps to Reproduce:
1. Open http://susning.nu/susning.fcgi?action=edit&id=Beryllium
2. Put cursor in the textarea and copy everything by pressing CTRL+A, CTRL+C
3. Edit the URL to http://susning.nu/susning.fcgi?action=edit&id=Brom and load
that page
4. (maybe optional) Select the existing text in the textarea
5. Put the cursor in the textarea and paste with CTRL+V

Actual Results:  
Crash (stack trace coming up)

Expected Results:  
Replaced the selected text with the copied text.

Comment 1

[Daniel Bratell]

I can no longer reproduce the crash, but instead gets garbage (lots of asian
characters) in the form. I guess it's just another symptom of the same
underlying problem. 

I reproduced it three times in a row before reporting so I wonder if something's
changed with my profile. I'll be back.

Comment 2

[Daniel Bratell]

With a fresher profile I still got garbage and instead crashed at the end with a
stack trace that looked a little like the ones I got when pasting:

MSVCRT! 7800124c()
nsDataObj::GetText(nsDataObj * const 0x00000356, const nsACString & {...},
tagFORMATETC & {...}, tagSTGMEDIUM & {...}) line 704 + 10 bytes
nsDataObj::GetData(nsDataObj * const 0x00000000, tagFORMATETC * 0x0012fd88,
tagSTGMEDIUM * 0x0012fd4c) line 220 + 6 bytes
OLE32! 77a9bb0b()
OLE32! 77a9b9df()

Comment 3

[kinmoz]

If you are using a TRUNK build, the asian character problem you mention could be
due to regression bug 164771.

Comment 4

[Daniel Bratell]

It's the trunk. I guess it's the same, and since the crash isn't reproducible by
me anymore...

*** This bug has been marked as a duplicate of 164771 ***

Comment 5

[Arthur]

If your build really is 20020317 as the bug description implies, you're seeing a
different bug.

Comment 6

[Jason Bassford]

Also, if you can't reproduce the problem any more you should not be marking the
bug as a dupe of something else at all, but resolving it as WORKSFORME.

Comment 7

[Daniel Bratell]

I don't know why it says March 17. This is most definately a trunk build a
couple of hours old. Also, even if I can't see the exact crash I saw first, I
still have big clipboard problems which I think is of the same origin as the
crash and since those problems are the same as in bug 164771 I marked it as a
dupe. If I after rebuilding with that bug's patch still see the crash, I promise
to reopen this bug.

Comment 8

[sujay]

verified.