Segfault in libGL.so.319.12[a19fe000+d2000]

Hi Nvidia,

I’m trying 319.12 drivers today.

I’m trying to run Quake Live. First game is always normal, I can go in and out of full screen etc. But when I leave the game and try to enter a different server, the plugin crashes. It’s always a crash in libGL.so:

[ 174.698408] plugin-containe[3451]: segfault at 700 ip a1a67b20 sp b304f370 error 4 in libGL.so.319.12[a19fe000+d2000]
[ 210.794712] plugin-containe[3506]: segfault at 700 ip a1a67b20 sp b304f370 error 4 in libGL.so.319.12[a19fe000+d2000]
[ 747.618687] plugin-containe[3846]: segfault at 700 ip a1a67b20 sp b3077370 error 4 in libGL.so.319.12[a19fe000+d2000]
[ 1001.926350] plugin-containe[4126]: segfault at 700 ip a1a67b20 sp b304f370 error 4 in libGL.so.319.12[a19fe000+d2000]
[ 1044.528529] plugin-containe[4176]: segfault at 700 ip a1a67b20 sp b304f370 error 4 in libGL.so.319.12[a19fe000+d2000]
[ 1105.963369] plugin-containe[4236]: segfault at 700 ip a1967b20 sp b2f77370 error 4 in libGL.so.319.12[a18fe000+d2000]
[ 1120.510963] plugin-containe[4251]: segfault at 700 ip a1a67b20 sp b3077370 error 4 in libGL.so.319.12[a19fe000+d2000]

Please, let me know how I can help debug this problem.

Best regards,

Lam
nvidia-bug-report.log.gz (110 KB)

I’ve been having weird segmentation faults with Quake Live lately as well, but they occur on both my Nvidia and ATI system. In my case I can’t even get to the server browser as it segfaults before then.

I’m using QLPrism, and have tried both 32bit and 64bit client. Haven’t got around to trying normal Firefox again though.

I’m probably having a different issue, though, as this occurs on 313 and I haven’t tested 319 yet.

Maybe you’ve used /block in game, it’s famously breaking QL plugin (so it crashes on login). You’ll either need to clean up blocklist on Windows, or ask QL Support (or sponge) to do it for you.

My QL works fine on 313. On 319 it works for one game, but crashes each time you leave that first game and want to play again.

Also, a friend is using 319.17 on his x86-64 and it works for him.

So this bug either depedns on something specific to my system (like X.org version) or it’s only crashing on i686.

Yes, you’re correct I thought that was just a coincidence! Serves me right for trying to block an annoying player.