Chromium/Opera “randomly” not rendering in i3
up vote
2
down vote
favorite
I'm on 18.04, using i3, and sometimes when I go from some workspace to a workspace containing chromium or opera, those windows aren't redrawing. I can still press ctrl+s to open a "save to" popup, which renders fine.
The behaviour is quite quirky, and it happens maybe twice a day, and I can't seem to find a way to reproduce it reliably. Here are a bunch of observations:
- I think I usually have cpu usage of 20%+ (according to
mpstat 2 1 | awk '$12 ~ /[0-9.]+/ { print 100 - $12"%" }'), when it happens - After it happens, I can't use
mod+q(to quit window from i3),ctrl+q(to quit from opera), but I can seem to be able to runctrl+wto quit a tab, even if I don't see it immediately. When I reopen opera, that tab is gone - I can quit the process by running
fkill opera, or the appropriate amount ofpkill opera
- About a week ago, I was running ubuntu 16.04 with i3, and I already had problems. I thought maybe getting a fresh install would help, but it didn't. It worked fine for a few days, but after ~3 days, I started getting the errors again, so maybe there's a package that I installed that broke it?
- Opera/Chromium didn't always do this. It started about 1-2 months ago
- When it does the rendering bug, it simply shows whatever was occupying those pixels in the previous workspace.
- I can still open terminals and other windows on that workspace, and they will display just fine. If I then shrink or remove them, the pixels previously occupied by that new window will now have changed to whatever was in those windows
- the mouse cursor doesn't leave a trail
- I think it happened with other resource-heavy windows, but I don't remember for sure
I haven't managed to isolate the conditions and versions of the browsers, i3, or other packages. I'm running the latest stable of everything, as far as I know.
From what I can tell, it could be anything from a driver error, to a bug in some package. I'm not even sure where to look for possible logs of this
Any suggestions? Does this happen to anyone else? Should I report this to opera/chrome? Should I also file a bug report for i3? I'm very confused
18.04 chromium workspaces i3-wm opera
asked Nov 15 at 11:10
towc
15119
add a comment |
up vote
2
down vote
favorite
I'm on 18.04, using i3, and sometimes when I go from some workspace to a workspace containing chromium or opera, those windows aren't redrawing. I can still press ctrl+s to open a "save to" popup, which renders fine.
The behaviour is quite quirky, and it happens maybe twice a day, and I can't seem to find a way to reproduce it reliably. Here are a bunch of observations:
- I think I usually have cpu usage of 20%+ (according to
mpstat 2 1 | awk '$12 ~ /[0-9.]+/ { print 100 - $12"%" }'), when it happens - After it happens, I can't use
mod+q(to quit window from i3),ctrl+q(to quit from opera), but I can seem to be able to runctrl+wto quit a tab, even if I don't see it immediately. When I reopen opera, that tab is gone - I can quit the process by running
fkill opera, or the appropriate amount ofpkill opera
- About a week ago, I was running ubuntu 16.04 with i3, and I already had problems. I thought maybe getting a fresh install would help, but it didn't. It worked fine for a few days, but after ~3 days, I started getting the errors again, so maybe there's a package that I installed that broke it?
- Opera/Chromium didn't always do this. It started about 1-2 months ago
- When it does the rendering bug, it simply shows whatever was occupying those pixels in the previous workspace.
- I can still open terminals and other windows on that workspace, and they will display just fine. If I then shrink or remove them, the pixels previously occupied by that new window will now have changed to whatever was in those windows
- the mouse cursor doesn't leave a trail
- I think it happened with other resource-heavy windows, but I don't remember for sure
I haven't managed to isolate the conditions and versions of the browsers, i3, or other packages. I'm running the latest stable of everything, as far as I know.
From what I can tell, it could be anything from a driver error, to a bug in some package. I'm not even sure where to look for possible logs of this
Any suggestions? Does this happen to anyone else? Should I report this to opera/chrome? Should I also file a bug report for i3? I'm very confused
18.04 chromium workspaces i3-wm opera
asked Nov 15 at 11:10
towc
15119
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I'm on 18.04, using i3, and sometimes when I go from some workspace to a workspace containing chromium or opera, those windows aren't redrawing. I can still press ctrl+s to open a "save to" popup, which renders fine.
The behaviour is quite quirky, and it happens maybe twice a day, and I can't seem to find a way to reproduce it reliably. Here are a bunch of observations:
- I think I usually have cpu usage of 20%+ (according to
mpstat 2 1 | awk '$12 ~ /[0-9.]+/ { print 100 - $12"%" }'), when it happens - After it happens, I can't use
mod+q(to quit window from i3),ctrl+q(to quit from opera), but I can seem to be able to runctrl+wto quit a tab, even if I don't see it immediately. When I reopen opera, that tab is gone - I can quit the process by running
fkill opera, or the appropriate amount ofpkill opera
- About a week ago, I was running ubuntu 16.04 with i3, and I already had problems. I thought maybe getting a fresh install would help, but it didn't. It worked fine for a few days, but after ~3 days, I started getting the errors again, so maybe there's a package that I installed that broke it?
- Opera/Chromium didn't always do this. It started about 1-2 months ago
- When it does the rendering bug, it simply shows whatever was occupying those pixels in the previous workspace.
- I can still open terminals and other windows on that workspace, and they will display just fine. If I then shrink or remove them, the pixels previously occupied by that new window will now have changed to whatever was in those windows
- the mouse cursor doesn't leave a trail
- I think it happened with other resource-heavy windows, but I don't remember for sure
I haven't managed to isolate the conditions and versions of the browsers, i3, or other packages. I'm running the latest stable of everything, as far as I know.
From what I can tell, it could be anything from a driver error, to a bug in some package. I'm not even sure where to look for possible logs of this
Any suggestions? Does this happen to anyone else? Should I report this to opera/chrome? Should I also file a bug report for i3? I'm very confused
18.04 chromium workspaces i3-wm opera
asked Nov 15 at 11:10
towc
15119
I'm on 18.04, using i3, and sometimes when I go from some workspace to a workspace containing chromium or opera, those windows aren't redrawing. I can still press ctrl+s to open a "save to" popup, which renders fine.
The behaviour is quite quirky, and it happens maybe twice a day, and I can't seem to find a way to reproduce it reliably. Here are a bunch of observations:
- I think I usually have cpu usage of 20%+ (according to
mpstat 2 1 | awk '$12 ~ /[0-9.]+/ { print 100 - $12"%" }'), when it happens - After it happens, I can't use
mod+q(to quit window from i3),ctrl+q(to quit from opera), but I can seem to be able to runctrl+wto quit a tab, even if I don't see it immediately. When I reopen opera, that tab is gone - I can quit the process by running
fkill opera, or the appropriate amount ofpkill opera
- About a week ago, I was running ubuntu 16.04 with i3, and I already had problems. I thought maybe getting a fresh install would help, but it didn't. It worked fine for a few days, but after ~3 days, I started getting the errors again, so maybe there's a package that I installed that broke it?
- Opera/Chromium didn't always do this. It started about 1-2 months ago
- When it does the rendering bug, it simply shows whatever was occupying those pixels in the previous workspace.
- I can still open terminals and other windows on that workspace, and they will display just fine. If I then shrink or remove them, the pixels previously occupied by that new window will now have changed to whatever was in those windows
- the mouse cursor doesn't leave a trail
- I think it happened with other resource-heavy windows, but I don't remember for sure
I haven't managed to isolate the conditions and versions of the browsers, i3, or other packages. I'm running the latest stable of everything, as far as I know.
From what I can tell, it could be anything from a driver error, to a bug in some package. I'm not even sure where to look for possible logs of this
Any suggestions? Does this happen to anyone else? Should I report this to opera/chrome? Should I also file a bug report for i3? I'm very confused
18.04 chromium workspaces i3-wm opera
18.04 chromium workspaces i3-wm opera
asked Nov 15 at 11:10
towc
15119
asked Nov 15 at 11:10
towc
15119
asked Nov 15 at 11:10
towc
15119
asked Nov 15 at 11:10
towc
15119
asked Nov 15 at 11:10
towc
15119
15119
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1093147%2fchromium-opera-randomly-not-rendering-in-i3%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
