Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Bug 1086823

Summary:	qemu sometimes crashes in spice-server with "rate_control->num_recent_enc_frames" assertion
Product:	Red Hat Enterprise Linux 7	Reporter:	David Jaša <djasa>
Component:	spice	Assignee:	Default Assignee for SPICE Bugs <rh-spice-bugs>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	cfergeau, dblechte, marcandre.lureau, mkenneth, mkrcmari, rbalakri
Target Milestone:	beta
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	spice-0.12.4-7.el7	Doc Type:	Bug Fix
Doc Text:	Under certain conditions, when SPICE streaming code triggers, a "mjpeg_encoder.c:627:mjpeg_encoder_adjust_params_to_bit_rate: assertion `rate_control->num_recent_enc_frames' failed" assertion would be raised. This issue is fixed by properly handling this case in the streaming code.	Story Points:	---
Clone Of:	1086820	Environment:
Last Closed:	2015-03-05 07:56:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1086820
Bug Blocks:

Description David Jaša 2014-04-11 15:13:19 UTC

This bug is likely to be in .el7 spice-server as well so let's track it with a separate bz. Technical discussion should be in parent bug.

+++ This bug was initially created as a clone of Bug #1086820 +++

Description of problem:
Sometimes, qemu process crashes with failed assertion: "rate_control->num_recent_enc_frames". The issue was also reported upstream in this ML thread:
http://lists.freedesktop.org/archives/spice-devel/2014-February/thread.html#16030

Version-Release number of selected component (if applicable):
spice-server-0.12.4-6.el6_5.1.x86_64
guest:
  * in my case: RHEL 6.5
  * upstream report: Windows 7 when working in Outlook

How reproducible:
random

Steps to Reproduce:
1. use of guest over wan could make bug more likely to occur
2.
3.

Actual results:
qemu crashes

Expected results:
no crash occurs

Additional info:

Comment 1 Marc-Andre Lureau 2014-07-01 22:03:29 UTC

original bug has solution, moving to POST

Comment 6 errata-xmlrpc 2015-03-05 07:56:23 UTC

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.

https://rhn.redhat.com/errata/RHBA-2015-0335.html