518590 - Right click on bookmark crashes firefox [@ strcmp - nsClipboard::HasDataMatchingFlavors]

Status: RESOLVED WORKSFORME

(Firefox :: Bookmarks & History, defect)

Description

[Steve Schveighoffer]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.3) Gecko/20090909 Fedora/3.5.3-1.fc11 Firefox/3.5.3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.3) Gecko/20090909 Fedora/3.5.3-1.fc11 Firefox/3.5.3

If I right click a bookmark in the bookmark toolbar to try and delete it, firefox crashes.  If I try to right click a bookmark in the bookmarks menu, it crashes.  If I open "organize bookmarks", then click on "bookmark toolbar" or "bookmark menu", it crashes.

Reproducible: Always

Steps to Reproduce:
1. Start Firefox
2. Right click "Most Visited" or other bookmark toolbar item
3. Firefox crashes
Actual Results:  
Firefox Crash

Expected Results:  
popup menu to tell what to do with bookmark.

Comment 1

[Tyler Downer [He/Him]]

Can you get a stacktrace? It is easiest to get a mozilla.com build for linux, but you can use https://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report as well

Comment 2

[Steve Schveighoffer]

Attachment: trace of error occurring

attached trace

Comment 3

[Arie Paap [:wildmyron]]

I think this is bug 495392.

Comment 4

[Stephanie Daugherty [:sdaugherty]]

Does it happen with a clean profile?

Comment 5

[Steve Schveighoffer]

Yes, in fact I created a new profile to create the stack trace and report the bug so I could leave open my normal profile's firefox to read instructions (on how to get a stacktrace) and report the bug.

Comment 6

[Marco Bonardo [:mak]]

it is possible comment 3 is correct, the stack trace seems to point there, but i'm just adding a dependancy for now.

Comment 7

[timeless]

#4  strcmp () at ../sysdeps/i386/i686/strcmp.S:39
No locals.
#5  0x0583fb97 in nsClipboard::HasDataMatchingFlavors (this=0xaff10160, 
    aFlavorList=0xaff0c6f0, aLength=3, aWhichClipboard=1, _retval=0xbfc87a18)
    at nsClipboard.cpp:448
        atom_name = 0x0

Comment 8

[Steve Schveighoffer]

Fedora updated it's version to 3.5.4, and this bug no longer occurs.  Not sure if it's something that was fixed on purpose.  Might want to try the related bug to see if it's also fixed.  Has anyone else had this crash occur?  Can they confirm that 3.5.4 fixes/does not fix the problem?

Comment 9

[Steve Schveighoffer]

It was suggested that since I was the only one who has seen this, and since it has been resolved in my case, that I should close it.