What happens when mimalloc: warning: unable to allocate from region: size 4194304 in log and then continues

[jolespin]

 11:22:48.296    76G / 215G  INFO    General                 (sequence_mapper_notifier.h:  77)   Processed 200000 reads
 11:22:48.313    76G / 215G  INFO    General                 (sequence_mapper_notifier.h:  77)   Processed 400000 reads
 11:22:48.485    76G / 215G  INFO    General                 (sequence_mapper_notifier.h:  77)   Processed 600000 reads
 11:22:48.514    76G / 215G  INFO    General                 (sequence_mapper_notifier.h:  77)   Processed 800000 reads
 11:22:48.526    76G / 215G  INFO    General                 (sequence_mapper_notifier.h:  77)   Processed 1000000 reads
 11:22:48.566    76G / 215G  INFO    General                 (sequence_mapper_notifier.h:  77)   Processed 1200000 reads
 11:22:48.624    76G / 215G  INFO    General                 (sequence_mapper_notifier.h:  77)   Processed 2200000 reads
 11:23:08.337    76G / 215G  INFO    General                 (sequence_mapper_notifier.h:  77)   Processed 4200000 reads
 11:23:21.826    76G / 215G  INFO    General                 (sequence_mapper_notifier.h:  77)   Processed 8400000 reads
 11:23:59.659    76G / 215G  INFO    General                 (sequence_mapper_notifier.h:  77)   Processed 16800000 reads
 11:25:06.696    76G / 215G  INFO    General                 (sequence_mapper_notifier.h:  77)   Processed 33600000 reads
 11:27:24.184    77G / 215G  INFO    General                 (sequence_mapper_notifier.h:  77)   Processed 67200000 reads
 11:32:02.958    77G / 215G  INFO    General                 (sequence_mapper_notifier.h:  77)   Processed 134400000 reads
mimalloc: warning: unable to allocate from region: size 4194304
mimalloc: warning: unable to allocate from region: size 4194304
mimalloc: warning: unable to allocate from region: size 4194304
mimalloc: warning: unable to allocate from region: size 4194304
mimalloc: warning: unable to allocate from region: size 4194304
mimalloc: warning: unable to allocate from region: size 4194304
mimalloc: warning: unable to allocate from region: size 4194304
mimalloc: warning: unable to allocate from region: size 4194304
mimalloc: warning: unable to allocate from region: size 4194304
mimalloc: warning: unable to allocate from region: size 4194304
mimalloc: warning: unable to allocate from region: size 4194304
mimalloc: warning: unable to allocate from region: size 4194304
mimalloc: warning: unable to allocate from region: size 4194304
mimalloc: warning: unable to allocate from region: size 4194304
mimalloc: warning: unable to allocate from region: size 4194304
mimalloc: warning: unable to allocate from region: size 4194304
mimalloc: warning: unable to allocate from region: size 4194304
 11:43:54.159    78G / 215G  INFO    General                 (sequence_mapper_notifier.h:  77)   Processed 268600000 reads
 12:04:50.310    91G / 215G  INFO    General                 (sequence_mapper_notifier.h:  95)   Total 442672592 reads processed

I'm making a pretty massive assembly. I had a few other jobs running our server that are computationally intensive and noticed the lines in the spades mimalloc: warning: unable to allocate from region: size 4194304 and then it goes to 11:43:54.159 78G / 215G INFO General (sequence_mapper_notifier.h: 77) Processed 268600000 reads

I have a few questions:

1. Is this likely because of the high memory jobs that were also running on the server concurrently?
2. Did an error occur or was this only a warning?
3. If (1) was true, if those jobs continued would it have caused this metaSPAdes job to be killed?
4. Are any of the downstream steps from here memory intensive (as I've started the other jobs again). I'm at the final k-mer stage K55.

[asl]

These warnings are benign