Fcalva/cyclone
1
0
Fork 0
mirror of https://github.com/justinethier/cyclone.git synced 2025-07-14 08:17:35 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

More notes

Browse source
This commit is contained in:
Justin Ethier 2015-12-04 23:38:09 -05:00
parent 11864e558f
commit 0946d56aaa
1 changed files with 3 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
gc-notes.txt
View file

@ -12,6 +12,9 @@ memory corruption
at that point by the collector thread, so no one is around to mark this object. at that point by the collector thread, so no one is around to mark this object.
wait a minute - but how does the obj even get on the heap? see this - if above was true there would be no ref to move this to the heap, right? so what is going on?? -> wait a minute - but how does the obj even get on the heap? see this - if above was true there would be no ref to move this to the heap, right? so what is going on?? ->
alloc 0xb78400e0 size = 32, obj=0xbffcd648, tag=0, mark=1 alloc 0xb78400e0 size = 32, obj=0xbffcd648, tag=0, mark=1
well, we also move globals, which would explain it since the next lambda becomes the head of the global list. so I think that explains it. the most expedient change is to just use moveBuf to mark the thread's roots.
but again, this did not fix all crashes, so there are either other issues with the GC (not surprising, although disappointing) or this is not the issue. but I think this has to be a problem given the error output observed today.
TODO: TODO:
- need to fix memory corruption bugs - need to fix memory corruption bugs