Bug 29750 - handle_dev_destroy_primary_surface: ASSERT !worker->surfaces[surface_id].context.canvas
Summary: handle_dev_destroy_primary_surface: ASSERT !worker->surfaces[surface_id].cont...
Status: RESOLVED MOVED
Alias: None
Product: Spice
Classification: Unclassified
Component: server (show other bugs)
Version: unspecified
Hardware: Other All
: medium major
Assignee: Spice Bug List
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-23 02:26 UTC by Yonit Halperin
Modified: 2018-06-03 10:14 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
qemu output (27.60 KB, text/plain)
2015-07-17 16:03 UTC, Pavel Grunt 		Details
View All

Description Yonit Halperin 2010-08-23 02:26:57 UTC 
It looks like the bug is in red_worker::destroy_surface_wait. 
destroy_surface_wait, doesn't really assure that all the references to the surface were destroyed. Specifically, if there are drawables that depends on this surface in the pipe, they stay in the pipe, and also all other drawables that belong to this surface and precede them; see red_worker::red_clear_surface_drawables_from_pipe.
The same bug can also occur in handle_dev_destroy_surfaces

We need to wait till the last item in the pipe that depends on the surface is sent.
Comment 1 Alexander Larsson 2010-09-22 03:12:47 UTC 
This was commited as 27f18287e899ff90fc0ee5ab697a8697d85953b2
Comment 2 Pavel Grunt 2015-07-17 16:00:23 UTC 
I just got this assert failure with the upstream Spice server (071647780dbda4fabf31e6b09940c14b62313913)

I wasn't doing anything special, just started qemu, connect using remote-viewer in fullscreen with 2 monitors.
Guest: RHEL6.7
Comment 3 Pavel Grunt 2015-07-17 16:03:03 UTC 
Created attachment 117201 [details]
qemu output

I will try reproduce and get better backtrace
Comment 4 GitLab Migration User 2018-06-03 10:14:45 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-server/issues/7.

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.