search for: dlmalloc

...ated (total KB allocated in the memory utilization page). Squid is using around twice as much memory as expected, and seems to grow without bounds (I run out of memory every now and then). I've tried configuring malloc.conf with H (as suggested by tjr), but it didn't help. Using Squid with dlmalloc however (--enable-dlmalloc), seems to stop the memory leaks. For my own purposes, I'll be using dlmalloc from now unless someone has other suggestions. For the record, I'm using 4.8-RELEASE and Squid 2.5.STABLE3 (recently installed from ports with all the patches there). I have Squid serve...

...ructures. Unfortunately that could be > happening anywhere. Writing R extensions, section 6.1.2 says: "Do not assume that memory allocated by Calloc/Realloc comes from the same pool as used by malloc: in particular do not use free or strdup with it." I think the reason is that R uses dlmalloc for Calloc on Windows: https://github.com/wch/r-source/blob/c634fec5214e73747b44d7c0e6f047fefe44667d/src/main/memory.c#L94-L103

...anywhere. >> >> Writing R extensions, section 6.1.2 says: "Do not assume that memory >> allocated by Calloc/Realloc comes from the same pool as used by >> malloc: in particular do not use free or strdup with it." >> >> I think the reason is that R uses dlmalloc for Calloc on Windows: >> https://github.com/wch/r-source/blob/c634fec5214e73747b44d7c0e6f047fefe44667d/src/main/memory.c#L94-L103 > > But that section #defines calloc and free to Rm_... counterparts in lockstep? (I assume that is where dlmalloc comes in?) > > Anyways, does it act...

...be >> happening anywhere. > > Writing R extensions, section 6.1.2 says: "Do not assume that memory > allocated by Calloc/Realloc comes from the same pool as used by > malloc: in particular do not use free or strdup with it." > > I think the reason is that R uses dlmalloc for Calloc on Windows: > https://github.com/wch/r-source/blob/c634fec5214e73747b44d7c0e6f047fefe44667d/src/main/memory.c#L94-L103 But that section #defines calloc and free to Rm_... counterparts in lockstep? (I assume that is where dlmalloc comes in?) Anyways, does it actually work to change f...

...gt;>> Writing R extensions, section 6.1.2 says: "Do not assume that memory >>> allocated by Calloc/Realloc comes from the same pool as used by >>> malloc: in particular do not use free or strdup with it." >>> >>> I think the reason is that R uses dlmalloc for Calloc on Windows: >>> https://github.com/wch/r-source/blob/c634fec5214e73747b44d7c0e6f047fefe44667d/src/main/memory.c#L94-L103 >> >> But that section #defines calloc and free to Rm_... counterparts in lockstep? (I assume that is where dlmalloc comes in?) >> >&gt...

...find -ldl configure: failed program was: #line 1887 "configure" #include "confdefs.h" #include <stdio.h> #include <ao/ao.h> int main() { return 0; ; return 0; } I couldn't find a libdl on my machine. The closest thing that matched in the ports section was libdlmalloc. This installed a libdlmalloc.so in /usr/local/lib. I linked this to /usr/local/lib/libdl.so and the configure exited without errors. Now a make dies with /usr/include/sys/socket.h:443: syntax error before `send' /usr/include/sys/socket.h:443: warning: data definition has no type or storage c...

...counting. Instead, I took one component of my GC - the general heap implementation - and built a trivial mark & sweep collector on top of it, which seems to be working very well for my purpose. This GC heap was to be the foundation for my collector. It's loosely inspired by the popular dlmalloc implementation (although it doesn't directly take any code from it), but it also supports a number of features useful for implementing a collector, such as the ability to efficiently walk the heap and free blocks based on a predicate callback. It also reserves space in the 8-byte allocation...

Hello, I was wondering how folks were feeling about replacing the default Windows CRT allocator in Clang, LLD and other LLVM tools possibly. The CRT heap allocator on Windows doesn't scale well on large core count machines. Any multi-threaded workload in LLVM that allocates often is impacted by this. As a result, link times with ThinLTO are extremely slow on Windows. We're observing

Hi all, Over the past couple weeks, I've been putting together a JavaScript backend for LLVM. At this point, I believe I've got reasonable implementations for all the instructions, primitives and derived types. I haven't gotten around to most of the intrinsics but I thought it would be a good idea to start getting some feedback before going much further. If anyone has the time and

So this wasn't tested for a month? Anyways, Free() is just free() with a check that we're not freeing a null pointer, followed by setting the pointer to NULL. At that point of tcltk.c, we have for (objc = i = 0; i < length(avec); i++){ const char *s; char *tmp; if (!isNull(nm) && strlen(s = translateChar(STRING_ELT(nm, i)))){ // tmp =