Oh dear, we're back to the navmap not loading for some people. The high CPU is obviously because it's spinning waiting for the navmap to come up. I've never been able to reproduce this but you can try deleting navmap, QtWebEngine and wingman.cfg in AppData/Local/wingman to reset the cache.