There are also some similar bugs need to fix.
I'll fix it as soon as I can.

Hi @MicroMilo
Thank you for the PR

While some of the changes make sense (clmessage length and division by 0) - the rest of return value checks are actually bad IMHO
There is no backup plan or recovery from failure to allocate memory and it is good that the app crashes
If malloc/calloc/realloc fail - there is absolutely no point to try and continue running. Moreover, it is harmful as it hides the real issue (if the app actually runs for some time after failure to allocate memory)
In some place, the fix includes logging the issue - which again needs memory allocated. In this case, best case scenario, the crash will show that memory allocation failed in logging - which is not true issue.

This is a generic issue with automatic scanners that warn about return value validation. In case of memory allocation - those do not have value.

To sum it up: I recommend against memory allocation validation changes - I'll review the rest after that.

Thanks again!

Thanks, @eakraly.
Thank you for your response. I think I know what you think about memory management.
I put forward this PR out of the discussion in #1762.

Leaving memory management aside, I still have some issues regarding null Pointers. Do you want me to request a PR?
for example: #1763, #1765