umm_malloc manual merge with upstream by mhightower83 · Pull Request #7337 · esp8266/Arduino (original) (raw)

I think not. The current behavior is that it's not possible to do malloc(maxBlock), which can be unexpected. However, from your explanations on gitter, even if you manage to make it work for maxBlock, it could potentially fail e. g. for maxBlock-overhead, because then the remaining space can't be divided. And that is also unexpected, which means the original cause for fixing it isn't resolved.
Like you said, too many corner cases, and hence too fragile.
I suggest reverting that. A comment has already been added to the docs stating that the maxBlock means free mem chunk, and that size can't be malloced due to overhead.