mipmap is dangerous in EXPO and Application Switcher (freezes compiz and/or system)

[triplesqaurednine]

This bug has been confirmed elsewhere (in the Archlinux forums). Basically, if the 'mipmap' option is enabled in EXPO or Application switcher - it will crash compiz and/or your system.

here is the Archlinux thread where users have mentioned the App-switcher crashing. I then tested it on my system and figured out that it is the 'mipmap' option that is bad if enabled;

https://bbs.archlinux.org/viewtopic.php?pid=1098258#p1098258

scrolldown the page, to last 5-6 posts - it is mentioned in there.

I then tested it in EXPO - and verified that enabling it, is also very dangerous and crashes compiz.

In these cases, as far as i know - Nvidia users are affected - i don't have a non-nvidia machine to test on so i can't verfiy if it is happening with other GFX H/W.

I also have another Archer who is (hopefully) going to verfiy this on his machine (just waiting for replies from the rest, who i've told to disable mipmap in those plugins.

cheerz

[triplesqaurednine (triplesquarednine)]

to add to this;

if you enable 'mipmap' in the 'static swither', it doesn't crash compiz but produces graphical artifacts;

http://ompldr.org/vZG5ndw

it would appear something is wrong with the mipmap-related code in compiz. disabling it get rid of the artifacts.

NOTE: there may be other bug reports to do with these plugins, that may actually be caused by having mipmaps, enabled.

I will have a look through bug reports to see if i can find any candidates

cheerz

[triplesqaurednine (triplesquarednine)]

this bug has been confirmed by another Archlinux user on both Intel and Nvidia hardware.

the mipmaps stuff is messed up in compiz. I've asked him to add himself to this report, as well.

[WhyNotHugo (whynothugo)]

I shows artifacts on the static application switcher for me too. However, it also crashes it after serveral uses (between 1-6 tries crashes compiz).

I just crashes on nvidia hardware (I can switch to another TTY, for example), but actually fails even worse on intel hardware. I've tested this on a laptop, and the monitor goes off (with no way of turning it back on), and changing TTY does not work.
If I ssh into the laptop, the dmesg shows an error in the video driver. Killing compiz, or X doesn't help at all. Rebooting (using kexec) results in a still turned off monitor.

Only a shutting down and turning the laptop back on allow me to get back into the system.

[triplesqaurednine (triplesquarednine)]

I believe these errors in dmesg, happened when using mipmaps with (the) various plugins with Nvidia;

[11221.046547] NVRM: Xid (0000:02:00): 31, Ch 00000003, engmask 00000101, intr 10000000
[11221.124494] NVRM: Xid (0000:02:00): 31, Ch 00000003, engmask 00000101, intr 10000000
[11221.175116] NVRM: Xid (0000:02:00): 31, Ch 00000003, engmask 00000101, intr 10000000
[14603.301987] NVRM: Xid (0000:02:00): 31, Ch 00000003, engmask 00000101, intr 10000000
[14607.890637] NVRM: Xid (0000:02:00): 31, Ch 00000003, engmask 00000101, intr 10000000
[15364.301813] NVRM: Xid (0000:02:00): 31, Ch 00000003, engmask 00000101, intr 10000000

[triplesqaurednine (triplesquarednine)]

As a side note - this bug doesn't exist in 0.9.6 - one of the Archers i had test it, couldn't reproduce the bug, but it turns out that he is using 0.9.6 ... so somewhere between 0.9.7 and 0.9.8 this bug was probably introduced.

I know that doesn't narrow it down a whole lot, but still - i thought it was worth mentioning.

[Daniel van Vugt (vanvugt)]

I think this was bug 1006216 and/or bug 1023716. Both appear to be fixed by the new mipmap logic introduced in compiz 0.9.8.0