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 659996 - "Too many open files" error when reading mail
"Too many open files" error when reading mail
Status: RESOLVED DUPLICATE of bug 655272
Product: evolution
Classification: Applications
Component: Mailer
3.0.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-09-24 09:51 UTC by Milan Bouchet-Valat
Modified: 2011-09-25 06:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.91/3.0

Attachments
Output of valgrind --trace-fds=yes for ~30 min (105.44 KB, text/plain)
2011-09-24 09:51 UTC, Milan Bouchet-Valat 		Details

Description Milan Bouchet-Valat 2011-09-24 09:51:51 UTC 
Created attachment 197389 [details]
Output of valgrind --trace-fds=yes for ~30 min

From time to time, I'm getting this error, with loads of lines like that in .xsession-errors:
(evolution:12296): camel-WARNING **: Could not save object state file to '/home/milan/.local/share/evolution/mail/imapx/nalimilan@club.fr@imap.sfr.fr/system/.#Trash.cmeta': Too many open files

When closing Evo, it eventually crashes, probably due to this warning (I can't get a trace at the moment because my yum install is broken and I lack debugging symbols):
GLib-ERROR **: Cannot create pipe main loop wake-up: Too many open files
aborting...


There are many reports of this problem in old versions of Evolution (2.6...) on the Web, some of which were fixed. For example, bug 350907 fixed a few fd leaks. I'm attaching the output of valgrind --trace-fds after about 30 minutes running, reading a few mails, changing IMAP folders, and suspending/resuming. I don't know if it contains useful information (and it lacks a few symbols), so please ask if you need more.
Comment 1 Akhil Laddha 2011-09-25 06:13:37 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 655272 ***