Solved Infinite spawn of windows on startup
-
LOL, I thought maybe the uninstall / re-install of the extension might fix the issue as it's not currently happening in a second profile, but as soon as I installed the extension in the problematic profile again, a seemingly infinite spawn of windows started again. Well, it's definitely that extension at fault, not Vivaldi!
-
-
-
I heard back from the Raindrop author.
He considers the issue a Vivaldi problem and doesn't plan to fix it on his side:
Hello! Unfortunately Vivaldi in my experience very unstable and unpredictable.
Right now I can't even open a Vivaldi settings screen, just not responding.
And what's even worse there no way to debug internals of Vivaldi to figure out why some Vivaldi specific bug happen with our extension. I just tired of battling with it, sorry.
I'm not sure how to debug this further myself, so I guess I get to choose to between using Vivaldi and using the Raindrop extension.
-
I tried to workaround the issue by installing the bookmarklet after disabling the extension, but installing the bookmarklet also caused dozens of blank windows to be spawned, just like with the extension.
So maybe there's something weird about the raindrop site, but it's not an issue with the extension.
-
I'm not sure how to debug this further.
-
@markstos said in Infinite spawn of windows on startup:
I heard back from the Raindrop author.
He considers the issue a Vivaldi problem and doesn't plan to fix it on his sideSad, that author of extension does not want to check.
As i do not use paid raindrop,io i can not help. -
I was able to trigger the issue again, this time just by clicking on a Mastodon icon in the sidebar.
The logs to STDOUT are full of mentions of extensions, but they don't appear to ones I have installed, but perhaps internal Vivaldi extensions.
Logs like these:
[127742:127742:0404/132328.501344:ERROR:CONSOLE(1)] "WindowPortal.componentWillUnmount: Expected to find contentWindow", source: chrome-extension://mpognobbkildjkofajifpdfhcoklimli/bundle.js
[127742:127742:0404/132331.794592:ERROR:CONSOLE(0)] "Unchecked runtime.lastError: Could not find guest", source: chrome-extension://mpognobbkildjkofajifpdfhcoklimli/window.html (0)Is there a way to try disabling this extension? It's not not seen in vivaldi://extensions.
Given that the issue has been repro'ed with the Raindrop extension disabled, it does appear to be a Vivaldi issue.
-
@markstos said in Infinite spawn of windows on startup:
mpognobbkildjkofajifpdfhcoklimli
Is the Vivaldi browser itself.
-
I believe I've isolated the issue, and it's something I would consider a bug in Vivaldi.
The issue seems to be triggered by this line of code in the "New Tab, New Window" extension:
chrome.tabs.onCreated.addListener(function(tab){
https://chromewebstore.google.com/detail/new-tab-new-window/dndlcbaomdoggooaficldplkcmkfpgff
I think the issue is only triggered when the Vivaldi sidebar is open, which I presume is implemented by the Vivaldi extension. I'll further guess that that the Vivaldi sidebar is firing the "chrome.tabs.onCreated" event when content is displayed there. Together, we have all the ingredients needed to DDoS Vivaldi with an infinite loop of window spawns:
- Vivaldi opens a new window with the sidebar open, causing an extra "tab.onCreated" event to fire.
- The New Tab, New Window event attempts to convert this tab to window by spawning a new window.
- The new window launches with the sidebar open, firing an extra "tab.onCreated" event and starting the recursion.
If this theory is correct, I think Vivaldi's internal content display should suppress the "tab.onCreated" event to avoid problems with extensions that the the event is only fired for normal tabs.
This extension has over 20,000 users because it's of interest to folks with tiling window managers that prefer to use that to tile the windows instead of in-browser tabs.
-
@markstos Please report issue to Vivaldi bug tracker.
Do not forget to add what you have done to fix it and all information you got from debugging, Vivaldi developers do not want to read thru all the thread.
Once that is done, share the bug number (beginning with VB-) you got by bug report mail. Thanks for helping us making Vivaldi better. -
@DoctorG Filed as bug VB-105536