[BUG]: crash in DataLogWriter

[virtuald]

Problem description

Reported on discord. Reproduced on my mac, looks like it's crashing in the log.flush for some reason.

from wpiutil import DataLogWriter
from wpiutil.log import IntegerLogEntry

log = DataLogWriter("something.wpilog")

e = IntegerLogEntry(log, "test")
e.append(5)
e.finish()

log.flush()
print("Done")

Operating System

MacOS

Installed Python Packages

Reproducible example code

[Braykoff]

I believe I was the one who originally reported this on Discord. It seems to be some sort of memory error, and is inconsistent (ie, if I run the script 10 times, it might work fine half of them). I'm running it with Python memory tracing, and I've gotten this:

(.venv) braykoff@MacBook-90 Folder % PYTHONMALLOC=debug python wpilogtest.py
Done
Debug memory block at address p=0x13fe11340: API 'r'
    0 bytes originally requested
    The 7 pad bytes at p-7 are FORBIDDENBYTE, as expected.
    The 8 pad bytes at tail=0x13fe11340 are not all FORBIDDENBYTE (0xfd):
        at tail+0: 0xdd *** OUCH
        at tail+1: 0xdd *** OUCH
        at tail+2: 0xdd *** OUCH
        at tail+3: 0xdd *** OUCH
        at tail+4: 0xdd *** OUCH
        at tail+5: 0xdd *** OUCH
        at tail+6: 0xdd *** OUCH
        at tail+7: 0xdd *** OUCH

Enable tracemalloc to get the memory block allocation traceback

Fatal Python error: _PyMem_DebugRawFree: bad trailing pad byte
Python runtime state: finalizing (tstate=0x14fe127a0)

Current thread 0x000000020c96df00 (most recent call first):
<no Python frame>
zsh: abort      PYTHONMALLOC=debug python wpilogtest.py

Ocassionally, the only output I get is this:

(.venv) braykoff@MacBook-90 Folder % PYTHONMALLOC=debug python wpilogtest.py
zsh: trace trap  PYTHONMALLOC=debug python wpilogtest.py