Valgrind fails in CI

[phischu]

No description provided.

[mattisboeckle]

I did some investigating on these valgrind errors and found that it was complaining about "uninitialized value was created by a heap allocation" when using bytearrays.

If we just initialize the allocated memory to 0 the valgrind errors disappear (at least locally)

[jiribenes]

I'm all for using calloc in bytearrays :)

[b-studios]

That would be great! Is there any performance implications of doing that?

[marvinborner]

I'm confused, this shouldn't be a problem, right? Why are we reading from the bytearray when it's not initialized yet (especially in all IO tests)? If I remember correctly, we've discussed calloc-ing before and decided against it(?)

I think the performance implications could be significant, since bytearrays could be used for loading multiple gigabytes of data etc.

[phischu]

It is good to know that initializing the array would fix it, but we should not actually initialize them to zero every time. Rather, we should find the underlying out-of-bounds access. I can not reproduce those errors locally, but @mattisboeckle since you can, please take a look.