Vivaldi 6.7 RC 1 – Vivaldi Desktop Browser snapshot 3329.16/17

Icehawk_de

@yngve

OK. I will try to remove or disable the extensions one by one after a crash. I'll start with Colorzilla.

So I can sort out the less used one.

But a few extensions are essential for me, e.g. Lastpass.

I will report back.

Zalex108

@Icehawk_de

Hi,
Don't Remove
Just Disable them

You can Run V from Command Line or create a special Shortcut with a Switch

--disable-extensions

Icehawk_de

I have disabled all extensions (except Lastpass). I still get unexpected Vivaldi crashes from time to time. But in the moment no corrupt user profile. I can start Vivaldi again and work.

Zalex108

@Icehawk_de

Try with this:

https://forum.vivaldi.net/topic/94705/guide-troubleshoot-disconnected

Icehawk_de

I've set up a complete new profile from scratch. No sync. No extensions.
I hope it ist now stable.

Update:
No it's not. Still get unexpected crashes.

yngve

@Icehawk_de Any crashdumps? or logs?

Icehawk_de

Sorry, no crash dump.

When I activate logging, is it only at startup or during the whole session till crash?

Edit/Update: The crash often happens, when I use the undocked developer console.

Icehawk_de

@yngve

I think, I found the problem.

As long as I don't use the undocked developer console, I don't get any crash.

yngve

@Icehawk_de Aha! That is something some of my colleagues are working on, but AFAIK they are having problems reproducing. They can reproduce one day, not the next.

One possible "solution" involves disabling a feature that was recently disabled upstream (but not backported).

If you could try starting Vivaldi with this command line argument added

--disable-feature=DevToolsSharedProcessInfobar

we might perhaps learn if it is actually relevant to the problem.

Icehawk_de

@yngve said in Vivaldi 6.7 RC 1 – Vivaldi Desktop Browser snapshot 3329.16/17:

If you could try starting Vivaldi with this command line argument added
--disable-feature=DevToolsSharedProcessInfobar
we might perhaps learn if it is actually relevant to the problem.

I now start Vivaldi with this argument and will tell you the result. It will take some time.

Icehawk_de

@yngve
I still have crashes.
It happens again with an open developer console.

Started with --disable-feature=DevToolsSharedProcessInfobar

yngve

@Icehawk_de Thanks; that means we need to look for some other fix.

A possible workaround may be to not use a detached devtools window; the problem may be related to a warning info bar related to debugging a tab that shares a process with a different tab.

Icehawk_de

I hope you will find and fix the problem.

The console is essential for my work and I would not like to change the browser, because I like Vivaldi.

I now try it with the docked console, but this is not the solution