[QAC generated] Problems Clearing Recent History

UNCONFIRMED
Unassigned

Status

()

UNCONFIRMED
8 years ago
7 years ago

People

(Reporter: smacharia8, Unassigned)

Tracking

Trunk
x86_64
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [bugday-2011-05-06])

(Reporter)

Description

8 years ago
Steps to Reproduce
---------------------------------------
1. Ctrl+Shift+Delete >> Everything >> Clear Now


What should have happened:
---------------------------------------
Clear and be done with it


What actually happened:
----------------------------------------
Freezes for a while and creates a bunch of redundant plugincontainer.exe processes, and occasionally will crash or give a javascript responsiveness error, even when performed at program startup (default homepage as well)...

Firefox 4 RC 1 (problem's actually been recurring on past builds as well)
Win 7 Home Premium x64
Intel Core i3 M350
Intel HD Graphics
(Reporter)

Updated

8 years ago
Component: General → Build Config
OS: Windows XP → Windows 7
Hardware: x86 → x86_64

Comment 1

8 years ago
Mozilla/5.0 (Windows NT 6.1; rv:2.0b13pre) Gecko/20110309 Firefox/4.0b13pre

Confirmed. Pressing Ctrl+Shift+Delete -> Everything -> Clear now, freezes the firefox for some time and gives a javascript error with Continue and Stop script dialogues.
provided the problem is caused by clearing cookies, this sounds like the same as Bug 633427
Component: Build Config → General

Comment 3

7 years ago
Reporter, are you still able to reproduce this bug if you clear everything except the cookies?

If you get a Firefox crash please provide the Crash ID from about:crashes.
https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report
Whiteboard: [bugday-2011-05-06]

Comment 4

7 years ago
Bug 633427 has been fixed in Firefox 12 (currently Aurora) and Firefox 13 (currently nightly).

Are you still able to reproduce the bug using Firefox Aurora or Firefox Nightly?
https://www.mozilla.org/en-US/firefox/aurora/
http://nightly.mozilla.org/
You need to log in before you can comment on or make changes to this bug.