mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

devblog

Browse source
This commit is contained in:
Joey Hess 2020-10-13 18:41:47 -04:00
parent c8995b040f
commit e726aee7be
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
doc/devblog/day_631-632__memory_leak.mdwn
View file

@ -1,14 +1,14 @@
I've spent two days trying to track down a recently introduced memory leak,
or leaks. This was unusually hard because all the profiler could tell
me is the memory is "PINNED", but not what allocated it or anything else
about it.
about it.
I probably should have bisected it, rather than staring at the code and
randomly reimplementing things I thought could be pinning memory. Oops.
Anyway, I've solved one of them, and the other one, if it's a memory leak
at all, is memory that the profiler does not even show is in use, but that
does appear to be allocated, at least as far as mmap goes.
And there is more memory that the profiler doesn't even show
being allocated, which got much bigger with a new toolchain, and I have not
gotten to the bottom of that yet.
--