> No, that was done with the DevStudio build. Note also this:
>
> Python 2.3a0 (#29, Oct 7 2002, 19:54:53) [MSC 32 bit (Intel)] on win32
> Type "help", "copyright", "credits" or "license" for more information.
>
> python_d mem usage : 2.340 K
>
> >>> b = {}
> [3319 refs]
> >>> for i in range(1000000):
> ... b[i] = [i] * 60
> ...
> [62003414 refs]
>
> python_d mem usage : 376.320 K
>
> >>> del b
> [3413 refs]
> >>>
>
> python_d mem usage : 351.716 K
>
> Again, with the devstudio build (the cygwin build will crash in the loop)
It's not a bug if freed memory is not given back to the system.
Fragmentation probably prevents this in this case.
--Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4