Reproducible: OpenGL application segfaults Xorg (w/ nvidia driver) every 15 minutes

[Brad Parker]

I have written an application that uses Qt, GStreamer and OpenGL. The application simply plays fullscreen videos in a loop. I'm using the nvidia-current driver on Maverick as my program requires 3D acceleration. Without fail, every 15 minutes, the application receives a SIGSEGV, followed by Xorg also receiving one. The backtrace from Xorg is:

Backtrace:
[ 7785.849] 0: /usr/bin/X (xorg_backtrace+0x28) [0x45c5a8]
[ 7785.849] 1: /usr/bin/X (0x400000+0x5a87d) [0x45a87d]
[ 7785.849] 2: /lib/libpthread.so.0 (0x7fc407208000+0xfb40) [0x7fc407217b40]
[ 7785.849] 3: /usr/lib/xorg/extra-modules/nvidia_drv.so (0x7fc401b80000+0x73a51) [0x7fc401bf3a51]
[ 7785.849] 4: /usr/lib/xorg/extra-modules/nvidia_drv.so (0x7fc401b80000+0x39ddec) [0x7fc401f1ddec]
[ 7785.849] 5: /usr/lib/xorg/extra-modules/nvidia_drv.so (0x7fc401b80000+0x3acef7) [0x7fc401f2cef7]
[ 7785.849] 6: /usr/bin/X (0x400000+0x3f979) [0x43f979]
[ 7785.849] 7: /usr/bin/X (0x400000+0x2187b) [0x42187b]
[ 7785.849] 8: /lib/libc.so.6 (__libc_start_main+0xfe) [0x7fc406173d8e]
[ 7785.849] 9: /usr/bin/X (0x400000+0x21409) [0x421409]
[ 7785.849] Segmentation fault at address 0x1a000c4a150
[ 7785.849]
Caught signal 11 (Segmentation fault). Server aborting

I have also attached a full gdb backtrace from the core that was dumped from my application. I'm not sure if this is an nvidia driver bug or an Xorg one, but I'm able to reproduce it on multiple machines of different hardware configuration, with different nvidia adapters and driver versions. I have tried an Nvidia ION chipset as well as an NVS 300, along with the binary nvidia driver versions 260.19.06-0ubuntu1 (the stock driver available in current Maverick repo) as well as 260.19.36 (downloaded from nvidia.com) and 270.29-0ubuntu1~maverick~xup2 (from ppa:ubuntu-x-swat/x-updates). It appears that either X or the video driver tries to free() an invalid (or null) pointer, and that causes the segfault, but I could be wrong.

Any help is greatly appreciated. Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-core 2:1.9.0-0ubuntu7.3
ProcVersionSignature: Ubuntu 2.6.35-27.48-generic 2.6.35.11
Uname: Linux 2.6.35-27-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 260.19.06 Mon Sep 13 04:29:19 PDT 2010
 GCC version: gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5)
Architecture: amd64
Date: Thu Mar 3 21:28:50 2011
DkmsStatus: nvidia-current, 260.19.06, 2.6.35-27-generic, x86_64: installed
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: Supermicro X8DT6
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-27-generic root=UUID=7b9f3db9-205c-483e-aac8-fb96339e4df2 ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: xorg-server
dmi.bios.date: 09/14/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.0a
dmi.board.asset.tag: 1234567890
dmi.board.name: X8DT6
dmi.board.vendor: Supermicro
dmi.board.version: 1234567890
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 1234567890
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0a:bd09/14/2010:svnSupermicro:pnX8DT6:pvr1234567890:rvnSupermicro:rnX8DT6:rvr1234567890:cvnSupermicro:ct17:cvr1234567890:
dmi.product.name: X8DT6
dmi.product.version: 1234567890
dmi.sys.vendor: Supermicro
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: maverick
 architecture: x86_64
 kernel: 2.6.35-27-generic

[Brad Parker (cbparker)]

Also, not sure if this means anything but the same code compiles and runs without issues on Windows.

[Brad Parker (cbparker)]

Also I have attached a gdb session (attachment is called xorg-gdb.txt) for Xorg itself.

[bugbot (bugbot)]

Hey Brad,

Hi, have you had a chance to test if this bug is still present in natty?

If it does (and if you're the original reporter), please boot into natty
and run the command:

  apport-collect <bug-number>

which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run this right after reproducing the problem.)

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.