This is what happens if you try to open a truly large E-mail on a device
that has not as much memory available:
Is there something we can do about this? Can we change the MIME parsing
algorithm to be less memory demanding for example?
Note that GArray is not really very sparse with memory once y
Hi there,
The imap_rescan function of the default IMAP provider of Evolution will
in case at the front of the IMAP Mailbox items got expunged, more or
less start marking all of the locally cached summary info as invalid.
(note. summary in this context means the envelope information of each
item t
On Sat, 2008-01-26 at 13:44 +0100, Philip Van Hoof wrote:
> This is what happens if you try to open a truly large E-mail on a device
> that has not as much memory available:
>
> Is there something we can do about this? Can we change the MIME parsing
> algorithm to be less memory demanding for exam
On Sat, 2008-01-26 at 22:12 -0500, Jeffrey Stedfast wrote:
> On Sat, 2008-01-26 at 13:44 +0100, Philip Van Hoof wrote:
> > This is what happens if you try to open a truly large E-mail on a device
> > that has not as much memory available:
> >
> > Is there something we can do about this? Can we cha
Something like the attached patch might work, tho it is untested.
If this doesn't work, then I suspect the problem is that the seek
position might get changed out from under the mime parser (assuming it
is using either a CamelStreamFs or an fd).
Note that camel_stream_fs_new_with_fd[_and_bounds](