I suspect it is this:
- Tor Browser is running on one machine and talking to Tor on another machine.
- When time is changed using
dateon another machine, Tor Browser starts to use 100% CPU.
Still not “really” a Whonix issue. Also not “really” an sdwdate issue. It still needs to be reproduced without mentioning Whonix / sdwdate as a general bug and then reported against Tor Project trac component Tor Browser.
Originally reported here with lots of discussion: