google chrome and chromium freezing

78 views
Skip to first unread message

cooloutac

unread,
Apr 19, 2017, 12:05:03 AM4/19/17
to qubes-users
Just started today dunno what the heck is up with that. In a bunch of my appvms. It wasn't the dom0 update that error ed my vms this issue was happening right before that. My Mother had told me she had tried to update dom0, or thought she did already, but apparently it didn't update. I bet it errored or something. She said she had no freezing at all in a few vms and updated right before she got off. So I'm thinking it started after that failed dom0 update.

But I also had noticed a week prior that chrome was not showing, for example, the live chat popup button on amazon.com. with no extensions nothing. ah no they probably changed their chat to allow some non https connection or something I bet. and in the default disposable I use with firefox that is not the case. sorry fro the stream of consciousness.

Regardless, I'm still using firefox for right now cause the freezing in the suspect vms has not happened with firefox for some reason. Over the years I always go back and forth to whichever one is less abused for the current time being.

But I'm so paranoid right now I'm gonna wipe the entire system. Actually even keepassx vault froze on me... I hope its just a hardware failure, fedora is good about monitoring hdd though...but yikes.

anybody have any encouraging words for me? lol.

Reg Tiangha

unread,
Apr 19, 2017, 12:11:51 AM4/19/17
to qubes...@googlegroups.com
No encouraging words, but I've noticed freezing today too. Not in
Chrome, but in things like nautilus and gnome-terminal. It's sporadic,
though and I haven't nailed anything down yet except it was something in
the latest batch of stable updates.

My coldkernel VMs won't boot either, and it's very similar to these
threads (ErrorHandler: BadAccess (attempt to access private resource
denied), but they'll boot properly with a dom0 vm kernel):

grsecurity kernel 4.9.20 not working - Qubes ErrorHandler: BadAccess MIT-SHM

https://groups.google.com/forum/#!topic/qubes-users/2X8wi5XebJc


[bug] qubes-guid crashes when putting debian-9 VM in true XFCE fullscreen

https://groups.google.com/forum/#!topic/qubes-users/d0lsqBbDYc0


Unsolicited feedback on qubes-issue #2455

https://groups.google.com/forum/#!topic/qubes-users/NSZEZD_k7KE


I don't know how to fix any of this.


cooloutac

unread,
Apr 19, 2017, 12:16:29 AM4/19/17
to qubes-users

delete this thread please don't know why I posted it. Its obviously more then a google chrome and chromium issue. I don't think its hardware issue cause its program affected, or maybe its vm affected I didn't even try to open terminal when it happened, not that it matters at this point, also probably worth checking the memory chips at least.

Is it possible to run a memory checker from a usb stick? Anybody got a recommended program to use i haven't used one in years. maybe my bios has a checker.

cooloutac

unread,
Apr 19, 2017, 12:20:10 AM4/19/17
to qubes-users, r...@reginaldtiangha.com

you becoming my favorite poster man Ty for being part of Qubes.

Andrew David Wong

unread,
Apr 19, 2017, 12:40:19 PM4/19/17
to Reg Tiangha, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
I, too, have noticed very frequent Chromium freezing recently. For me,
Chromium browser seems to be the only app/window that freezes, and I
have to restart the whole AppVM when it does. The problem seems to
have started right after updating qubes-libvchan-xen to 3.2.1, but
this is merely an observed correlation.

Issue created:

https://github.com/QubesOS/qubes-issues/issues/2765

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJY95LgAAoJENtN07w5UDAwb8sP/2EZ0PfTeByuKgdcVuW4tVCk
1CCGsG2IzIcSR8TD5ic953gawJFk2/3jeKmZNlSWl344zMPXX2B3jt2dN76DXf4K
+hrzV8x54kQefgX5BhAXcjCzX3YluzEYoIUzAFnSYIapVUikijatLrVMWkTjXyj+
lHw02kfEZ0hf66ASxf7Vm635SOCRf0dQS17CishrTEGDQH/ysnBNudPv4MAxswRq
if6Skkke6OB0l4wRT5IzmIl91h/PbmGdcrIUtUlc818iYDVgEu9xBkj9Gn4t9/Ix
/GbMfuBmJ2boX+9RcNiLAOSw1HjRgmjm/jLzarNR90xDmNFTWR74CNsWIugH9lDX
lYsOzCef8nPm7a7rgFdI7Rje7kivWcNn2omrL8XrcY3M2IgmF67DBIf8Bc6UvPBk
0nB+rs7zrYfkPUIr6mAVjNKS5v8vVBJpjJ/XntqZouzXzuMhxIGtKfYw1DJB4JWj
pqdmVOIaHvA/MGuEJQ66/rSxUryqnAzGvdsy6X2lcFTg8pxmdHHb97hZNNo1Joqe
gvu7iiZ9+sd2SX6wbKEWNR6mbfxeydp8Q1aJOfvDdkIGRVOrhIYW3ddYjnHJoUVH
gwPb5tQpENC24OzxH+wFBNWRGuzfjWUr34aHI8MvBHtdTyWKM3rosybul1iBGj1R
JtcnmYblHO2EVfmRnQRo
=29KB
-----END PGP SIGNATURE-----

Andrew David Wong

unread,
Apr 19, 2017, 12:44:23 PM4/19/17
to Reg Tiangha, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

I believe this bug is different from the ones described in these other
three threads.

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJY95PeAAoJENtN07w5UDAwY/EP/RxqBGLMxT1vFjLx+bF3ES1E
Pz+0odzJbVwj3A2Ww9AXPIERhGj74tGmZE2DS7iyxgcYlSvrWAww+M6SdgAZmDR2
DSptZeVKtcbRlmNb6WMkBil8MFwL2PlVzNLlAOj0emOKMTIenR+56/H69XUA0FNF
R3gRdGgD/rJVI0/0jwrupuI1ZGjt3yRmurMxXMSvlFPcfJJypemk7cTm1HHDi+Or
Kl1OGE9b71ang3Ege4SQrn0lH5d8mX3b+SkjlkebuUXXhJE/Q6RieftFqpv9fgwI
LkzVadTf/xBxTH9DezOwuGP4AKci+Qdz6TLaHC+Am4c4yG/kaNnqXYVnWCSZ2FEc
+ZXchiSFxr0M+yCK6rnwEa4n/D5K2/ZznjsQNcm35W5+aHDKNDHye8sLFG65G0Jt
/rMvQ+d3vlW3gghVTc+NeWRu1/yGHi4Jm5Btv6Wb26W8e1EURzVGUcsKXPKyToAD
B42j1sXv9TktfwOGzLynnKC9QEbzUsmX5eVid4bJH/U/e8aC48k5gUmNnwxHdMyH
L/avwmybgXzDozdj2qPj4PaIWRjY8qGugsgb35nQD213YPbySNSwTfeGpTH43W+/
4yy6LFTn1+WBVQhsbq0u3zIBAenyseJzTrwRHygMg8iPQPR3L3ijl99vEx0K23zr
oFhqe9T3z+a2CwCdRQJI
=Zbw4
-----END PGP SIGNATURE-----

Reg Tiangha

unread,
Apr 19, 2017, 12:52:26 PM4/19/17
to qubes...@googlegroups.com
Yeah, it's probably a different bug.

Andrew, what's your hardware configuration? Specifically, RAM and
whether or not you're running on an SSD or a hard drive?

I'm still trying to resolve some of my other issues that I'm
experiencing because of the update, but I'm noticing a lot more RAM
usage (including a lot of swap being used; 600MB in dom0 right now on my
laptop when in the past, it's usually held at 0MB, but my hard drive
light isn't on when the freezing occurs and there doesn't seem to be
anything abnormal when running top on the VM) and I'm wondering if the
'freezing' is related, and potentially more noticeable to those who have
a lot of swap in use. Don't have time to really delve into it at the
moment though, so it's also anecdotal.

I have noticed though that if I launch xterm or any other app on the VM
using Qubes Manager, that as soon as that new window pops up, everything
becomes responsive again. Also, that when the freezes occur, I sometimes
can't connect to the VM with virsh until it becomes unstuck again.


Andrew David Wong

unread,
Apr 19, 2017, 4:13:04 PM4/19/17
to Reg Tiangha, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

> Yeah, it's probably a different bug.
>
> Andrew, what's your hardware configuration? Specifically, RAM and
> whether or not you're running on an SSD or a hard drive?
>

20 GB RAM, SSD

> I'm still trying to resolve some of my other issues that I'm
> experiencing because of the update, but I'm noticing a lot more RAM
> usage (including a lot of swap being used; 600MB in dom0 right now on my
> laptop when in the past, it's usually held at 0MB, but my hard drive
> light isn't on when the freezing occurs and there doesn't seem to be
> anything abnormal when running top on the VM) and I'm wondering if the
> 'freezing' is related, and potentially more noticeable to those who have
> a lot of swap in use. Don't have time to really delve into it at the
> moment though, so it's also anecdotal.
>

Hm. Haven't noticed anything like that, but I haven't really been
looking for it. I'll post here again if I notice it.

> I have noticed though that if I launch xterm or any other app on the VM
> using Qubes Manager, that as soon as that new window pops up, everything
> becomes responsive again. Also, that when the freezes occur, I sometimes
> can't connect to the VM with virsh until it becomes unstuck again.
>

Ok, thanks. I'll trying launching an xterm next time I have a frozen VM.

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJY98S6AAoJENtN07w5UDAwn84QAKTeETVeQwQ4N2VIAVukW06V
dqRsKQsXQoJIO3G0+CAzT/EcbBvXbla6bi8taeUJfk5MPmTZspFM2OeWe7ZcwZVH
hAIk+P7Q+cYnPNThK/K1ZncAKSTwsixB+/64pzNdXvzui/t2FOff4bD68wd4Zs1S
l35HtkPHWpAEuIXyXwJBqWo4koiZ6LoDCFd9fLCDi1iC4BePFKqz6Na4FwJXySGQ
b+t6JTCaZCP66P26vwT3rm1KvgcwfYSkKcY1C0GQ0OCd7wjQDMaANsmnN5srsyEi
VFW9ibyunWmfs70l09ESbfd6QOnt9r40shThvpIUPYWXfUIVInAZKreqbBgPrPy5
c4OlH2B5LtMb3CK62LxPff7H08aafTn8gclRbRlaBtV4gkOIuczajjTvVSd3GAfZ
EnOo8ZfUXlGXqXy+LxfAmqFHwvGkcFrLfZiKwIAmXQ2oh1d62ZJs/+9fmQ/7WOTy
U18/KpZQvlDQbArs+bha7EzHacKO6SmZ7E7157ojE+q5C8EZzt6dsR5Lv3vSq+hS
qbYH8EZ5vLHJeK4m069gNBnkl1/0liLyfsc1X6gIB5vEfqhaB8TzAM4lUlZ9Cd2e
Gufx3NEuhdHW8Hj7NFYdfc5lcmSC+/xqFblinVjzUc6qEe+nF/cm+g3J3qMP8sxr
a014v6k1lUebTXASbaOL
=65RC
-----END PGP SIGNATURE-----

cooloutac

unread,
Apr 19, 2017, 5:20:13 PM4/19/17
to qubes-users, r...@reginaldtiangha.com

yes I think I noticed this too. When I got the freeze instead of shutting down vm I launched the terminal from it. was going to kill process and then realized it was working again.

The machine this is happening on has 500gb ssd and 16gb ram, iommu on, intel gpu, intel 5 cpu.

Another machine doesn't have this issue, and it has no iommu, no ssd, and old amd cpu, older nvidia gpu. This machine also never got the missing kernel bug. And has had no restored backup vms.

Legacy boot on both.

In fact I wonder if the freezing is happening on those vms that were affected. Because it happened when updating my fedora-24 clone from the qubes-manager gui. When I went to hit enter to close the vm, window was frozen so I manually shut it down. This hasn't happened on any of the other templates, and in fact, this was the only template that had a missing kernel problem. Could it be related? Never had any freezing before the day of dom0 update.

none of my untrusted vms were affected with the dom0 update bug. I will start using chrome in them and see if it freezes.

cooloutac

unread,
Apr 19, 2017, 7:00:07 PM4/19/17
to qubes-users, r...@reginaldtiangha.com
Well this time it happened again and on the debian-8-clone-1 template that didn't have a missing kernel issue. wow.

And yes I can confirm what Reg Tiangha said... I opened a gnome-terminal when the update froze. And as soon as I did that you could see the y's pop on the screen I was hitting for yes to update. But then both terminals froze. So I simply just once again opened a second gnome-terminal and they everything unfroze immediately and updates kicked into action.

No idea what that means but hopefully thats a clue for a dev.

cooloutac

unread,
Apr 19, 2017, 8:57:31 PM4/19/17
to qubes-users, r...@reginaldtiangha.com

Ya I don't think this is related to the missing kernel issue, or at least that wasn't the direct cause it seems.

Reply all
Reply to author
Forward
0 new messages