Either I'm confused or the gc is

[Steven Schveighoffer]

On 10/21/20 12:24 PM, donallen wrote:

> The problem is that at some point, the verifier starts spewing bogus 
> error messages about what it is seeing in the tree. Oddly, putting in 
> debugging writelns results in the error messages not occurring -- a 
> Heisenbug.  But working with gdb, I found that the account structs after 
> the error messages start are zeroed. Turning on gc profiling tells me 
> that 3 gcs have occurred. Disabling the gc results in the program 
> running correctly -- no error messages (and I know the database has no 
> errors because the C version, which has been around for awhile, confirms 
> that the db is well formed).

Something I thought of - try running manual GC collections:

import core.memory;

GC.collect(); // peppered around your code

It might make your code fail closer to the true problem.

-Steve