Description: Running w -shi results in a segmentation fault.

On Sep 9 I upgraded procps-ng 4.0.3-1 -> 4.0.4-1 on 3 separate laptops. Since that upgrade, I'm getting random segfaults from /usr/bin/w using "shi" flag on all 3 laptops. I use this command in a script that sends me a status email hourly. I've been running the command this way for over a year without issue. Beginning with 4.0.4, I'm getting random segfaults from that command. I'm running LTS kernel on all 3 machines.

Additional info:
* package version(s) - 4.0.4 (procps-ng 4.0.4-1)
* config and/or log files etc. - journalctl for a recent event:

Sep 17 08:07:35 computer kernel: w[5081]: segfault at 15c ip 000055f9e95259e8 sp 00007fff93fedcc0 error 4 in w[55f9e9525000+2000] likely on CPU 2 (core 1, socket 0)
Sep 17 08:07:35 computer kernel: Code: 24 f8 0f 00 00 00 48 39 fc 75 eb 81 e6 ff 0f 00 00 48 29 f4 48 85 f6 74 06 48 83 4c 34 f8 00 49 89 e7 85 d2 0f 84 28 01 00 00 <49> 8b 84 24 5c 01 00 00 49 8b 94 24 64 01 00 00 48 89 c6 48 89 45
Sep 17 08:07:35 computer systemd[1]: Started Process Core Dump (PID 5082/UID 0).
Sep 17 08:07:35 computer systemd-coredump[5083]: Process 5081 (w) of user 1000 dumped core.
Sep 17 08:07:35 computer systemd[1]: systemd-coredump@5-5082-0.service: Deactivated successfully.

Steps to reproduce:

enter w -shi on the command line.