{"action":"created","issue":{"url":"https://api.github.com/repos/MaxXor/xRAT/issues/29","labels_url":"https://api.github.com/repos/MaxXor/xRAT/issues/29/labels{/name}","comments_url":"https://api.github.com/repos/MaxXor/xRAT/issues/29/comments","events_url":"https://api.github.com/repos/MaxXor/xRAT/issues/29/events","html_url":"https://github.com/MaxXor/xRAT/issues/29","id":63023554,"number":29,"title":"Remote Desktop Issues","user":{"login":"yankejustin","id":9338742,"avatar_url":"https://avatars.githubusercontent.com/u/9338742?v=3","gravatar_id":"","url":"https://api.github.com/users/yankejustin","html_url":"https://github.com/yankejustin","followers_url":"https://api.github.com/users/yankejustin/followers","following_url":"https://api.github.com/users/yankejustin/following{/other_user}","gists_url":"https://api.github.com/users/yankejustin/gists{/gist_id}","starred_url":"https://api.github.com/users/yankejustin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/yankejustin/subscriptions","organizations_url":"https://api.github.com/users/yankejustin/orgs","repos_url":"https://api.github.com/users/yankejustin/repos","events_url":"https://api.github.com/users/yankejustin/events{/privacy}","received_events_url":"https://api.github.com/users/yankejustin/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/MaxXor/xRAT/labels/bug","name":"bug","color":"fc2929"},{"url":"https://api.github.com/repos/MaxXor/xRAT/labels/help%20wanted","name":"help wanted","color":"159818"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-03-19T15:54:09Z","updated_at":"2015-03-21T03:47:10Z","closed_at":null,"body":"Already known, but just kept here in case others would like to investigate or propose fixes to these issues with the Remote Desktop feature.\r\n\r\nIssues:\r\n1) Sucks down memory on the Client - Yes, the Garbage Collector will eventually collect the unused resources that have gone astray. However, it does so every second (low-blow to the performance train). It could be very negative to the user if the machine being used is rather poor. The memory allocations will stay around 200MB to 700MB while running the Remote Desktop tool. It will cycle up and down those limits as fast as 3/4 of a second to 1 second...\r\n2) Issues with multiple monitors:\r\n--> When receiving data of a monitor that is larger than the one you are watching (ex: client has a 1920x1080 monitor and yours is 1080x760) the smaller monitor does not correctly scale the image. This issue is likely due to the way changes are calculated on the client. It causes random pixel anomalies (black pixels, poor resolution in some patches)."},"comment":{"url":"https://api.github.com/repos/MaxXor/xRAT/issues/comments/84239091","html_url":"https://github.com/MaxXor/xRAT/issues/29#issuecomment-84239091","issue_url":"https://api.github.com/repos/MaxXor/xRAT/issues/29","id":84239091,"user":{"login":"yankejustin","id":9338742,"avatar_url":"https://avatars.githubusercontent.com/u/9338742?v=3","gravatar_id":"","url":"https://api.github.com/users/yankejustin","html_url":"https://github.com/yankejustin","followers_url":"https://api.github.com/users/yankejustin/followers","following_url":"https://api.github.com/users/yankejustin/following{/other_user}","gists_url":"https://api.github.com/users/yankejustin/gists{/gist_id}","starred_url":"https://api.github.com/users/yankejustin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/yankejustin/subscriptions","organizations_url":"https://api.github.com/users/yankejustin/orgs","repos_url":"https://api.github.com/users/yankejustin/repos","events_url":"https://api.github.com/users/yankejustin/events{/privacy}","received_events_url":"https://api.github.com/users/yankejustin/received_events","type":"User","site_admin":false},"created_at":"2015-03-21T03:47:10Z","updated_at":"2015-03-21T03:47:10Z","body":"The problem is that the garbage collector is collecting multiple times a second (around 2-3). This is something that should be avoided. Telling the garbage collector to forcibly collect is not what was intended to be done, but is a fix that is viable but very slow. Telling the Garbage Collector to forcibly collect on all generations for each time the send buffer receives the data would be incredibly slower than letting it leak until the Garbage Collector automagically collects the garbage. The short-term fix is let it leak because the Garbage Collector will get rid of it when it gets bad, but the long-term fix really, really should be to locate the things that are leaking so much and to stop them at the source instead of working around the leak."}}