dhalbert
commented
4 years ago Something is clearly going wrong with storage management, so we'll need to look at the heap allocation that happens during scanning, and whether the internal audio buffers are being managed properly (they are on the root pointer list, etc.). @jepler does this ring any bells w/r/t audio?
Thanks for coming up with a really simple example that is just audio playing in the background during a scan. That narrows things down considerably, since there's no audio Python code that's being called in a loop or anything like that.
jepler
kevinjwalters
I had some code which was working well until I changed the WaveFile use to include a pre-allocated 2048
bytearray. That new code fell over in different bizarre ways on three boards, one went into the hard fault handler.I've experimented a bit with REPL and I believe one way of triggering this is with adafruit_ble's
start_scan(). This is where the real application falls over too although it's interesting that it worked perfectly with WaveFile doing its own thing for buffers.Here's a reproduction of the issue on the nRF52840-based Adafruit CLUE.
Nothing more appears on the serial connection as it's now kaput. The screen on the CLUE is useful here as it reports:
Running in safe mode: Not running saved code.I suspect that
TypeError: can't convert 'float' object to str implicitlyis bogus and just caused by memory corruption.BTW, would be useful to have some tips about whether the bytearray size should vary based on the wav file rate and/or playback rate in the docs. The docs also mention 2x512 but I've seen
MemoryErrorexceptions for 2048 bytes when I run out of memory.