It would appear that specifying a search window in your textgrids for feature extraction that is too small leads to malloc errors that are a bit cryptic and hard to debug. Perhaps some note about minimum window sizes and a custom error message for this problem would be a good idea?
For example, during feature extraction for voiced stops I received the following error message:
VotFrontEnd2(16557,0x7fff721e1000) malloc: *** error for object 0x7fa86a011808: incorrect checksum for freed object - object was probably modified after being freed.
*** set a breakpoint in malloc_error_break to debug
It would appear that specifying a search window in your textgrids for feature extraction that is too small leads to malloc errors that are a bit cryptic and hard to debug. Perhaps some note about minimum window sizes and a custom error message for this problem would be a good idea?
For example, during feature extraction for voiced stops I received the following error message: