Bug 92354 - memory not been freed after high latency
Summary: memory not been freed after high latency
Status: RESOLVED MOVED
Alias: None
Product: Spice
Classification: Unclassified
Component: spice-gtk (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Victor Toso
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-09 10:34 UTC by Victor Toso
Modified: 2018-06-03 10:21 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
no latency (240.88 KB, text/plain)
2015-10-09 10:35 UTC, Victor Toso 		Details
200 ms (119.12 KB, text/plain)
2015-10-09 10:36 UTC, Victor Toso 		Details
1000 ms (191.10 KB, text/plain)
2015-10-09 10:36 UTC, Victor Toso 		Details
View All

Description Victor Toso 2015-10-09 10:34:54 UTC 
Related to https://bugzilla.redhat.com/show_bug.cgi?id=1264156

Test: sharing webcam and increasing latency.

Seems like another memory-pool without limit IMHO. Filing bug to look later on.

Massifs attached: without latency, with 200 ms latency and 1000 ms latency.
Comment 1 Victor Toso 2015-10-09 10:35:54 UTC 
Created attachment 118775 [details]
no latency
Comment 2 Victor Toso 2015-10-09 10:36:12 UTC 
Created attachment 118776 [details]
200 ms
Comment 3 Victor Toso 2015-10-09 10:36:30 UTC 
Created attachment 118777 [details]
1000 ms
Comment 4 Victor Toso 2015-10-09 10:38:41 UTC 
Note, even with a solution to rhbz#1264156 like the proposal in the mailing list [0] this seem to happen.

[0] http://lists.freedesktop.org/archives/spice-devel/2015-October/022159.html
Comment 5 GitLab Migration User 2018-06-03 10:21:33 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/spice/spice-gtk/issues/27.

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.