Zip4j loops when trying to create split zip files when metadata size is greater than partiton size

[Charles-PORROT]

Hello.

Our project uses zip4j v2.11.5.

We encountered an issue when using the library to make split zip files.
We have noticed a bug where, if the size of the metadata is greater than the partion size (for instance, 816Ko > 512ko), the API is unable to store the headers in the final zip file, and loops indefinitely until the JVM encounters an OoM error.

We can go around this bug by increasing the partition size, however our client requests that we find a more stable solution, as they aim to work on very large quantities of data and would like a scalable solution.

Is there a technical possibility to solve the behaviour in this library ?