This repository was archived by the owner on Sep 8, 2020. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 8, 2020. It is now read-only.
Strange niceness value on WSL #993
Description
I was running nice ninja -j10 -k0 all check-all on WSL Ubuntu, and started htop in a second WLS window. The output looked like this:
1 [||||| 20.8%] 4 [||||||| 33.8%] 7 [| 4.0%] 10 [ 0.0%]
2 [|||| 13.9%] 5 [||| 10.5%] 8 [| 1.3%] 11 [| 4.0%]
3 [||||||||| 45.0%] 6 [ 0.0%] 9 [| 3.3%] 12 [ 0.0%]
Mem[|||||||||||||||||||||| 6.89G/16.0G] Tasks: 23, 4 thr; 2 running
Swp[||| 1005M/19.5G] Load average: 0.52 0.58 0.59
Uptime: 05:09:02
PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command
1 root 20 0 8896 276 240 S 0.0 0.0 0:00.09 /init
3534 root 20 0 8896 216 172 S 0.0 0.0 0:00.00 ├─ /init
3535 csaba 20 0 16888 3504 3424 S 0.0 0.0 0:00.10 │ └─ -bash
3617 csaba 20 0 16720 3656 1612 R 0.0 0.0 0:00.18 │ └─ htop
6 root 20 0 8896 164 120 S 0.0 0.0 0:00.00 ├─ /init
7 csaba 20 0 17020 3412 3268 S 0.0 0.0 0:00.26 │ └─ -bash
9418 csaba 10 4294967286 127M 19212 416 S 0.0 0.1 0:10.16 │ └─ ninja -j10 -k0 all check-all
18411 csaba 10 4294967286 10660 592 560 S 0.0 0.0 0:00.00 │ └─ /bin/sh -c cd /home/csaba/w
18412 csaba 10 4294967286 2580M 869M 46384 S 0.0 5.3 1:23.40 │ └─ /usr/bin/python2.7 /home
18641 csaba 10 4294967286 2580M 869M 46384 S 0.0 5.3 0:39.75 │ ├─ /usr/bin/python2.7 /h
18640 csaba 10 4294967286 2580M 869M 46384 S 0.0 5.3 0:22.96 │ ├─ /usr/bin/python2.7 /h
18639 csaba 10 4294967286 2580M 869M 46384 S 0.0 5.3 0:01.07 │ ├─ /usr/bin/python2.7 /h
18638 csaba 10 4294967286 130M 11848 10388 S 0.0 0.1 2:06.02 │ ├─ /usr/bin/python2.7 /h
18637 csaba 10 4294967286 130M 37092 35000 S 0.0 0.2 2:07.55 │ ├─ /usr/bin/python2.7 /h
18636 csaba 10 4294967286 130M 37044 35020 S 0.0 0.2 2:00.30 │ ├─ /usr/bin/python2.7 /h
18635 csaba 10 4294967286 131M 38712 36544 S 0.0 0.2 2:07.46 │ ├─ /usr/bin/python2.7 /h
18634 csaba 10 4294967286 130M 36688 34672 S 0.0 0.2 1:58.85 │ ├─ /usr/bin/python2.7 /h
18633 csaba 10 4294967286 130M 36816 34820 S 0.0 0.2 2:06.64 │ ├─ /usr/bin/python2.7 /h
18632 csaba 10 4294967286 129M 36076 34712 S 0.0 0.2 2:03.88 │ ├─ /usr/bin/python2.7 /h
8856 csaba 10 4294967286 12180 1552 1476 S 0.0 0.0 0:00.04 │ │ └─ /bin/bash /home/cs
8921 csaba 10 4294967286 100T 2452 1432 R 100. 0.0 2h39:33 │ │ └─ /home/csaba/wk/
18631 csaba 10 4294967286 130M 36932 34812 S 0.0 0.2 2:02.29 │ ├─ /usr/bin/python2.7 /h
18630 csaba 10 4294967286 129M 36072 34104 S 0.0 0.2 1:56.90 │ ├─ /usr/bin/python2.7 /h
18629 csaba 10 4294967286 129M 35564 34356 S 0.0 0.2 2:02.48 │ ├─ /usr/bin/python2.7 /h
18628 csaba 10 4294967286 130M 36872 33792 S 0.0 0.2 2:01.04 │ ├─ /usr/bin/python2.7 /h
18627 csaba 10 4294967286 129M 35652 34304 S 0.0 0.2 2:09.10 │ └─ /usr/bin/python2.7 /h
5 root 20 0 8896 276 240 S 0.0 0.0 0:00.00 └─ /init
Note the value 4294967286 for the NI column. This is consistent with what ps reported:
ps -eo pid,user,pri,ni,args --sort user
PID USER PRI NI COMMAND
7 csaba 19 0 -bash
11896 csaba 19 0 -bash
11926 csaba 29 4294967286 ninja -j10 -k0 all check-all
12454 csaba 29 4294967286 /bin/sh -c cd /home/csaba/wk/llvm
However, htop is seemingly not prepared for such a value, and the columns get out of alignment.
Either htop should be able to display such a large "nice" value, or 4294967286 could be special-cased.
Activity