Closed
Bug 597835
Opened 14 years ago
Closed 14 years ago
freeze if focus moved from bookmark library during delete of many (1000) bookmarks or if too many selected to delete
Categories
(Firefox :: Bookmarks & History, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 472343
People
(Reporter: steve_nelson47, Unassigned)
Details
(Keywords: stackwanted)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10 (.NET CLR 3.5.30729)
I selected 800 of 3000+ bookmarks to be deleted. After the delete process started, I moved the operating system's focus to a different window, and the bookmark library (and firefox) stopped responding.
Then I selected 1200 bookmarks to delete. The delete process never started;
the bookmark library and firefox stopped responding first.
Reproducible: Always
Steps to Reproduce:
1.Have a large number of bookmarks. I had 3000+.
2.Select a large number to delete and begin the delete process, if possible.
3.Start another program, or click on an open window of another program.
It doesn't matter whether you are connected to the internet or not.
Actual Results:
The bookmark library and the main firefox program stop responding.
Expected Results:
The bookmark library should have deleted the selected bookmarks, evidently one by one.
Reporter | ||
Updated•14 years ago
|
Summary: freeze if focus moved from library during delete of many (1000) bookmarks or if too many selected to delete → freeze if focus moved from bookmark library during delete of many (1000) bookmarks or if too many selected to delete
Comment 1•14 years ago
|
||
Can you get a Stacktrace Log for that Hang?
https://developer.mozilla.org/en/How_to_get_a_stacktrace_with_WinDbg
Keywords: stackwanted
Version: unspecified → 3.6 Branch
Updated•14 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•