As suggested by Firerat, I am starting a new thread on this, separate from the general vivaldi thread. I'm interested to know if anyone else has seen this behaviour. The version of vivaldi is 2.6.1566.49 (correction:2.7.1628.33), installed in Slackware as a slackbuild. I think there were similar crashes in my previous version but this one is definitely worse.

1) The freeze is in input; both mouse and keyboard are affected. As far as I can see, video remains normal. But because the keyboard is dead, there is no way of escaping from the program or from X, for example by switching to a console. I have to switch off the machine.

2) The problem is intermittent and occasional. I don't know what sets it off, but it usually occurs during input and I think always when the mouse cursor is in its text form (I), not an arrow shape. It has happened when I was mousing over printed text in Yahoo, but again the cursor was in its text form.

3) Retrospective checks of messages and syslog show no suspicious messages at the time of the freeze.

4) Adding an alternative usb keyboard or mouse did not help.

Any ideas?

Did you use ruario's script https://gist.github.com/ruario/dcbba...cc883542ff7ace?

1 members found this post helpful.

Not so far. I've been using the official slackbuild, which is probably not the latest version. But thanks for the tip. I'll try reinstalling from that script.

PS: I gave the wrong version in my original post. /var/log/packages gives the package name as vivaldi-2.7.1628.33-x86_64-1_SBo. 2.6.1566.49 is in /var/log/removed.

PPS: OK, I'm now running 2.8.1664.36. Let's see if this one is more stable.

It happened again today and this was with the new version. So I tried to ssh in from my laptop. ssh gave me "connect to host bigboy: no route to host". So I tried pinging. The name bigboy resolved correctly to 192.168.2.100 but the result was "Destination host unreachable". When I started the desktop again, I checked that sshd is a running daemon. It is.

So it looks as if it's not just vivaldi that freezes. It is somehow stopping the whole system. That is very bad. I am typing this post in graphical links but that's only a temporary fix. If I can't find a solution to this, I will go back to Firefox.

I assume ssh works fine under ordinary circumstance.

can you gauge how hard the cpu is working ( fan speed )
what about disk activity?
do you have swap?

I've seen system become unresponsive due to lack of memory
things appear to freeze but are actually very, very slow
From what you describe I don't think that is the case here, but worth keeping in mind.

under these no/low mem situations, I find ssh normally 'hangs' and sometimes eventually connects and I can address the problem ( I normally know what it is as I did it ) .

I get "No route to host" if I've caused a "full on crash"

A possibility springs to mind, faulty ram
it could be unrelated to vivaldi, you are just using that "most of the time"
different version are affected, and no-one else seems to be affected.

available on many diagnostic CD/DVD/USB boot tools
https://www.memtest.org/

you can usually find it on Distro install disks
you can even add it to lilo/grub
https://slackbuilds.org/repository/1...tem/memtest86/

it may be worth running that to eliminate faulty ram being the cause.

I'm beginning to wonder if it's a cpu thing. My messages file shows that I am having occasional overheat events when the kernel throttles back the cpu. Usually that causes no problems. But when I was building software in LFS, which is a fairly memory-intensive process, I never got a freeze like this.

As far as memory is concerned, I have 4G core and a 5G swap partition.

PS: I just ran top and the first three processes are all vivaldi!
PPS: ps ax shows that there are 12 vivaldi processes altogether! And that is with one open tab. I usually have 2 or 3.

unless high cpu temp. is unexpected ( you aren't asking your cpu to do too much ) I wouldn't worry about that.

yes, I guess compiling would have problems with faulty memory
still, memtest is a definitive "ram is fine"

It's not unusual to see multiple processes with a browser
I've never used Vivaldi, so I don't know if that is unusual or not.

How high is the cpu/mem use?
Does that use make sense, for instance: some script laden webpage open that auto refreshes?

With Firefox I can "firefox --safe-mode" to start without loading extensions etc.
anything similar with Vivaldi ?

The top vivaldi process shows cpu 1.7 and mem 6.8. I don't know what the units are. The other processes are less intensive. Whether these figures make sense or not I have no idea. I don't know what websites do. What is currently being displayed is my gmail account in the new standard format. But all the freezes so far have occurred in LQ or (on one occasion) in Yahoo.

The equivalent of safe mode in vivaldi is incognito. I'm trying it out now. There are still 10 processes and the top one is about the same size. I think I'll use it in my usual way for a while and see what happens.

they will be %
given they are so low I don't see them as a problem.

Another thing I've noticed in vivaldi as compared with FF is that it takes a long time to come up. That suggests to me that it is a more intensive user of resources. Maybe it's just too big for my machine. That would explain why the problem only showed up with the latest versions.

PS: I just got in with ssh from littleboy. No problems at all, so the earlier failure definitely meant the system was down.

I thought running in incognito mode would be the solution. No crashes yesterday. Then today it happened twice! I've had enough. I've reinstalled FF and I'm using it now. No more Vivaldi for me.

Isn't absolutely everything logged in Linux?

Processes started/stopped, files touched, opened, closed etc. etc...
Surely there must be something happening in the minutes up to (that totally unacceptable) break-down?

What do they say over at the Vivaldi forum? Problem doesn't seem to be widespread?

Btw. remember studying log file analyzers...


Sorry, but I simply can't understand why your Linux logs wouldn't provide the answer!

Enlighten me, please!

seemingly random crashes/freezes described here
https://www.linuxquestions.org/quest...7/#post6041153

we found the cause with that one

Yes, when Linux is running. Not after it has crashed. If it were only a X freeze, that would have been logged.
I don't know of any log that keeps permanent track of non-daemon processes started or stopped. In a running system, you can check what's currently running with ps, and check open files in /proc, but in a crashed system? If someone can suggest a diagnostic, fine, but I haven't got time to mess around with an incredibly complex program that includes about ten different sub-processes just to stop it crashing when I want to make a post here.

1 members found this post helpful.

I assume the memtest diagnostics passed without error