![]() If the 1.0.8.2 is the first viewer connected, the server will jump to 100% CPU.Ģ. In following, the 10961 server was configured to accept multi viewers coonection (i.e.: Keep Existing Connections), the viewer is 1.0.8.2 and 1.0.9.6ġ. On the other hand, when using the 1.0.9.5 or 1.0.9.6 or 10961 viewer to connect to 10961 server, all are working properly with any one of the settings.Īlthough (probably) the problem source is located, I would like to report some interesting phenomenon I saw during my test. Don't show remote cursor - server 100% CPU Let remote server deal with mouse cursor - Connection established properly, CPU consumption normal. Track remote cursor locally - server 100% CPU Here are my test results of 1.0.8.2 viewer connecting to 10961 server, with following setting: OK! After hours of testing & testing, again & again, finally I locate the setting the causing this issue: the Remote Cursor Setting of viewer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |