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.
Created attachment 717460[details]
Backtrace
Description of problem:
Connected remote-viewer to qemu-kvm instance, qemu-kvm core dumped after clicking 'X' button.
Version-Release number of selected component (if applicable):
qemu-kvm-1.4.0-1.el7.x86_64
3.9.0-0.rc3.44.el7.x86_64
glibc-2.16-29.el7.x86_64
How reproducible:
Only once so far.
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Logs will be attached.
hit again while connecting qemu-kvm through remote-viewer, closing it then reconnecting through vncviewer
#0 0x00007f8f9610d1db in _int_malloc () from /lib64/libc.so.6
#1 0x00007f8f9610f443 in malloc () from /lib64/libc.so.6
#2 0x00007f8f9b7da6f9 in realloc_and_trace (mem=0x0, n_bytes=3428) at vl.c:2740
#3 0x00007f8f9acc8737 in g_realloc () from /lib64/libglib-2.0.so.0
#4 0x00007f8f9b7d3e54 in buffer_reserve (buffer=0x7f8f8d305540, len=<optimized out>) at ui/vnc.c:475
#5 0x00007f8f9b7d5783 in vnc_write (vs=0x7f8f8d2f9480, data=0x7f8f9def4310, len=2404) at ui/vnc.c:1365
#6 0x00007f8f9b7d49c9 in vnc_raw_send_framebuffer_update (vs=vs@entry=0x7f8f8d2f9480, x=x@entry=0, y=y@entry=0, w=w@entry=601, h=h@entry=27)
at ui/vnc.c:686
#7 0x00007f8f9b7c723d in send_sub_rect_solid (h=27, w=601, y=0, x=0, vs=0x7f8f8d2f9480) at ui/vnc-enc-tight.c:1511
#8 find_large_solid_color_rect (max_rows=51, h=960, w=1280, y=0, x=0, vs=0x7f8f8d2f9480) at ui/vnc-enc-tight.c:1607
#9 tight_send_framebuffer_update (vs=0x7f8f8d2f9480, x=0, y=0, w=1280, h=960) at ui/vnc-enc-tight.c:1660
#10 0x00007f8f9b7d0960 in vnc_worker_thread_loop (queue=queue@entry=0x7f8f9def3460) at ui/vnc-jobs.c:259
#11 0x00007f8f9b7d0b30 in vnc_worker_thread (arg=0x7f8f9def3460) at ui/vnc-jobs.c:319
#12 0x00007f8f99a52d15 in start_thread () from /lib64/libpthread.so.0
#13 0x00007f8f9618246d in clone () from /lib64/libc.so.6
Created attachment 717460 [details] Backtrace Description of problem: Connected remote-viewer to qemu-kvm instance, qemu-kvm core dumped after clicking 'X' button. Version-Release number of selected component (if applicable): qemu-kvm-1.4.0-1.el7.x86_64 3.9.0-0.rc3.44.el7.x86_64 glibc-2.16-29.el7.x86_64 How reproducible: Only once so far. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Logs will be attached.