REMOTE DESKTOP ON MAC BLACK SCREEN WINDOWS

If it doesn't drain completely, it will result in a corrupt TLS stream.

If you do that, you'll see a bunch of text that shows when it does an SSL_Write, and when it actually sends data on the socket, as well as when it buffers and drains.īefore the fix, when I sent the initial large jpeg, it sent a partial TLS frame, then it deleted the buffer instead of draining it completely, and sent the next TLS frame, which ended up corrupting the TLS packet, causing the browser to disconnect.Īfter the fix, you should see whenever it is forced to buffer the data, you should see it drain it completely (may take a couple sends), before it sends any new data. If you define that, then run the agent in console mode. If you want to look at some of the verbose debug messages I added, add the following to the flags in the makefile (you can just insert it next to the MAXJPEGBUF Side note: since your previous fix was to remove the compression settings, I'm wondering if that was even more optimal, yet faster, and removing it was just enough to slow your test machine down to reach these same types of limits.ĮDIT: The usleep(100) call, when placed only after the util_crc call on line 257, seems to have the effect of making it work better without running every single time the crc function is run, but still a pretty slow experience.Īnd just to add, when I set -DJPEGMAXBUF=0, before my fixes, that worked correctly 0% of the time on my Catalina system, but after the fixes, it seemed to work 100% of the time. But I'll leave that until after the primary issue is discovered. Supplementary comment that I'll note during this experiment: Mouse movement worked fine, and fairly instantaneously, however clicking, double clicking, dragging, etc. Not sure if that jogs anything in your memory (as you obviously have more familiarity with the inner-workings here than I do) but it seems like it would be failing due to being too fast! The other percentage of the time, Remote Desktop works! Seeing as how I only added logging calls and didn't modify code, I tried a few variations of usleep with the values 10, 20, 100, and 1000 placed immediately before the return of the util_crc function.Īt 10 usec, the Remote Desktop still flickers and disappears ~95% of the timeĪt 20 usec, the Remote Desktop still flickers and disappears ~90% of the timeĪt 100 usec, the Remote Desktop still flickers and disappears <0.5% of the time, and is pretty darn slow.Īt 1000 usec, the Remote Desktop still flickers and disappears ~0% of the time, but is unbearably slow. Still pretty quick in C, but slower than optimal. Now, the logging function I made opens a file, writes to it, then closes it. All of a sudden, I could see my screen via an internet connected server. It wasn't until I introduced a logging call within the util_crc's for loop. I wanted to start trying to track down the issue, so I started by adding a simple logging function to output to a text file, which I added in various spots around mac_tile.c.

REMOTE DESKTOP ON MAC BLACK SCREEN WINDOWS

A few times the meshagent never came back and needed to be manually started again, but could not define a definitive pattern where I could replicate it successfully in all cases.ĭo you recommend, and if so, what is the best way to enable a helpful debug on the agent for some additional data? Unlike the Windows agent, I don't see a log entry every time a crash occurs. I also noticed that the PID of the meshagent process changes rapidly during this time, which I believe means it is crashing. UncaughtException1: Error: timers.onElapsed() callback handler on 'sendNetworkUpdate()' => TypeError: cannot read property 'split' of undefinedĮstablishing IPC-x-Connection to LoginWindow for KVM UncaughtException1: Error: => EventEmitter.emit(): Event dispatch for 'Command' on 'MeshAgent' threw an exception: TypeError: undefined not callable (property 'write' of ) in method 'handleServerCommand()'

Remote desktop on mac black screen