Bug 200071 - GLib-ERROR **: gmem.c:172: failed to allocate 1073741824 bytes
Summary: GLib-ERROR **: gmem.c:172: failed to allocate 1073741824 bytes
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 5
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2006-07-25 10:46 UTC by Need Real Name
Modified: 2007-11-30 22:11 UTC (History)
0 users

Clone Of:
Last Closed: 2006-09-03 13:40:21 UTC

Attachments (Terms of Use)
strace from bug buddy (6.90 KB, text/plain)
2006-07-26 11:25 UTC, Need Real Name
no flags Details

Description Need Real Name 2006-07-25 10:46:04 UTC
Evolution keeps crashing.

CAMEL_VERBOSE_DEBUG=1 tells me it's trying to allocate a gig of ram:
 GLib-ERROR **: gmem.c:172: failed to allocate 1073741824 bytes

Comment 1 Matthew Barnes 2006-07-25 10:55:47 UTC
This isn't nearly enough information to do anything about.

Please at least provide the version of Evolution you're using, steps to
reproduce, and if possible a backtrace at the point of failure.

Comment 2 Need Real Name 2006-07-25 13:23:18 UTC
I'm trying, but the stack trace is useless, even though I have debuginfo
packages installed.

Next time it happens, I'll post it.

Comment 3 Need Real Name 2006-07-26 11:23:21 UTC
I get a different crash now, let me know if you want a new bug:
 camel-exchange-provider-ERROR **: file camel-stub.c: line 463
(stub_send_internal): should not be reached

The error, and crash, is triggered when I view a particular message with an

Comment 4 Need Real Name 2006-07-26 11:25:44 UTC
Created attachment 133065 [details]
strace from bug buddy

Comment 5 Matthew Barnes 2006-07-26 12:28:31 UTC
Can you provide a sample mail message with attachment that reproduces the problem?

Comment 6 Need Real Name 2006-09-01 22:42:40 UTC
Not any more. The problem has disappeared.
btw why do I get two NEEDINFO requests instead of one?

Comment 7 Matthew Barnes 2006-09-03 13:40:21 UTC
Okay, I'll assume whatever problem you were seeing has been fixed and close this
bug.  Feel free to re-open it if you start getting the same crashes again.

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