I have the same issue on sen2cor v2.4.0.
A workaround is to avoid the processing of bands at 10 m resolution, I confirm that the process reach successfully the end if ‘–resolution 20’ argument is used when running sen2cor.
Since this problems was affecting also the previous version, as also reported in this post, I am wondering if sen2cor developers are aware of this bug since it has not been corrected in the last release.
Federico