Bug 61280

Summary:	ps self-copy tests never stop allocating memory
Product:	cairo	Reporter:	Darxus <darxus>
Component:	general	Assignee:	Chris Wilson <chris>
Status:	RESOLVED FIXED	QA Contact:	cairo-bugs mailing list <cairo-bugs>
Severity:	normal
Priority:	medium
Version:	1.12.14
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Darxus 2013-02-22 13:56:40 UTC

15:08 < Darxus>   PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND
15:08 < Darxus>  7788 darxus    20   0 5957m 5.0g  480 D  12.3 64.3   0:55.70 lt-cairo-test-s
15:08 < ickle> ps self-copy
15:08 < Darxus> Yah, should it be taking 5.9gb ram?
15:08 < ickle> manages to circumvent our timers and limits
15:09 < Darxus> 7248m
15:09 < ickle> if you converted every quantum state in the universe and converted it to a bit, you would still not have enough
15:09 < Darxus> Eh?
15:10 < Darxus> 10.4g, out of 8gb physical.
15:11 < Darxus> So should I kill it?
15:11 < ickle> yes
15:12 < Darxus> 12.9g, killed.  So what's up with that?  Should it be disabled so it's safe to run make check?

Tests include:
self-copy-overlap.ps2.argb32 [0]:
self-copy-overlap.ps3.argb32 [0]:

I believe the commit I saw this with last night was 446a3dc5c0298e35b9a1e38460bc3804ab6e01ce but it's not very new.

Built with: ./autogen.sh --prefix=$installdir --enable-gl --enable-xcb

Can these at least be disabled so it's safe to run make check?

Cairo from git is reporting 1.12.15.  There doesn't appear to be an appropriate option the the Version field for this bug.

Comment 1 Uli Schlachter 2013-08-21 13:39:14 UTC

I think this was fixed already (at least I cannot reproduce it), but I cannot figure out which commit actually did that. Feel free to reopen if I am wrong.

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.