Am 11.09.2012 12:22, schrieb Eldar Insafutdinov:
On Monday, 10 September 2012 at 21:18:41 UTC, Sönke Ludwig wrote:
Am 10.09.2012 23:03, schrieb Nick Sabalausky:
On Mon, 10 Sep 2012 22:26:39 +0200
Sönke Ludwig sludwig@rejectedsoftware.com wrote:My current plan is to default to safe GC memory, which is reasonably
fast, and to provide the option to use the faster but unsafe manual
version when speed really matters. (I just tested the GC version and
its memory consumption is stable and only slightly worse with
11MB/5,8MB)Oh, so the memory leak is fixed in the GC version, too?
Jep, it just holds on a bit more memory than it should because of a pool
allocator that is filled with each request - but eventually the whole
pool will get collected. I'll test a bit more and switch back to the GC
version as the default tomorrow.With the latest commit that enables GC allocator as a default one the
server crashes immediately after startup.
Should work again. The Windows GC seems to be lazy compared to the Linux
one and avoided the crash. There were some untracked GC allocations in
the libevent back end that are now back to manual.