Graeme Gill wrote:
Unfortunately I'm unable to reproduce the problem, and I tried a few differentI experience the issue on Windows 10 (x64). Are there any options (or environment variables may be) to enable extended logging? Or some debug build to run on my machine, or whatever else that could help identify the problem. I'm ready to assist as much as I'm capable of (if you have time to investigate the issue, of course).
systems. It smells a like an un-initialized variable or memory overwrite, but
running on Linux with valgrind didn't uncover anything suspicious.
Without more hints as to what triggers it, I'm at a loss.
