On Mon, 2012-09-24 at 09:31 +0200, David Henningsson wrote:
> On 09/23/2012 12:19 PM, Tanu Kaskinen wrote:
> > On Thu, 2012-04-19 at 10:54 +0200, David Henningsson wrote:
> >> Nowadays, we are using more hashmaps and other things, than we did
> >> before. Therefore, I often get the "flist is full (
On 09/23/2012 12:19 PM, Tanu Kaskinen wrote:
On Thu, 2012-04-19 at 10:54 +0200, David Henningsson wrote:
Nowadays, we are using more hashmaps and other things, than we did
before. Therefore, I often get the "flist is full (don't worry)"
message. This change should avoid that message. I was unabl
On Thu, 2012-04-19 at 10:54 +0200, David Henningsson wrote:
> Nowadays, we are using more hashmaps and other things, than we did
> before. Therefore, I often get the "flist is full (don't worry)"
> message. This change should avoid that message. I was unable to find
> any significance in increase o
On 04/19/2012 11:45 AM, Dalleau, Frederic wrote:
Hi David,
On Thu, Apr 19, 2012 at 10:54 AM, David Henningsson
wrote:
Nowadays, we are using more hashmaps and other things, than we did
before. Therefore, I often get the "flist is full (don't worry)"
message. This change should avoid that mess
Hi David,
On Thu, Apr 19, 2012 at 10:54 AM, David Henningsson
wrote:
> Nowadays, we are using more hashmaps and other things, than we did
> before. Therefore, I often get the "flist is full (don't worry)"
> message. This change should avoid that message. I was unable to find
> any significance in
Nowadays, we are using more hashmaps and other things, than we did
before. Therefore, I often get the "flist is full (don't worry)"
message. This change should avoid that message. I was unable to find
any significance in increase of memory footprint from this change.
Signed-off-by: David Henningss