RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 586315 [details]
Backtrace from qemu-kvm when doing multiple resolution changes

Description of problem:
When doing resolution changes in a loop on guest, qemu-kvm process crashes with sigabrt, Sometimes I need to wait for longer time, sometimes It occurs after several resolution changes.
Following ASSERT os raised:
dev_destroy_surfaces: ASSERT !worker->surfaces[i].context.canvas failed

I am attaching bt from qemu-kvm process

Version-Release number of selected component (if applicable):
spice-server-0.10.1-10.el6.x86_64
qemu-kvm-0.12.1.2-2.292.el6.x86_64
spice-gtk-0.11-10.el6.x86_
WindowsXP guest with qxl driver with off-screen surfaces support installed 


How reproducible:
100% (If you try long enough)

Steps to Reproduce:
1. Connect to a Windows guest with qxl driver installed.
2. Run resolution changes in loop
  
Actual results:
sigabrt is catch on qemu-kvm process.

Expected results:
Smooth resolution changes.

Additional info:

This is
spice_assert(ring->next != NULL && ring->prev != NULL);
triggering in spice-server/common/ring.h

How do you do these resolution changes in a loop? Manually or do you have a tool to do that?

(In reply to comment #1)
> This is
> spice_assert(ring->next != NULL && ring->prev != NULL);
> triggering in spice-server/common/ring.h
> 
> How do you do these resolution changes in a loop? Manually or do you have a
> tool to do that?

I am running the script from bug #578845.

Created attachment 586577 [details]
fix patch 1

Created attachment 586578 [details]
proposed fix patch 2

The bug can occur when the primary surface or all the surfaces are destroyed (e.g., resolution changes, reset, switching users).

RHEL6.4 QA ACK

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-0529.html

*** Bug 863495 has been marked as a duplicate of this bug. ***