Procedure to re-create the problem:
1) Set up a 14 mile or longer out-and-back course.
2) Start a run; enable navigation for the 14 mile out-and-back course.
3) Switch between the different available screens, including scrolling through the map screen.
When the above is done, the watch reboots.
I'm not sure of the exact length of the course needed to reproduce this problem, but I have two different 14.x mile out-and-back courses that recreate this problem. I've not been able to determine what is special about these courses other than the fact that they are out-and-back and rather lengthy. I've not had this problem with any number shorter courses. I've also not had this problem with a 15.x mile loop course. I've also not had this problem with an 13.1 mile A-to-B course.
SW: v16.22
