After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 273964 - Crash when switching to calendar
Crash when switching to calendar
Status: VERIFIED FIXED
Product: evolution
Classification: Applications
Component: Calendar
2.2.x (obsolete)
Other All
: Normal blocker
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-03-22 14:47 UTC by Tommi Komulainen
Modified: 2013-09-10 14:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
stack trace (92.44 KB, text/plain)
2005-03-22 14:48 UTC, Tommi Komulainen
Details

Description Tommi Komulainen 2005-03-22 14:47:47 UTC
Switching to calendar view simply crashes with the following error message
printed in the console:

GThread-ERROR **: file gthread-posix.c: line 351 (): error 'Cannot allocate
memory' during 'pthread_create'

Using the exchange connector.  Earlier the calendar worked fine, then all
of the sudden it just started crashing.  The first crash occurred right
after creating a new task, but since then any attempt to switch to calendar
crashes.

The stack trace indicates evolution ends up creating new threads in an
endless loop until around 256 threads it just crashes.
Comment 1 Tommi Komulainen 2005-03-22 14:48:14 UTC
Created attachment 45009 [details]
stack trace
Comment 2 Tommi Komulainen 2005-03-22 14:51:15 UTC
After removing calendar and tasks cache.ics the crash goes away (until
the next time...)
Comment 3 Chenthill P 2005-03-24 08:15:44 UTC
Can you provide your cache.ics file if possible.
Comment 4 JP Rosevear 2005-03-29 06:34:53 UTC
What distro/kernel is this?
Comment 5 Tommi Komulainen 2005-03-29 08:55:42 UTC
Unfortunately I can't provide the cache.  This is RH9 (derivative)
with 2.4.20-33.9 kernel.
Comment 6 Rodrigo Moya 2005-04-07 19:26:36 UTC
Fixed in CVS
Comment 7 Poornima 2005-08-09 05:47:56 UTC
This bug is not reproducible in evolution 2.3.x, hence changing state of the bug
to 'verified. Reporter can reopen the bug if this bug is reproducible in his
setup with evolution 2.3.x client.