I will investigate as much as I can, I suspect there might be a need to put larger amount of data into the pak to cause these issues. It could be usefull to have an engineer look at this section of code since this issue did not happen before 4.16. Someone with more insight into what has changed and why this would happen could perhaps shed more light on it.
On my end all I can do is process-of-elimination which might take a while to analyse.