Stack overflow in base64_decode()
Issue raised by user 2018-02-05 via email: stack overflow inside base64_decode() function, when a large data file is supplied.
One step of the work around produced for Bug #3163 uses the internal SaxonJS.U.Atomic.base64Binary.fromString() function to decode a base-64 encoded version of an SEF. SaxonJS.U.Atomic.base64Binary.fromString() calls base64_decode(). The function is used to decode a string of data which has been encoded using base-64 encoding. The output data is represented as a string containing octets/codepoints in the range 0-255.
It is suspected that the stack overflow is caused by the large regex at the start of the base64_decode() function.
Please register to edit this issue