Bug 22964 - double free for r600 context
Summary: double free for r600 context
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/R100 (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-27 06:54 UTC by Radu Benea
Modified: 2009-09-01 09:32 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
valgrind log file for double context free in r600 (RV730XT) (41.53 KB, text/plain)
2009-07-27 06:54 UTC, Radu Benea
Details
the sources for the qt demo (13.52 KB, application/octet-stream)
2009-07-27 06:56 UTC, Radu Benea
Details
Protect agains double free patch (879 bytes, patch)
2009-07-27 07:18 UTC, Pauli
Details | Splinter Review

Description Radu Benea 2009-07-27 06:54:06 UTC
Created attachment 28035 [details]
valgrind log file for double context free in r600 (RV730XT)

I ran qt4/examples/opengl/textures/textures (demo present in Qt4 - my version is 4.5.2) which uses 6 gl windows and upon closing the application I got a double-free exception.
What's more interesting about it is that the window has 6 context but the first 2 work correctly, but if you use any of the other 4 the application will do a double free.
Comment 1 Radu Benea 2009-07-27 06:56:38 UTC
Created attachment 28036 [details]
the sources for the qt demo
Comment 2 Pauli 2009-07-27 07:18:00 UTC
Created attachment 28037 [details] [review]
Protect agains double free patch

This work around protects against double free but I don't think it is correct fix to the bug.
Comment 3 Alex Deucher 2009-08-23 13:42:35 UTC
Is this still an issue with current mesa git?
Comment 4 Adam Jackson 2009-08-24 12:33:00 UTC
Mass version move, cvs -> git
Comment 5 Radu Benea 2009-08-24 13:38:07 UTC
this no longer happens with current git master

if this has been properly fixed (not with the patch in here) please close the bug


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.