Context Navigation

Changes between Initial Version and Version 1 of Ticket #17847, comment 29

initial	v1
1		Tested hrev56325 x64. Suspends a thread on my physical system - see Core 3 (added an attachment). Can resume if I mouse click between active/inactive windows. I can jump into KDL, run commands and then exit, then the thread resumes further - sometimes it does it again within 30 minutes and sometimes not again - or after several hours of a consistent haikuporter-based build project. I tested this by building both blender and qtwebengine with haikuporter (ie. long stress test condition). With smaller hp builds like blender, the threading issue may happen 1 out of 3-4 builds. With the qywebengine, I'll usually get it within 20-30 minutes after compiling starts.
	1	Tested hrev56325 x64. Suspends a thread on my physical system - see Core 3 (added an attachment). Can resume if I mouse click between active/inactive windows. I can jump into KDL, run commands and then exit, then the thread resumes further - sometimes it does it again within 30 minutes and sometimes not again - or after several hours of a consistent haikuporter-based build project. I tested this by building both blender and qtwebengine with haikuporter (ie. long stress test condition). With smaller hp builds like blender, the threading issue may happen 1 out of 3-4 builds. With the qtwebengine, I'll usually get it within 20-30 minutes after compiling starts.
2	2
3	3	If you use ProcessController, it may trigger a system freeze. No high memory/CPU/thread usage during this time when thread is pending/stalled.