Here is the glib allocation code:
gpointer
g_malloc (gsize n_bytes)
{
if (G_UNLIKELY (!g_mem_initialized))
g_mem_init_nomessage();
if (G_LIKELY (n_bytes))
{
gpointer mem;
mem = glib_mem_vtable.malloc (n_bytes);
if (mem)
return mem;
g_error ("%s: failed to allocate %"G_GSIZE_FORMAT" bytes",
G_STRLOC, n_bytes);
}
return NULL;
}
Basically, what happened was that the glib_mem_vtable.malloc() freaked
out about the huge size requested and as a response it returned NULL.
This in turn caused the program to call g_error() which printed the
error.
Re-running this scenario under gdb with a breakpoint on g_error and then
obtaining a backtrace would probably be interesting because the bug is
almost certainly in the calling code (possibly in totem). However, if
the reporter does not have a specific set of steps that can reproduce
this bug then further analysis is not possible. This bug should not be
re-opened unless a consistent repro is found.
--
totem tries to allocate 4GB
https://bugs.launchpad.net/bugs/237401
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in ubuntu.
--
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
