this behaves differently, sometimes OOM, other times it throws a syntax error which then logs out the entire json string as the exception message.
this json sample is 24mb, it should never be all logged out. the exception message should be always be short and understandable.
it's three times worse, coz the message gets logged out three times
also, I think the memory isn't being released as the exception is kept in memory with debugging enabled
also when this runs successfully, the DeserializeJson timer output doesn't work either?
I've checked this ticket and confirmed the issue happened on lucee latest version 126.96.36.199 SNAPSHOT also. Yeah, the exception message shows full 24mb JSON data and also it created an exception.log.1.bak file having a size of almost 80mb at every time run the file.
Potentially sensitive info should only be in the error detail
can you move the cfml snippet
to the exception detail?
otherwise sensitive information may be exposed
, Moved the CFML snippet to exception detail.