[Tickets #2315] Uploading attachment uses too much memory

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=2315
-----------------------------------------------------------------------
 Ticket             | 2315
 Updated By         | nomis80 at lqt.ca
 Summary            | Uploading attachment uses too much memory
 Queue              | IMP
 Version            | 4.0.3
 State              | Unconfirmed
 Priority           | 2. Medium
 Type               | Bug
 Owners             | 
-----------------------------------------------------------------------


nomis80 at lqt.ca (2005-07-26 10:24) wrote:

> are you using mySQL to store 
> your attachments?

Yes.

> If so, you have not searched either the bug index 
> or the mailing list

I don't understand your reasoning. I do store my attachments in MySQL, and I
did search the mailing list and the bug index.

> where the issue has been addressed numerous times.

Have you heard of URLs? They're very useful for *locating* stuff, you know.
Maybe you could give one to me, that would be helpful.

> Or have you run test.php, like docs/INSTALL tells you to, and it 
> clearly states that memory_limit should be DISABLED.

Hahaha, sure. Please, try to understand the problem. I want to send a 10M
attachment, and IMP is already eating 320M and the disk is trashing to swap.
You really think removing the limit would make IMP not consume that much
memory? The problem is not that the limit is too low, it's that IMP uses
*too much memory*.

> As for PHP usage, we can try to do as much as possible to free 
> memory, but we are limited as to how PHP allocates memory.  So if you 
> are having major issues with PHP's memory usage, you need to bug the 
> PHP folks.

Yeah, sure, it's a bug in PHP. And maybe you'll be interested in hearing
about the memory leak in malloc() that I found this morning. And I've found
a security flaw in "rm" the other day.

IMP really does eat too much memory when sending attachments, and maybe if
you had replied something like "could not reproduce" then I would have
believed you more than you simply dismissing my bug report because you're
too narrow minded to believe that there could be a tiny chance that I really
did witness that bug, spent countless hours measuring, tweaking, profiling
and generally hacking, searched the documentation, mailing list archives,
bug index, and finally, out of desperation, resigned to file a bug.