Sorting issue in containers

[atb00ker]

Describe the bug

When I have the following setting:

[containers]
all=True

I am seeing the exited containers in the list, but the exited containers mess up the sorting.
Example, when I sort with memory used, I see:

B	running	58 mins	0	100.5M	11.6G	0	0	864b	0b	/usr/local/bin/entrypoint.sh
A	running	58 mins	0	41.5M	11.6G	0	0	864b	0b	/usr/local/bin/entrypoint.sh
C	exited		NaN	?	-	-	-	NaNb	NaNb	[ "/init" ]
D	running	a week	0	365M	11.6G	0	0	920b	80b	/init
E	running	58 mins	0	100.5M	11.6G	0	0	864b	0b	/usr/local/bin/entrypoint.sh
F	exited		NaN	?	-	-	-	NaNb	NaNb	/usr/local/bin/entrypoint.sh
H	running	a week	0	592M	11.6G	0	0	864b	0b	/usr/local/bin/entrypoint.sh
G	running	58 mins	0	100.5M	11.6G	0	0	864b	0b	/usr/local/bin/entrypoint.sh

To Reproduce
Steps to reproduce the behavior:

1. Start glances with following options:

[containers]
all=True

2. Run, say, 5 containers, let say containers are named as followed: A, B, C, D, E
   Note: (naming is important because alphabetically sorting is messing things):

3. Stop the container C

4. Sort on Memory usage.
   Note that container A and B will be sorted and container D and E will be sorted.
   But they wouldn't show proper sorting among each other, i.e if D consumes more memory than A it will still be below C because value of C is ? and it alphabetically sorted itself to the position.

Expected behavior

I would expect an exited container to consume 0 memory and CPU and sort itself accordingly at the bottom.