Only one tab is stuck; it won't close or open

[jamesray1]

Have you searched for similar issues? Yes.

Description

A tab is stuck; it won't open or close, with no title or favicon. Closing the browser and reopening it (with tabs set to open from where I left off) loads it as a new tab, and I can close it.

Steps to Reproduce

Not sure.

Actual result:
Can't open or close one tab, while others work.

Expected result:
Able to open or close all tabs.

Reproduces how often: [What percentage of the time does it reproduce?]
Not often. I just started using Brave 0.19.16 today and it has occurred once.

Brave Version

Brave: 0.19.16
rev: 88d0bc1
Muon: 4.4.19
libchromiumcontent: 61.0.3163.79
V8: 6.1.534.32
Node.js: 7.9.0
Update Channel: Beta
OS Platform: Linux
OS Release: 4.10.0-35-generic
OS Architecture: x64

Reproducible on current live release:
Tabs have been stuck in previous releases, but I can't remember it occurring on the latest stable release.

Additional Information

I had 10 tabs open including 1 pinned tab.
If it occurs again, I'll check the CPU and memory usage, but currently each CPU is about 5% and memory is about 42%. There are a lot of processes starting with Brave (the highest memory process is brave --user-data-dir=brave [[ ] 196.4 MiB

[jamesray1]

It happened again. That's twice in a day:

I can't remember what caused it. I just opened the browser and noticed it. Again, closing the browser and reopening, it opens a new tab and I can close it.

[srirambv]

This is same as #11129. @jamesray1 did you have any private tabs?

[jamesray1]

No, I had no private tabs open. It occurred again today. Yes it could be the same issue, although I can't remember if I closed tabs before it occurred. I did reproduce your issue.

[jamesray1]

This issue just happened again now with 0.19.80 on Windows, but I can't reproduce it.

Brave: 0.19.80
rev: 7d07299
Muon: 4.5.13
libchromiumcontent: 62.0.3202.75
V8: 6.2.414.36
Node.js: 7.9.0
Update Channel: Release
OS Platform: Microsoft Windows
OS Release: 10.0.15063
OS Architecture: x64

[jamesray1]

IIRC there was no ghost tab. There was no private tab.

[jamesray1]

It happened again.

I'm still not sure how to reproduce it. Restarting unfreezes the browser.

[petemill]

I'm pretty sure this is related to memory pressure causing a discard which was broken and resulted in a dead tab. That's resolved with #12916 and soon to be even better with #13120. If not, there's no specific STR on this issue, so closing anyway. Thanks for the report!