68665 - bookmark folder add/delete - cpu usage goes to 100%

Status: VERIFIED FIXED

(SeaMonkey :: Bookmarks & History, defect)

Description

[Colin Blake]

This is similar to bug 68539 and bug 67942, but I am seeing the system going
100% cpu bound. Since 68539 and 67942 don't mention this, I'm considering
this a different problem. If it turns out this bug has the same root cause,
then feel free to mark it a dup.

M0.8 (almost) 2001021020 on OpenVMS.
M0.8 (almost) 2001021203 on Linux.

Bookmarks -> Manage Bookmarks
Click on menubar "New Folder" button
Scroll down to the newly created folder "New Folder"
Click on th enew folder "New Folder"
Click on menubar "Delete" button

************************************************************
* Call to xpconnect wrapped JSObject produced this error:  *
[Exception... "[JavaScript Error: "field.select is not a function" {file: "chrom
e://global/content/treeBindings.xml#treecell-indented-folder-inline-edit-base.se
tMode()" line: 17}] [nsIController::doCommand]"  nsresult: "0x80570021
(NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS)"  location: "JS frame ::
chrome://global/content/globalOverlay.js :: goDoCommand :: line 71"  data: yes]
************************************************************
An error occurred executing the cmd_newfolder command

CPU is pegged at 100%

Comment 1

[gary_Cope]

The steps mentioned here are very similar to those in bug 68542, 
'hang when chosing edit|delete on a corrupted bookmark'.

That bug will also produce the javascript error above before the browser hangs.

Comment 2

[Stephen Walker]

*** Bug 69567 has been marked as a duplicate of this bug. ***

Comment 3

[Stephen Walker]

Also seen on win32, OS -> All

Comment 4

[Claudius Gayle]

I'm upping the severity to critical. I didn't get any error messages or warning this just
locked up my mac and my linux box. With a 2001022213 build.
Only thorugh dramatic 'ER' style lifesaving techniques was I able to keep the linux box up,
sadly, we lost the Mac.

Comment 5

[Keyser Sose]

Adding hang keyword.

Comment 6

[Ben Goodger (use ben at mozilla dot org for email)]

Fix checked in. 

Comment 7

[Claudius Gayle]

VERIFIED Fixed