Bug 30265 - r600g: potential memory leak
Summary: r600g: potential memory leak
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/r600 (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-19 08:10 UTC by Nicolas Kaiser
Modified: 2010-10-01 04:34 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
(r600g) Output of valgrind --trace-children=yes --leak-check=full glxgears (143.69 KB, text/plain)
2010-09-19 08:10 UTC, Nicolas Kaiser 		Details
(r600c) Output of valgrind --trace-children=yes --leak-check=full glxgears (10.64 KB, text/plain)
2010-09-19 08:12 UTC, Nicolas Kaiser 		Details
View All

Description Nicolas Kaiser 2010-09-19 08:10:15 UTC 
Created attachment 38798 [details]
(r600g) Output of valgrind --trace-children=yes --leak-check=full glxgears

Shortly running glxgears in valgrind with r600g:

LEAK SUMMARY:
 definitely lost: 4,414,144 bytes in 236 blocks

With r600c, there's a lot less loss output.

System environment:
-- system architecture: amd64
-- Linux distribution: Gentoo
-- GPU: RS780G
-- Model: ATI Radeon HD 3200
-- Display connector: VGA
-- xf86-video-ati: b90cb61ccb0f4f80e0627141f223354a9371d47d
-- xserver: 1.9.0
-- mesa: e4513e7fb96c6336d8c7fcdadfaddb6b335a736e
-- drm: 7ec9a1effa4f551897f91f3b017723a8adf011d9
-- kernel: 2.6.36-rc4-00166-g151b6a5
Comment 1 Nicolas Kaiser 2010-09-19 08:12:42 UTC 
Created attachment 38799 [details]
(r600c) Output of valgrind --trace-children=yes --leak-check=full glxgears

For comparison purposes.
Comment 2 Nicolas Kaiser 2010-10-01 04:34:19 UTC 
Since mesa commit 7ee8fa0421fd3c6522120d8639c6b311674a9b10
(Jerome Glisse, "r600g: switch to new design"), there is no more
definitely lost memory detected with valgrind.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.