New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Video Freeze , audio continues on media players #494
Comments
|
The problem happen also with video games. |
|
The master version hasn't been updated in a year. This issue is newer than that and I can reproduce it on all my archlinux computers when building compton from git using the compton-git package in the aur. |
|
Really strange, using the compton-git fix it for me. |
|
This repo hasn't been updated over a year as you can see. Compton that archlinux packages(that I use) is from yshui. Since compton hasn't been updated for long time it's some dependency (update) that broke compton and compton isn't updated to reflect that change. I possibly don't have this freeze issue now. It's hard to know since it's random. @ekce Can you try compton with |
|
@BurhanDanger I'll try it when I get a chance. A couple things I should have mentioned:
|
|
@mnivoliez , the game you mentioned , is it opengl accelerated ?
Face this as well. Thought it's chrome being chrome. |
|
A bunch of games, all using opengl or used through wine.
Envoyé par BlueMail
Le 30 mai 2018 à 19:34, à 19:34, BurhanDanger <notifications@github.com> a écrit:
…
@mnivoliez , the game you mentioned , is it opengl accelerated ?
> I've noticed the freezes affecting web browsers as well.
Face this as well. Thought it's chrome being chrome.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#494 (comment)
|
|
Experiencing the same issue on my XPS 13 (9350, i7 6560U, Intel Iris Graphics 540), using i3wm. I noticed that displaying the i3bar (using the super key as) unfreezes the display. I can also provide some more details if you want (logs, etc.). |
|
Same issue on XPS 9560 on both intel GPU and on NVIDIA gpu. |
|
This happens to me too. using i3-gaps, nvidia drivers. Same in games too (tried with stepmania and enter the gungeon primarily) |
|
The same here. Switching backend to xrender helps, but it's a bit choppy experience compared to glx. |
|
Same here! |
|
The last commit is 1 y/o, 18 pull requests that will never be merged, Wayland is around the corner, I don't think Compton is going anywhere now, sadly... |
|
@JPenuchot I'm maintaining a bug fix fork. But I can't seem to reproduce this bug... |
|
same in games and video |
|
OK, may I ask what window manager do you guys use? Sounds like you are all using i3? |
|
Yep, i3 on my side |
|
Yep, I am using i3-gaps |
|
i3-gaps too |
|
AwesomeWM |
|
Confirming that it happens on openbox too, I was using i3-gaps before
…-- att. Fernando Vasquez --
On Fri, Aug 17, 2018 at 9:10 PM, Alex Kir ***@***.***> wrote:
AwesomeWM
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#494 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AKojScrxIcnWyRlMuHcq8CEhrv2zzI_Tks5uR4WggaJpZM4T939H>
.
|
|
Xfwm4 |
|
Hmm, I was thinking this might be because compton doesn't interact well with i3. But no, it happens with other WM as well. Now I'm lost, I'm using AwesomeWM, and this problem has never happened to me. I need a way to reproduce this before I can fix this. |
|
Are there any logs to look for when it happens? Or maybe I can try to troubleshoot it locally, just tell me where to look :) I didn't find any messages in journal nor in .xsession-errors. |
|
I doubt there are logs for that. |
|
I don't think it really has anything to do with resolution, it happens on both my monitor and my laptop screen 1080p and 720p respectively, anyway, here are my settings (which are pretty basic if I may add) I'm using an intel internal graphics card, if that works for anything |
|
@enanajmain A workaround is in place (which might cause performance problems), and I'm looking into the real cause of the problem. |
|
Thanks for still looking into it! |
|
I think I fully understand it now. Turns out to be a Xlib bug. Lesson learned: never use Xlib, always use xcb |
|
Plan is to switch at least the event handling bit to xcb. Will definitely need some testers. |
|
Very cool of you to take care of that issue, thanks a lot |
|
Done. Can someone try this branch: yshui/compton@next ? (Beware that branch has extra changes that contain bugs. If you encounter other problems unrelated to screen freeze, please open a issue on my repo mentioning the name of the branch.) (This branch is known to crash due to some xlib/xcb interoperability issues) |
|
@yshui I was using Ubuntu 17.10 with compton in their official repo. Yesterday I switched to Ubuntu 18.04. Now, before I went on to install your branch, I wanted to record and test if the problem still persists. I don't know why, but the problem has fixed itself. I've been watching videos on mpv and chromium-browser while constantly pressing The current version on official Ubuntu repo is N.B I think it's worth mentioning that the chromium browser has had a massive upgrade. Maybe that has something to do with it. |
|
I am running your next branch, it seems to fix the issue as well. |
|
I'm seeing regular crashes on the Edit: I updated the |
|
Been running on the |
|
Have run the branch for a day. No crashes so far and the glx backend works fine. |
|
I tried yshui/compton@next this solves the problem for me! I still get these messages: Thanks for making an effort! This was a very frustrating problem, I even switched to sway to try it out, it's great, but the stable branch does not have the features I want yet. |
|
Same here, been using it daily for 2 days and got no problem so far. Good work ! Do you have a donation link or something ? |
|
Making the switch to that branch on my setup, will see if things work alright. |
|
@JPenuchot I would rather have helping hands than donations. |
|
Haven't seen ANY freezes so far after a day of use. Thank you~ |
|
I'm closing this now since it looks like yshui 's next branch solved this(which also needs testing for regression). Test that and Feel free to comment here or open issue on yshui's fork mentioning which branch you used. |
@yshui What can I help you with specifically? :-) |
|
@psychon I composed a short list of things I can think of right now: |
|
@yshui Okay, which branch do you want me to work against? "Move to XCB" sounds like something that I can easily do and I touched pixman's API once or twice and might be able to "do stuff with regions". |
|
@psychon I'm currently doing the pixman conversion, so maybe you could pick up the xcb conversion? You can base your work on the next branch. |
|
I've decided to test the old version of compton one more time. Interestingly I wasn't able to reproduce the issue. It might have something to do with the updated kernel (currently 4.18.8-200.fc28.x86_64). I don't see anything else from graphics stack updated. Just wanted to let you know. |
|
@valsoray17 The screen freeze is caused by an extremely timing dependent race condition. The bug can totally be there in the old version (BTW, it's a Xlib bug) but just doesn't manifest. |
|
Thanks for the explanation, will monitor the old version more |
|
@yshui, I was using next branch of your fork for a week. I just experienced two crashes today. Any idea? |
|
@enanajmain please open a bug report |
Platform: archlinux x86_64
kern: 4.16.8
GPU, drivers, and screen setup: i915 (intel i5-4210U CPU @ 1.70GHz)
modsettings
i3 on xorg(xorg-server 1.19.6+13+gd0d1a694f-2), mesa 18.0.3-1
Compton version: compton 0.1_beta2.5-11
Steps of reproduction
Run compton with following
Play video in mpv or google-chrome (with h/w decode or s/w decode) in fullscreen. After sometime videoframe freezes at a point ,but audio keeps continuing. Whole system doesn't freeze. Switch from fullscreen , video frame syncs to appropriate frame and continues.
Happens randomly. Without compositor video plays smoothly.
Expected behavior
Play video smoothly without freezing video.
The text was updated successfully, but these errors were encountered: