[Bug 104887] [Version 18.1] Memory leak when frequently create shaders on ubuntu/Linux

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=104887

            Bug ID: 104887
           Summary: [Version 18.1] Memory leak when frequently create
                    shaders on ubuntu/Linux
           Product: Mesa
           Version: git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: critical
          Priority: medium
         Component: Drivers/DRI/i965
          Assignee: intel-3d-bugs at lists.freedesktop.org
          Reporter: 94389147 at qq.com
        QA Contact: intel-3d-bugs at lists.freedesktop.org

Created attachment 137091
  --> https://bugs.freedesktop.org/attachment.cgi?id=137091&action=edit
including opengl_demo.zip valgrind.result glxinfo.txt

Hi all,
   I ran a test program in ubuntu 16.04, mesa 18.1. Please see attached
glxinfo.txt for system information and opengl_demo.zip for test program.

   The test program use create simple shader 10 times. Using valgrind as
following 'valgrind --tool=memcheck --leak-check=yes --show-reachable=yes
--num-callers=20 --track-fds=yes ./es2tri', it easy to get a memory leak report
as in attachement.

==24757== LEAK SUMMARY:
==24757==    definitely lost: 144 bytes in 2 blocks
==24757==    indirectly lost: 8,000 bytes in 40 blocks
==24757==      possibly lost: 1,460,261 bytes in 4,429 blocks
==24757==    still reachable: 165,485 bytes in 115 blocks
==24757==         suppressed: 0 bytes in 0 blocks

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20180131/d3279e5c/attachment.html>