(In reply to comment #205)
> (In reply to comment #204)
> > Actually that would make the solution *extremely* simple: have SDL1 tag the
> > window as "_NET_WM_BYPASS_COMPOSITOR", "1" - problem solved.
> AFAIK SDL 1 reached end of life - there won't be any official updates.
> Actual problem with legacy code is here, not with "false positives".
No, false positives is what you'll get on your approach - proof: the cause for this discussion.
> Your "fix" causes regression for me. Isn't it a bad fix?
It's not a fix, thus not a bad fix.
It's a trade-off: we've a feature that will either get you less performance boost than another feature - or crashes.
Then what's the "regression"?
You suspend compositing instead and get 3 more extra fps in your shooter?
If you can work around the problem in a way so that we do no more get a "help, kwin crashed after checking this" bugreport about every week, i'll happily vote for that solution.
inb4: If your solution is "disable it by default and remove the config GUI", you're asking for a single target ("you") solution - and i'm dead sure the "secret command to make kwin faster" will show up pretty fas as well - with known consequences.
> Also, you've disabled all Intel cards, while the problem may be specific to
> i915g driver or older mesa versions.
(In reply to comment #205) BYPASS_ COMPOSITOR" , "1" - problem solved.
> (In reply to comment #204)
> > Actually that would make the solution *extremely* simple: have SDL1 tag the
> > window as "_NET_WM_
> AFAIK SDL 1 reached end of life - there won't be any official updates.
> Actual problem with legacy code is here, not with "false positives".
No, false positives is what you'll get on your approach - proof: the cause for this discussion.
> Your "fix" causes regression for me. Isn't it a bad fix?
It's not a fix, thus not a bad fix.
It's a trade-off: we've a feature that will either get you less performance boost than another feature - or crashes.
Then what's the "regression"?
You suspend compositing instead and get 3 more extra fps in your shooter?
If you can work around the problem in a way so that we do no more get a "help, kwin crashed after checking this" bugreport about every week, i'll happily vote for that solution.
inb4: If your solution is "disable it by default and remove the config GUI", you're asking for a single target ("you") solution - and i'm dead sure the "secret command to make kwin faster" will show up pretty fas as well - with known consequences.
> Also, you've disabled all Intel cards, while the problem may be specific to
> i915g driver or older mesa versions.
It seems Sandybridge is affected by the same root cause (see comment #17 and comment #43) and it seems Ubuntu/Compiz meanwhile figured this happens =) /bugs.launchpad .net/ubuntu/ +source/ mesa/+bug/ 947544
https:/