Duncan Coutts wrote:
On Sun, 2006-09-24 at 01:28 +0400, Bulat Ziganshin wrote:
Hello Duncan,
Sunday, September 24, 2006, 12:22:38 AM, you wrote:
after program prints 40 mb allocated look at Task Manager indication
- it shows that two times more memory actually in use. it seems that
problem
: Re: bug in mallocForeignPtrBytes (both 6.4 and 6.6)
|
| Duncan Coutts wrote:
| On Sun, 2006-09-24 at 01:28 +0400, Bulat Ziganshin wrote:
|
| Hello Duncan,
|
| Sunday, September 24, 2006, 12:22:38 AM, you wrote:
|
|
| after program prints 40 mb allocated look at Task Manager
indication
Hello Duncan,
Sunday, September 24, 2006, 12:22:38 AM, you wrote:
after program prints 40 mb allocated look at Task Manager indication
- it shows that two times more memory actually in use. it seems that
problem is only with allocating memory buffers whose sizes are powers
of 2 or very close
On Sun, 2006-09-24 at 01:28 +0400, Bulat Ziganshin wrote:
Hello Duncan,
Sunday, September 24, 2006, 12:22:38 AM, you wrote:
after program prints 40 mb allocated look at Task Manager indication
- it shows that two times more memory actually in use. it seems that
problem is only with
Hello glasgow-haskell-users,
the attached program show up the bug in mallocForeignPtrBytes (and
newPinnedByteArray#) implementation - it allocates two times more
memory as requested. The bug seen both on 6.6rc and june 6.4 windows
builds, namely:
On Sat, 2006-09-23 at 13:58 +0400, Bulat Ziganshin wrote:
Hello glasgow-haskell-users,
the attached program show up the bug in mallocForeignPtrBytes (and
newPinnedByteArray#) implementation - it allocates two times more
memory as requested. The bug seen both on 6.6rc and june 6.4 windows