Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

Tabs permanently stuck if Brave is out of RAM #12516

Closed
Katamori opened this issue Jan 5, 2018 · 4 comments
Closed

Tabs permanently stuck if Brave is out of RAM #12516

Katamori opened this issue Jan 5, 2018 · 4 comments
Labels
duplicate Issue has already been reported

Comments

@Katamori
Copy link

Katamori commented Jan 5, 2018

Description

If used under heavy RAM load, then, when resource is taken away from tabs, thy become unresponsive. You can't click back on them, and given the lack of internal task manager, you can't even close them.

Steps to Reproduce

  1. Make your RAM usage above 90%.
  2. Open multiple tabs in Brave and switch to another program. Use it and wait.
  3. Return to Brave and try to click on tabs.

Actual result:

Tabs don't react to any mouse-based interaction.

Expected result:

Tabs can be opened as always.

Reproduces how often:

Frequent under heavy RAM load.

Brave Version

about:brave info:

Brave: 0.19.123
rev: f45cb3a
Muon: 4.5.31
libchromiumcontent: 63.0.3239.108
V8: 6.3.292.48
Node.js: 7.9.0
Update Channel: Release
OS Platform: Microsoft Windows
OS Release: 10.0.15063
OS Architecture: x64

Reproducible on current live release:

Yes

@srirambv
Copy link
Collaborator

srirambv commented Jan 5, 2018

This issue has been captured here #12202. Closing as dupe. Added +1 on the issue

@Katamori
Copy link
Author

Katamori commented Jan 5, 2018

Oh, sorry, the different wording made me confused.

@srirambv
Copy link
Collaborator

srirambv commented Jan 5, 2018

No worries. Thanks for reporting

@srirambv srirambv added the duplicate Issue has already been reported label Jan 5, 2018
@kjozwiak
Copy link
Member

kjozwiak commented Jan 5, 2018

Thanks for taking the the time to report this @Katamori! Closing as this is a dupe.

@kjozwiak kjozwiak closed this as completed Jan 5, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
duplicate Issue has already been reported
Projects
None yet
Development

No branches or pull requests

3 participants