Bug 845345 - GLib-ERROR **: gmem.c:165: failed to allocate 210453397505 bytes
GLib-ERROR **: gmem.c:165: failed to allocate 210453397505 bytes
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: gobject-introspection (Show other bugs)
17
ppc64 Linux
urgent Severity urgent
: ---
: ---
Assigned To: Colin Walters
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-08-02 14:30 EDT by Mark Hamzy
Modified: 2013-02-07 09:31 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-02-07 09:31:42 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Mark Hamzy 2012-08-02 14:30:23 EDT
I am running the newui branch of the anaconda installer on a Fedora 17 DVD and am seeing the following:

Program received signal SIGTRAP, Trace/breakpoint trap.
0x00000fff893676d4 in .raise () from /lib64/libpthread.so.0
(gdb) bt
#0  0x00000fffb45676d4 in .raise () from /lib64/libpthread.so.0
#1  0x00000fffb2a01ec8 in g_logv (log_domain=0xfffb2a7df48 "GLib",
    log_level=G_LOG_LEVEL_ERROR,
    format=0xfffb2a866a0 "%s: failed to allocate %lu bytes",
    args1=0xffffa284e48 "") at gmessages.c:758
#2  0x00000fffb2a020b0 in g_log (
    log_domain=<error reading variable: value has been optimized out>,
    log_level=<error reading variable: value has been optimized out>,
    format=<error reading variable: value has been optimized out>)
    at gmessages.c:792
#3  0x00000fffb29ffec4 in g_malloc (n_bytes=210453397505) at gmem.c:164
#4  0x00000fffb2a1fbfc in g_strndup (
    str=0x10019768110 "GtkViewport { background-color: @theme_bg_color }", '3' <repeats 15 times>"\360, ",
    n=<error reading variable: value has been optimized out>)
    at gstrfuncs.c:420
#5  0x00000fffad97b360 in gtk_css_provider_load_from_data (
    css_provider=0x1001944f100,
    data=0x10019768110 "GtkViewport { background-color: @theme_bg_color }", '3' <repeats 15 times>"\360, ", length=210453397504, error=0xffffa285220)
    at gtkcssprovider.c:2492
#6  0x00000fffb21f795c in ?? () from /lib64/libffi.so.5
#7  0x00000fffb21f704c in .ffi_call () from /lib64/libffi.so.5
---Type <return> to continue, or q <return> to quit---
#8  0x00000fffafe725fc in g_callable_info_invoke (info=0x100196f3a80,
    function=0xfffade0a538, in_args=0x10019728900, n_in_args=<optimized out>,
    out_args=0x0, n_out_args=<optimized out>, return_value=0xffffa285488,
    is_method=<optimized out>, throws=32, error=0xffffa285440)
    at girepository/gicallableinfo.c:610
#9  0x00000fffafe74650 in g_function_info_invoke (info=0x100196f3a80,
    in_args=0x10019728900, n_in_args=<optimized out>, out_args=0x0,
    n_out_args=<optimized out>, return_value=0xffffa285488,
    error=0xffffa285440) at girepository/gifunctioninfo.c:274
#10 0x00000fffb300a2dc in _invoke_callable (callable_info=0x100196f3a80,
    cache=0x10019794240, state=0xffffa285448) at pygi-invoke.c:52
#11 _wrap_g_callable_info_invoke (self=0xfffa9716c20, py_args=<optimized out>,
    kwargs=<optimized out>) at pygi-invoke.c:633
#12 0x00000fffb466006c in .PyCFunction_Call () from /lib64/libpython2.7.so.1.0

The corresponding anaconda function that causes this is:

./pyanaconda/ui/gui/utils.py:
def setViewportBackground(vp, color="@theme_bg_color"):
Comment 1 Mark Hamzy 2012-08-02 14:35:07 EDT
That should be:

def setViewportBackground(vp, color="@theme_bg_color"):
    """Set the background color of the GtkViewport vp to be the same as the
       overall UI background.  This should not be called for every viewport,
       as that will affect things like TreeViews as well.
    """

    provider = Gtk.CssProvider()
    provider.load_from_data("GtkViewport { background-color: %s }" % color)
    context = vp.get_style_context()
    context.add_provider(provider, Gtk.STYLE_PROVIDER_PRIORITY_APPLICATION)
Comment 2 Phil Knirsch 2013-02-07 09:31:42 EST
Closing as this wasn't an issue with Fedora 18 anymore.

Thanks & regards, Phil

Note You need to log in before you can comment on or make changes to this bug.