Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#42639 - [nvidia-340xx] memory leak causes Xorg to hang

Attached to Project: Arch Linux
Opened by kogepathic (yoj2ce) - Friday, 31 October 2014, 18:27 GMT
Last edited by Laurent Carlier (lordheavy) - Sunday, 14 December 2014, 17:58 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
The NVidia driver contains a regression whereby VRAM is not deallocated and eventually leads to Xorg hang when the driver cannot allocate more VRAM. Issue observed on MacBook Pro 4,1 (Early 2008) with NVidia 8600M GT (256MB variant).

NVidia-settings reports 98-99% (253-255MB) VRAM used when running 2D productivity applications such as Chrome, xterm, and nvidia-settings. Trying to play video in VLC is a good way to provoke the crash. Reverting back to nvidia-340.32-1 and linux-3.16.2-1 restores the previous behaviour (~40% VRAM used when running productivity applications).

Tested with Enlightenment and awesome, nvidia-settings reports identical VRAM use and Xorg crashes when trying to watch video (SD or HD) with VLC.

Additional info:
awesome 3.5.5-1
enlightenment 0.19.0-1
linux 3.17.1-1
linux-firmware 20141009.0e5f637-1
linux-headers 3.17.1-1
nvidia-340xx 340.46-4
nvidia-340xx-libgl 340.46-3
nvidia-340xx-utils 340.46-3
slim 1.3.6-5
vlc 2.1.5-4
xorg-server 1.16.1-1
xorg-server-common 1.16.1-1


Steps to reproduce:
1. Start X (using slim or startx)
2. Play video with VLC
3. Wait

Expected behaviour:
1. Start X
2. Play video with VLC
3. System is stable
This task depends upon

Closed by  Laurent Carlier (lordheavy)
Sunday, 14 December 2014, 17:58 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed upstream
Comment by Doug Newgard (Scimmia) - Saturday, 01 November 2014, 03:27 GMT
This sounds like an upstream bug, I don't see how it could be a packaging problem. You should report it to them.
Comment by kogepathic (yoj2ce) - Saturday, 01 November 2014, 09:08 GMT
Sorry, this is my first Arch bug and I'm not entirely sure how the process works.

I've also filed an upstream bug with nvidia over this issue. Hopefully they can get it fixed.

https://devtalk.nvidia.com/default/topic/786024/linux/340-46-4-memory-leak/
Comment by Sven-Hendrik Haase (Svenstaro) - Thursday, 20 November 2014, 16:57 GMT
Is this still a problem now?
Comment by kogepathic (yoj2ce) - Sunday, 14 December 2014, 15:07 GMT
It appears to be fixed in the most recent driver release.

Loading...