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.

Description of problem:
remote-viewer crash because could not allocate memory for big amount of data.

Version-Release number of selected component (if applicable):
virt-viewer 0.5.6-8
spice=gtk 0.20-9
spice-vdagent 0.14.0-2


Steps to Reproduce:
1.Connect to guest by remote-viewer from client
2.Open text file in client VM and copy whole text (more than 100Mb) into clipboard
3.Open text editor in guest VM and paste text from clipboard

Actual results:
remote-viewer crashes

Expected results:
remote-viewer does not crash

Additional info:

gdb:
GLib-ERROR **: gmem.c:170: failed to allocate 155676817 bytes
aborting...
Program received signal SIGABRT, Aborted.


(gdb) backtrace
#0  0x0000003a81e32925 in raise (sig=6)
   at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
Cannot access memory at address 0x7fffffffcad8


guest: Win7 64
client: Rhel6.5 64
host: RHEL 6.5 64

See also bug 1017250

in general, crash on OOM is the expected behaviour, and it's fine for the client.

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

following dep bug status

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-2014-1487.html