Bug 26461 - blender creates massive GEM object leak
Summary: blender creates massive GEM object leak
Status: RESOLVED DUPLICATE of bug 24119
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Eric Anholt
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-06 15:57 UTC by Jan Alexander Steffens (heftig)
Modified: 2010-03-12 17:14 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Jan Alexander Steffens (heftig) 2010-02-06 15:57:51 UTC
Rotating or scaling the default cube (not the view) in blender causes a leak of gem objects. It accumulates multiple gigabytes within seconds, as reported by /sys/kernel/debug/dri/0/gem_objects. The system begins to thrash when RAM is full. The objects are released when blender is closed.

System:
Thinkpad X61t (GM965)
Arch Linux x86_64
xorg-server 1.7.4.901-1
KMS,UXA

Tested configurations:
Kernel 2.6.32.7-1
mesa 7.7-1
xf86-video-intel 2.9.1-1

and

Kernel 2.6.33-rc6-zen from git (2010-02-05)
xf86-video-intel from git (2010-02-06)
mesa from git (2010-02-06)

Leak happens using both.

Leaks:
blender 2.49a-1 from Arch
blender-2.49b-linux-glibc236-py26-x86_64
blender-2.40-linux-glibc2.3.2-x86_64-py24-static
blender-publisher-2.25-linux-glibc2.1.2-i386 (test caused the object bytes counter to overflow into negativity)

Does not leak:
blender-2.5-alpha0-linux-glibc27-x86_64
blender-2.49b-linux-glibc236-py26-x86_64 using accompanying software libGL
Comment 1 Sven Arvidsson 2010-02-20 12:03:54 UTC
I can reproduce this, might be the same bug I reported in bug #24119.
Comment 2 Eric Anholt 2010-03-12 17:14:40 UTC
I think this is going to be the same root cause (I see only one type of leak occurring I think), so I'll mark this as a dup of the other.


*** This bug has been marked as a duplicate of bug 24119 ***


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.