Description of the issue: Typically my browser has multiple tabs opened, and it is set to open where I left off. Occasionally when I shut down Brave, a window that was hidden behind remains open. Then when I reopen Brave, ALL tabs and groups are gone! PLEASE - this can be prevented if I could limit Brave to ONE SINGLE WINDOW. Then when Brave is reopened, I can truly resume where I left off. I have spend many hours trying to rebuild the workspace and never can duplicate the previous setup. This is all due to that hidden window. Please, Please, PLEASE allow the user to limit Brave to ONE SINGLE WINDOW !!!
Brave Version (check About Brave): Brave 1.85.120 (Official Build) (64-bit) Chromium: 143.0.7499.192
**Operating System:**Ubuntu 24.04
289wk
January 10, 2026, 7:09am
2
@2010CVPI
opened 08:50PM - 05 Sep 24 UTC
feature/tabs-bar
OS/Linux
feature/tear-off-tabs
OS/Desktop
### Description
When I move a tab between windows, a new window with an empty t… ab spawns in addition to the other windows.
### Steps to reproduce
1. Open multiple windows with multiple tabs.
(actually a single window with multiple tabs might be enough)
2. Move mouse onto a tab, then mousedown and hold to start dragging.
3. Keep the mouse button down, and drag the tab down until it detaches from the window's tab bar.
4. Keep the mouse button down, and drag the tab to a different (existing) window, or to the same place where it was, in the same window.
5. Release the mouse button to drop the tab to the new place.
### Actual result
(good) In step 3, a new (temporary?) window appears where I am dragging the tab.
(good) In step 4, the tab re-attaches into the destination tab bar.
(bad) In step 4, the new temporary window remains open, with an empty tab.
(good) In step 5, the tab is moved to the correct place.
(bad) After the operation, the additional window with empty tab remains open.
### Expected result
Tab is moved to the correct place.
No new window is created or remains open after the operation.
### Reproduces how often
Easily reproduced
### Brave version (brave://version info)
Brave: 1.69.153 Chromium: 128.0.6613.85 (Official Build) (64-bit)
Revision: a69e96756922f88cbce3482971d70cfd1ee6f872
OS: Linux
Distro: Ubuntu 12
Desktop: KDE Plasma 5.27.11
### Channel information
- [X] release (stable)
- [ ] beta
- [ ] nightly
### Reproducibility
- [ ] with Brave Shields disabled
- [ ] with Brave Rewards disabled
- [ ] in the latest version of Chrome
### Miscellaneous information
I think I understand how this happens:
- Dragging a tab around creates a new temporary window, which makes sense if I want to detach the tab from the window.
- In previous versions, there was a mechanism that would close a window when the last tab is closed, or removed from the window.
- In the current version, the window remains open, even after removing the last tab.
- The "temporary" window that appears during the drag + drop operation is not internally marked as such, and therefore the same behavior occurs that leaves it open after the operation.
“https://www.reddit.com/r/brave_browser/comments/1fmq57q/brave_browser_leaving_big_white_boxes_behind_when/?rdt=63989 ”
“Brave browser is leaving bug white boxes behind when I move a tab from one page to another they remain on my desktop till I close out of Brave and it is happening all the time. Anyone have a solution to this problem?”
Description of the issue: New tabs are open in the browser’s task manager that aren’t visible in the browser. If I close the browser, it continues to run because it thinks these tabs are open
How can this issue be reproduced? I don’t know what exactly triggers this, but I only started noticing it after I disabled the setting to close window when closing last tab, so I think it’s related.
I tried mashing ctrl+w on the new tab page but that didn’t trigger it.
Expected result: There shouldn’t be…
(authored by @sampson )
For those impacted by performance and/or memory issues, here are a couple steps to take which will help us in helping you.
As many here have stated, it’s good to disable extensions. Extensions are third-party applications; it’s entirely possible an extension could eat up tons of memory. By removing them from the equation, we greatly simplify the task of identifying the problem itself.