Unexpected browser close

[DedSec002]

when using extension, i see most of the time Chrome browser gets closed expectedly in the event of creating new tab.

Please if this problem.

[breschio]

Hi @DedSec002, thanks for the report.

I dug through the extension and couldn't find any code paths that create new tabs or windows. The service worker (background.js) only does two chrome.tabs.* calls: sendMessage (toggle sidebar) and captureVisibleTab (screenshots). There's no chrome.tabs.create, chrome.windows.create, or window.open anywhere in the JS, so the extension shouldn't be causing tab/window creation directly.

The most plausible mechanism I can think of is a renderer crash from the auto-injected content script (~530 KB across html2canvas.min.js + moat.js + content_script.js), which on low-memory machines or heavy pages could surface as Chrome's "Aw, Snap!" tab crash and be perceived as the browser closing.

To pin this down, could you share:

1. Chrome version + OS
2. Whether the whole Chrome window closes, or just one tab going to "Aw, Snap!"
3. The URL/site you were on when it happened
4. Any entries in chrome://crashes from around that time
5. The error log at chrome://extensions for Drawbridge (toggle "Developer mode" → "Errors")
6. Whether the Drawbridge sidebar was open in the source tab

With repro details I can take another pass. If it turns out to be the heavy auto-inject, switching to activeTab + chrome.scripting.executeScript on icon click (rather than <all_urls> content script injection) is the standard mitigation.

---

Generated by Claude Code