Bug 2431 - Major memory leak in PGP message handling
Summary: Major memory leak in PGP message handling
Status: RESOLVED FIXED
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: Other (show other bugs)
Version: 3.7.8
Hardware: PC Linux
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2011-05-19 05:09 UTC by th61
Modified: 2011-10-29 10:02 UTC (History)
0 users

See Also:


Attachments

Description th61 2011-05-19 05:09:54 UTC
Discovered on Claws Mail 3.7.8 on Ubuntu 11.04 x64 with GPG 1.4.11


There is a major memory leak somewhere in GPG message handling.

Each time a GPG encrypted message is selected in the folder view, immediately following the decryption, the memory allocated to Claws increases by roughly the size of the message, but does not release when the message is no longer selected, has not been selected in a while, or is more than n selections ago, despite CPU usage clearly indicating decryption and signature verification occurring each time a message is selected.

I first noticed this bug when I saw the claws-mail process consuming 1.8 GB RAM after a long day working with sizable encrypted attachments.

This bug can be easily reproduced by sending a sizable attachment to an account's inbox, then watching the memory and CPU response each time the message is repeatedly selected and deselected, to simulate the normal back and forth workflow. CPU time stays constant, suggesting on-the-fly (not cached) decryption, but the memory usage ratchets up without fail.
Comment 1 Colin Leroy 2011-08-31 19:35:31 UTC
Hi,

Is this with PGP/Mime or Inline ?
Comment 2 users 2011-08-31 20:40:34 UTC
Changes related to this bug have been committed.
Please check latest CVS and update the bug accordingly.
You can also get the patch from:
http://www.colino.net/claws-mail/

2011-08-31 [colin]	3.7.10cvs14

	* src/plugins/pgpinline/pgpinline.c
	* src/plugins/pgpmime/pgpmime.c
		Fix bug #2431, "Major memory leak in PGP message handling".

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