Logged In: YES 
user_id=31435

sin_avatar, it's the number of integer objects _simultaneously 
alive_ that matters, not the total number of integer objects 
ever created.  Creating a list (or any other in-memory 
container) containing millions of integers can be a bad idea 
on many counts.

I'm closing this as WontFix, as there are no plans to replace 
the integer freelist.  I think it would be good if an upper bound 
were placed on its size (as most other internal freelists have), 
but that's trickier than it sounds and there are no plans to do 
that either.

> I can't udestood why you don't care about this?

It's a tradeoff:  it's much easier to avoid in real life than it is to 
change the implementation in a way that would actually help 
(the int freelist is an important speed optimization for most 
integer-heavy apps).  Changing your coding practices to live 
with this is your only realistic hope for relief.

BTW, the idea that you might really need to create a list with 
10 million integers in each thread of a threaded server is too 
bizarre to argue about ;-)