If we pass an invalid scratch pointer to secp256k1_scratch_destroy, the VERIFY_CHECK will probably fail, and libsecp will crash with the message
src/scratch_impl.h:28: test condition failed: scratch->alloc_size == 0
If VERIFY_CHECK after the invalid scratch space check, libsecp will call the error callback function with the "invalid scratch space" message instead.