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 1609853 - out of memory for drawing widgets on top bar and also some document pages
Summary: out of memory for drawing widgets on top bar and also some document pages
Keywords:
Status: CLOSED DUPLICATE of bug 1378961
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: evince
Version: 7.6
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Marek Kašík
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-30 15:57 UTC by Tomas Hudziec
Modified: 2018-07-30 16:36 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-30 16:36:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Tomas Hudziec 2018-07-30 15:57:12 UTC 
Description of problem:
Some pages of document and top bar of evince window are not rendered correctly after fast scrolling in sample pdf file.

Version-Release number of selected component (if applicable):
evince-3.28.2-5.el7.x86_64

How reproducible:
always with sample pdf file

Steps to Reproduce:
1. run evince from command line
2. open sample pdf file in evince
3. scroll fast through document up & down with side scroll bar
4. stop on some not rendered page (only shadow space of it)
5. resize program window

Actual results:
Top bar of evince window becomes black.
Following Gtk-WARNINGs are printed in terminal:
(evince:18493): Gtk-WARNING **: 17:10:24.046: drawing failure for widget 'GtkOverlay': out of memory
(evince:18493): Gtk-WARNING **: 17:10:24.046: drawing failure for widget 'GtkBox': out of memory
(evince:18493): Gtk-WARNING **: 17:10:24.046: drawing failure for widget 'GtkPaned': out of memory
(evince:18493): Gtk-WARNING **: 17:10:24.046: drawing failure for widget 'GtkBox': out of memory
(evince:18493): Gtk-WARNING **: 17:10:24.046: drawing failure for widget 'EvWindow': out of memory
(evince:18493): Gtk-WARNING **: 17:10:24.112: drawing failure for widget 'EvView': out of memory
(evince:18493): Gtk-WARNING **: 17:10:24.113: drawing failure for widget 'GtkScrolledWindow': out of memory

Expected results:
No Gtk-WARNINGs in terminal, correct rendering of top bar and document pages.

Additional info:
sample pdf file for testing is Red_Hat_Enterprise_Linux-7-System_Administrators_Guide-en-US.pdf: 600 pages, ~6MB
Comment 3 Marek Kašík 2018-07-30 16:36:16 UTC 
Hi,

this is a duplicate of the bug #1378961. Once I apply the patch locally the issue disappears.

*** This bug has been marked as a duplicate of bug 1378961 ***
Note You need to log in before you can comment on or make changes to this bug.