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#43174 - [mesa-dri] Memory leak in i965 on glClear

Attached to Project: Arch Linux
Opened by Roland Ruckerbauer (ruabmbua) - Saturday, 20 December 2014, 16:36 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 11 February 2015, 21:38 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Jan de Groot (JGC)
Andreas Radke (AndyRTR)
Laurent Carlier (lordheavy)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
The library /usr/lib/xorg/modules/dri/i965_dri.so leaks heap memory.

Additional info:
* mesa-dri 10.3.5-1
* valgrind log:
==7962== Memcheck, a memory error detector
==7962== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==7962== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==7962== Command: ./test
==7962==
==7962==
==7962== HEAP SUMMARY:
==7962== in use at exit: 39,805 bytes in 429 blocks
==7962== total heap usage: 43,373 allocs, 42,944 frees, 110,298,432 bytes allocated
==7962==
==7962== 126 bytes in 8 blocks are definitely lost in loss record 48 of 74
==7962== at 0x4C29F90: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==7962== by 0x63EA859: strdup (in /usr/lib/libc-2.20.so)
==7962== by 0xC1E828A: ??? (in /usr/lib/xorg/modules/dri/i965_dri.so)
==7962== by 0xC1EA42E: ??? (in /usr/lib/xorg/modules/dri/i965_dri.so)
==7962== by 0xC1F3E7B: ??? (in /usr/lib/xorg/modules/dri/i965_dri.so)
==7962== by 0xC08CF5E: ??? (in /usr/lib/xorg/modules/dri/i965_dri.so)
==7962== by 0xC177162: ??? (in /usr/lib/xorg/modules/dri/i965_dri.so)
==7962== by 0xC2C7425: ??? (in /usr/lib/xorg/modules/dri/i965_dri.so)
==7962== by 0xC2C7EBB: ??? (in /usr/lib/xorg/modules/dri/i965_dri.so)
==7962== by 0xC2825A7: ??? (in /usr/lib/xorg/modules/dri/i965_dri.so)
==7962== by 0x401918: main (in /home/roland/Entwicklung/test/build/release/test)
==7962==
==7962== LEAK SUMMARY:
==7962== definitely lost: 126 bytes in 8 blocks
==7962== indirectly lost: 0 bytes in 0 blocks
==7962== possibly lost: 0 bytes in 0 blocks
==7962== still reachable: 39,679 bytes in 421 blocks
==7962== suppressed: 0 bytes in 0 blocks
==7962== Reachable blocks (those to which a pointer was found) are not shown.
==7962== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==7962==
==7962== For counts of detected and suppressed errors, rerun with: -v
==7962== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 2 from 1)


Steps to reproduce:
Run an OpenGL application inside valgrind, which makes use of glClear. The function call will produce a memory leak inside the i965 shared library.
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 11 February 2015, 21:38 GMT
Reason for closing:  Fixed
Comment by Doug Newgard (Scimmia) - Saturday, 20 December 2014, 16:45 GMT
Please include versions when reporting bugs. I'm guessing we're talking about mesa 10.3.5? Is it fixed in 10.4.0? If not, you might want to report this upstream as it's not a packaging bug.

Oops, sorry, I missed where you did include the version number. As I said, see if it's still present in 10.4.0.
Comment by Roland Ruckerbauer (ruabmbua) - Saturday, 20 December 2014, 17:12 GMT
Sorry, I can not upgrade to the new mesa, because of another bug in it. I am using a laptop with muxless switchable graphics, which causes problems on many upgrades of video driver, xorg and mesa packages. I currently trying, to get it up and running with the new OpenGL implementation in testing.

Without breaking my whole system...
Comment by Roland Ruckerbauer (ruabmbua) - Saturday, 20 December 2014, 18:09 GMT
You can mark the issue as resolved. I successfully tried it with the new mesa in testing. Although now my other graphics card causes a similar problem now. I will inspect it and open another bug report.

Loading...