Closed Bug 1701336 Opened 3 years ago Closed 3 years ago

history clear crash

Categories

(Firefox :: Bookmarks & History, defect)

Firefox 88
defect

Tracking

()

RESOLVED DUPLICATE of bug 734643

People

(Reporter: sophia.albert, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:88.0) Gecko/20100101 Firefox/88.0

Steps to reproduce:

Have several thousand occurrences in web history
Go to History (Ctrl + Maj + H)
Search occurence (like "wikipedia") with thousand occurences
Select all and delete

Actual results:

It overloads the ram and crashes firefox

Expected results:

Just delete selected item in history

The Bugbug bot thinks this bug should belong to the 'Firefox::Bookmarks & History' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → Bookmarks & History
Flags: needinfo?(sophia.albert)

More details on the bug:
When I click on delete, it overloads the ram, but firefox deletes the history little by little. After a while the Firefox interface stops responding (but Firefox still works), then the system interface stops responding (Ubuntu Gnome, 8GB ram). Strictly speaking, there is no Firefox crash, and I couldn't find a crash report in about: crashes. It's the whole system that crashes. I have had the problem several times this year.
Hope these details help you.

Flags: needinfo?(sophia.albert)

I reproduced the bug on Windows 10 with 16 Go of ram (Firefox 88). It is not a ram problem.
I searched for "google.com" in history and selected 4000 occurrences, and clicked on delete.
It took me about 200MB of extra ram, but didn't overload the ram actually. Only firefox was unresponsive for a few minutes, then it finally responds and deleted the history successfully. I think on Ubuntu the additional problem is that it was taking all the available resources.
There is a problem with the history

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.