Safari freezes inside a Screen Sharing (VNC) session

I have a Mac Mini that is connected to my TV and acts as my media server. I manage this machine via VNC (Screen Sharing).
If the TV is off (i.e. the Mini is running headless), Safari will freeze when rendering most webpages.
If the TV is on, Safari works as expected.
I don't really know when this started happening, but it's fairly recent (2011).
This also happens with Chrome as well, so I suspect this may be WebKit and hardware acceleration getting tripped up.
It's a fairly niche thing, but I suspect there are other folks out there who may be stumped by this issue.

Also, this doesn't appear to have anything to do with Flash either. I installed Click2Flash to doublecheck, and I still see the same behaviour.

Similar Messages

Remote Screen Sharing (VNC) from outside of my LAN

I often have to connect to my parents' Macs to help them out with various things. I commute between two cities and stay with them when I'm there.
(I set up a dynamic hostname with DynDNS to point to our router, which defaults to port 443, which on the home network is reserved for the QNAP NAS that's set up. I set the router up to be reachable at port 455 but I'm not sure if it is successfully sending IP address updates to DynDNS. I don't see a way to check if it is. DynDNS seems to require a paid account for that functionality and my routers log is also not very helpful. In short, I'm having trouble getting the whole dynamic DNS thing to work reliably with our router, which is otherwise a great little box: a Fritz!Box Fon WLAN 7390).
I use Jolly's Fast VNC (http://goo.gl/UmllQ) to connect to a personal server and that works wonderfully, but then there the details are taken care of for me by my provider and I just have to type in the details.
What I'd really love is something like Edovia's Screens (http://www.edovia.com/)... except for the Mac rather than the iPhone/iPad (though I do own an iPhone copy of it and it's wonderful).
We do share a MobileMe subscription in the family, but that's not very helpful here either.
So far, we've used iChat, Skype screen sharing and I often end up using TeamViewer because of its speed and near non-existant setup.
My goal is to find a way to connect to my parents' Macbooks even when they are not around so I can help them out with problems while they may not even be around. The key here is that I want to be able to control their screens without needing any action on their part.
Suggestions for the simplest possible way to do this are very welcome.

I didn't know TeamViewer could be set up to be accessible without a second user having to be around to give me the session ID and password. I wonder if it's worth looking into that if LogMeIn Free with its server always running is a perfectly acceptable solution? Any advantages to using TeamViewer's solution?
The free LogMeIn account does NOT allow file transfer. The free for personal use TeamViewer does.
LogMeIn server hides in the background, so it is less likely your parents will Quit LogMeIn.com, were as TeamViewer looks like just another app, so they might Quit from it to get it out of the way.
Of course if you need to transfer a file (or 2), you could use DropBox.com for that, and it is a very easy way to transfer files between systems. Or you could store the file on your MobileMe account in a public place, then via LogMeIn copy the file from your public space into your Parent's Mac(s). Or your could use LogMeIn to start TeamViewer, and then use TeamViewer to transfer the file.
Basically once you can start applications on your Parent's Mac(s), you can use any number of utilities for transferring data.
We do have MobileMe. I was under the impression that the way Back to my Mac works is that it will show you YOUR remote Macs in the Finder's sidebar. You know, ones that you're also logged in with YOUR MobileMe credentials. We all use our own, unique MobileMe accounts. Am I missing something?
Yes, all the Macs would need to use the same MobileMe account. Do you all really need separate accounts? Maybe a Family account.
I could deal with the port forwarding and DynDNS but I'll have to set that up to remotely administer my router and NAS, which is turning out to be quite the pain. So if I can simplify, I will. LogMeIn or TeamViewer will do the trick just fine.
Port forwarding is a once and done thing for your parent's router. It allows you to get to their Macs from outside their home. It should have nothing to do with remote admin, or your router and NAS. Also once you can Screen Share your parent's Mac, you can then use that Mac to talk from the inside to their router. Although one must be very careful about making router config changes as one "Oops" and you could loose your remote access, and have to visit Mom and Dad to get physical access
By the way, I've been using VNC/Screen Sharing and AFP file sharing over ssh tunnels in conjunction with port forwarding on the destination router for years. I do this, even though it is more work, because it was available long before most of the above services were available, and because it has a lot more flexibility once you know how to use it. Oh yea, I'm also a Unix software developer and spend a lot of time using ssh anyway

How can I set up a screen screen sharing VNC at a resolution higher than display?

I have a mid 2010 MacBook Pro 13in, and i have set up screen sharing to access over VNC. I want to view my mac on my 1920x1080 display hooked up to my PC. But when i do it is not full screen, it is the same resolution as my MBP. how can i run it at a higher resolution only over VNC?

As Cvid suggests, I create my "frames" in Photoshop. Not sure about all versions, but my PS has several Actions, just for frames, and I have made a few more, with a different "look."
I Save_As PSD, and just Import those as Footage (I do not need the capability to work with the individual Layers).
Good luck,
Hunt

Screen Sharing / vnc with OS X 10.5.6 fails

I can not get the Screen Sharing that comes with OS X 10.5.6 to work with any vnc client. The server is my laptop, an MBP 2.4 GHz Intel running OS X 10.5.6.
*I enable Screen Sharing by doing the following:*
1) +System Preferences > Sharing > Screen Sharing+ is checked
2) +System Preferences > Sharing > Screen Sharing > Computer Settings > Anyone may request permission to control screen+ is checked
3) +System Preferences > Sharing > Screen Sharing > Computer Settings > VNC viewers may control screen with password+ is checked and I've entered a password
4) I also have Remote Login enabled for SSH access, but no other services are enabled.
*I see two different behaviors depending on one of two clients that I try using:*
1) +Chicken of the VNC v2.0b4+ running on same machine- Always says "Connection Terminated / Authentication Failed" without ever asking for a password. Logs the following in system.log (dates, hostnames and pids removed):
Chicken of the VNC: Server reports Version RFB 003.889
Chicken of the VNC: Bogus RFB Protocol Version Number from AppleRemoteDesktop, switching to protocol 003.007
I believe that the information in system.log is OK, and is just warning me that Chicken of the VNC is working around Apple's strange protocol version.
2) +TightVNC 1.3.9 on Windows XP sp2+- Says "Security type requested", then asks for a password. I enter it, click OK and tightvnc simply waits endlessly.
*Other Notes:*
1) I have tried configuring and starting the server using kickstart from the command line as suggested at http://support.apple.com/kb/HT2370 (+sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/k ickstart -activate -configure -access -on -restart -agent -privs -all+)
2) I have tried unchecking +VNC viewers may control screen with password+, but in this case Chicken of the VNC says "Please configure Apple Remote Desktop to allow VNC Viewers to control the screen. Unknown authType 30,31,32" and TightVNC says "Server did not offer supported security type!"
3) If I disable the Screen Sharing feature that comes out of the box with OS X, I CAN install and successfully run the OSXVnc server available at http://sourceforge.net/projects/osxvnc/. In this case, both Chicken of the VNC and TightVNC are able to connect.
*So Apple's Screen Sharing does not work. Does anyone know what the problem is? Are there any log files I can look at, or is there another way I can debug this? I'm not impressed. :)*

Thanks for the suggestion. It was possible that one of these files had become corrupted, so I tried moving each of these files to another directory but unfortunately I'm still seeing the same behavior.
Here's what happens with each of these files individually after they're moved:
1) When I set the VNC password in the system prefs, com.apple.VNCSettings.txt gets re-created (with the same contents as the original unless I change the password, so that just looks like a hash of the password).
2) com.apple.RemoteManagement.plist also gets recreated when I change the system prefs. If I use "sudo plutil -convert xml1 com.apple.RemoteManagement.plist" I get the following:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>ARD_AllLocalUsers</key>
<true/>
<key>ARD_AllLocalUsersPrivs</key>
<integer>2</integer>
<key>ScreenSharingReqPermEnabled</key>
<true/>
<key>VNCLegacyConnectionsEnabled</key>
<true/>
</dict>
</plist>
3) For me, com.apple.RemoteDesktop.plist does not exist.
4) Interestingly, com.apple.ARDAgent.plist does not get created until I run "sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/k ickstart -activate -configure -access -on -restart -agent -privs -all". Its XML contents are as follows:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>AdminConnectInfoList</key>
<dict/>
<key>AgentLogLevel</key>
<integer>3</integer>
<key>ServerConnectInfoList</key>
<dict/>
<key>Version</key>
<real>3</real>
</dict>
</plist>
Looking at this, I tried setting ScreenSharingReqPermEnabled to false, but that didn't help. Then I increased AgentLogLevel to 100 and got a lot of output in system.log (12:28:45 is when I restart the server and 12:29:34 is when I try to connect):
Feb 24 12:28:45 ARDAgent [749]: ******ARDAgent Launched******
Feb 24 12:28:45 ARDAgent [749]: got a sessionDict, onConsoleRef is 0xa04cd400
Feb 24 12:28:45 ARDAgent [749]: grUserOnConsole is 1
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 122
Feb 24 12:28:45 ARDAgent [749]: LoadMenuExtra: Attempting to unload menu extra
Feb 24 12:28:45 ARDAgent [749]: PostNotificationForced: Going to send notifation value 9
Feb 24 12:28:45 ARDAgent [749]: UpdatePrefs: versionFlt : 0.000000 kCurrentPrefsVersion : 3.000000
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 44
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 22
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 100
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 94
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 96
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 18
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 106
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 74
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 130
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 60
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 45
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 65
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 66
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 105
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 115
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 38
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 12
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 61
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 20
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 62
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 39
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 30
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 101
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 53
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 103
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 107
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 109
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 135
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 41
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 110
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 111
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 28
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 36
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 48
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 59
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 57
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 116
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 58
Feb 24 12:28:45 ARDAgent [749]: InitAppUsageHandlers: Called gTrackingDays is set to 0
Feb 24 12:28:45 ARDAgent [749]: CheckRFBServerPIDFile: return 679
Feb 24 12:28:45 ARDAgent [749]: RemoteCommandListenerThread init communications
Feb 24 12:28:45 ARDAgent [749]: RFBServerStart - did not kill 679
Feb 24 12:28:45 ARDAgent [749]: DOCStartDOC: No serial number. Task Server not started.
Feb 24 12:28:45 ARDAgent [749]: DT_InitLocalProcessing: Loading existing tasks from disk.
Feb 24 12:28:45 ARDAgent [749]: DT_InitLocalProcessing: Found 0 tasks
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 158
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 117
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 118
Feb 24 12:28:45 ARDAgent [749]: AddHandler: Added handler for cmdCode 162
Feb 24 12:28:45 ARDAgent [749]: ARD Agent: RFB Server exited quickly after starting - probable failure.
Feb 24 12:28:45 ARDAgent [749]: PostNotificationForced: Going to send notifation value 6
Feb 24 12:28:45 ARDAgent [749]: PostNotificationForced: Setting lastNotification to value 6
Feb 24 12:28:45 ARDAgent [749]: ******ARDAgent Ready******
Feb 24 12:29:34 Chicken of the VNC[693]: Server reports Version RFB 003.889
Feb 24 12:29:34 Chicken of the VNC[693]: Bogus RFB Protocol Version Number from AppleRemoteDesktop, switching to protocol 003.007
Feb 24 12:29:36 ARDAgent [749]: PostNotificationForced: Going to send notifation value 1
Feb 24 12:29:36 ARDAgent [749]: PostNotificationForced: Got request for kCurrentStateNotification. Sending value 6
Interesting that it says "ARD Agent: RFB Server exited quickly after starting - probable failure." That doesn't sound too good.
I will try to watch fs_usage more closely to see what else gets modified and accessed, but I'm increasingly suspicious that there's simply a bug which is showing up under whatever specific conditions I have on my machine. Perhaps the included log info will trigger an idea for someone.

Lion broke screen sharing, VNC?

Lion is installed fine and dandy on my iMac. However, I cannot use Screen Sharing from my laptop (not upgraded... Yet) nor can I use VNC from my PC or iPad to connect to the iMac. Everything gets a "could not connect" error with no useful information.
I have Remote Administration turned on with thiMac and could use VNC just before the Lion upgrade went in.
Any pointers/suggestions?

etresoft wrote:
VNC is not a standard protocol.
But what IS truth?
Not easy to define!
We both have truths!
Are yours the same as mine?
What exactly do you mean by "standard" as it pertains here?
Standards exist and apply to those who agree to adhere to them.
The group of people who use a protocol commonly referred to as VNC agree on certain functionality, and means of operation.
Apple used to operate in accordance with the expectations of this group.
They no longer do.
So, you could (and more or less did) state accurately that Screen sharing isn't VNC.
Or that screen shareing with VNC no longer works.
The point of the OP was that something changed such that Object X no longer does Task Y.
That is true.
Any way you slice it, it's a net feature loss.

Any Better Screen Sharing VNC alternative ?

just stat to use Screen Sharing to control my other PCs at home ,
not sure is it some setting problem or what.
Every time Screen Sharing first start it will run fine, but after a while screen sharing will fail to refresh the remote computer screen at the mean time still having control the remote PC it just don't refresh the screen or don't refresh completely.
so is there any thing i can do to improve SS ? or is there any other VNC viewer for OSX , the only free viewer i find is Chicken of the VNC it had very limited function.
any suggestion is welcome
thx

Apple's screen sharing is the most compatible solution, though any VNC viewer should work. Most are rather buggy and Chicken of the VNC was the best that I came across. The best is "Apple Remote Desktop", but you have to purchase it. From my experiences the screen sharing is the best alternative to ARD.

Leopard Screen Sharing (VNC) Quality?

Before Leopard I used to use Vine VNC Server for accessing my Mac over the internet. Now that Leopard has its own VNC (Screen Sharing) server built in theres no need to use it.
Normally when I VNC'ed to my Mac over the internet using UltraVNC on Windows it would automatically select the best image compression/quality (eg only displaying 256 colors only etc) to make it much quicker over the internet.
But the new Leopard VNC server only seems to allow full quality screen sharing, which is painfully slow over the internet (esp as my macs running at 1600x1500!), selecting anything other than Auto in UltraVNC will instantly disconnect after entering my VNC password.
Does Leopard's VNC (Screen Sharing) support compression/image quality like Vine VNC? If so how do you enable it?
Thanks for any help!

Thats what I thought as well, the "Allow control" option in ARD admin prefs is off. When ARD admin is not launched VNC to the computer works fine. If ARD admin is opened I can no longer VNC to it. Its like the "Allow control" pref doesn't actually do anything & instead is forced on always

Connect from Windows through screen sharing (VNC) and get out of full screen mode

How do you get out of fullscreen mode?
I connect to a OS X Lion computer through a Windows computer (which actually also is remote).
I use TightVNC software on Windows to connect. It's the only VNC software I am able to connect to OS X Lion with. TightVNC is kind of weak otherwise in the way that it does not have features for OS X targets - like you can't send "command" key pushes, or even Ctrl pushes and other F2 etc keys just don't really work.
Which means I cannot exit full screened apps by way of Command-F or similar. Moving the mouse cursor to the top of the screen also does not pop down the menu (although on some occasions I have been able to do this, I'm not sure how and it's terribly hard to reproduce).
I'd need a on-screen way (like a button to click) to get out of full screen mode.
Any ideas???

Are you using TightVNC because you found it was the only VNC client that worked well with Mac OS X built-in VNC server? Or is there another reason?
Vine Server (aka OSXvnc - free to use the server)
<http://www.macupdate.com/info.php/id/11283/vine-server-%26-viewer>
plays nicer with 3rd party VNC clients, so that you could try any number of other WIndows VNC clients. Maybe one of those will do a better job of sending Command/Control/Option keys.
But if you do install Vine server make sure you turn off Mac OS X Screen Sharing (and/or Remote Managment) so that you do not conflict with port 5900. Or via Vine Server configs, tell Vine Server to use a different port number, such as 5901, then make sure you connect to the correct port from your Windows client.

Need help with screen sharing/VNC

I can't seem to get screen sharing to work. I got my dad an iMac this Christmas and thought I could help him learn it with screen sharing. Not going so well. I tried experimenting with a friend's Macbook and I was able to screen share when we were within wireless range via iChat and Bonjour. But when more remote, the "share screen" icon on iChat is grayed out. My friend tried setting up an AIM account (v 4.7 I think) and we still can't screen share.
So I tried the VNC option with my dad's computer. I went to Finder >Go >Connect to server >entered vnc://Dad's IP address and got the message that it couldn't be found.
All three of the computers in this message have screen sharing turned on, firewall set to accept anyone, and have 10.5.1. We all use DSL modems (from the phone company), connected wirelessly; and I'm the only one with a dot Mac account.

2 ideas
The DSL modems that are provided by my Telephone Company (Centurytel) are all Westell and Netopia routers. The phone company calls them modems, but they are actually routers with a built-in NAT firewall. This means you have to set up port forwarding for VNC to work. The TCP ports to forward are 5500,5800,5900. VNC doesn't use UDP.
If you are both using Leopard, then the free .mac account takes care of the port forwarding problem, and also finding the other party's IP number (the .mac id continues to work for iChat even after the 60 day trial). You both login to .mac, start the chat, and then request to share screens. It's working so well for me that as soon as the 400mb 1.5.2 update becomes available I will start moving my clients over to Leopard

Targeting Screen Sharing/VNC to Spaces?

Hi All,
Does anyone know if it's possible to target a "space" just for Screensharing/VNC? I've got a Mac Mini that is setup as a dedicated Media Server running Plex, but it still requires maintenance from time to time. Sadly, whenever I log in via VNC I just get whatever view that is outputting to the TV.
Any ideas? Thanks...

Did you find the solution?
I am just looking for the same...

Remote connection, screen sharing, etc question

I'd like to remotely connect to my desktop either from a PC or another mac that isn't on my local network. I have a domain name registers, and i'd like to use this domain (godaddy.com) and just be able to type afp/smb/ssh (depending on if I'm on a mac or pc) and hhtp://www.mydomian.com and instantly get to my computer to change downloads and get files from an external drive, my OSX main disk, etc. I have a MobileMe account to, if thats any help. if I cant use my domain and somehow point it to my dynamic IP, I can use dyndns.
thanks

how would I set this up? do I forward 5900 (is that the ssh port?) and 22 on my router? or after that type ssh www.mydomain.com:5900? I'm not sure how to enable the ssh capability. I have remote management, screen sharing, file sharing, remote login, and web sharing enabled in settings, do i need anything else enabled, which ports exactly should I enable?
Assuming you want to maintain secure connections over the internet, I would suggest configuring your home router to forward a random high numbered port to your target home system's port 22. Most home routers allow this, but how to do it varies from manufacture to manufacture. A Google Search will most likely find instructions for your model router.
So lets assume you choose internet port 12345 to forward. Making an connect to your home system from the outside world would looks something like:
ssh -p 12345 [email protected]
That gives you an interactive shell login to your system.
If you wish to tunnel a screen sharing VNC session you would use something like:
ssh -p 12345 -L 5901:localhost:5900 [email protected]
Then using your VNC client of choice you would connect to
localhost:5901
Your VNC client would then talk to local port 5901, ssh would send this to the remote system's port 5900 which is the default VNC server port.
Using ssh to tunnel other protocols is done in a similar way, only the ports used will be different. Since I have only personally tunneled screen sharing, I'm not going to try to explain how to tunnel other protocols.
NOTE: You can specify as many ssh -L options on the command line as you like. Also the SSHTunnel utility can help you setup ssh tunnels.

Screen Sharing freezing and high CPU usage

Hello all,
I use screen sharing to remote my mac mini as a media server connected to ma HD TV to play movies, music and surf.
Since I upgrade to mavericks on my macs (Macbook Pro Retina and my Mac Mini) I have some troubles with the screen sharing feature.
No problems with the login step, the connexion is fast, all permissions are OK (I saw there were a bug with some RDP release) but sometimes, when I use fullscreen software as VLC, Firefox, etc (not the native apple full screen feature, I just clic on the + at the top of the window), my sreen sharing freeze and I can't do or move anything on the remoted mac mini. I'm unable to close (or reduce) the screen sharing app too, it's totaly busy (But I can see the movie or the website on the 2 computer, there is no deconnection)... I have to kill the process through the monitoring activity.
During the freezing time, I try to use vnc light from my Iphone and I have no problem, I can move the mouse, reduce le VLC windows... As soon I reduce the VLC windows, the screen sharing works again. I also use the logitech TouchMouse to remote the mouse, everything work fine.
Here are a screen shot of the monitoring activity of the Mac running the screen sharing app, we can see that there is a very high CPU usage when I use VLC in fullscreen on my mac mini. The first is in normal mode. The second is in freeze mode. Screen Sharing is named "Partage d'écran".
Can someone help me to fix that, everything works fine with Mountain Lion.

I have a Macbook Pro 13.5" 2.8 GHz 4 core (2 real, 2 hyperthreaded) i7 machine running with 1920X1200 display, 3 virtual screens and VMWare adding a few virtual screens (full sized). I have another Macbook Pro 15" with 2.6 GHz Haswell 8 core (4 real, 4 hyperthreaded). I see the problem using Screen Sharing on the 15 inch (Retina screen) mode simulating 1920 X 1200 pixels using Screen Sharing to the 13.5" Macbook Pro.
When I get the ScreenSharing problem, I have identified it as related to the VMWare screen on the 13.5" Macbook Pro being shown through Screen Sharing on the Retina Screen. Before you conclude it is a VMWare problem, the computations are only on the Screen Sharing client side, not on the server side running VMWare. The mouse gets unusable through Screen Sharing. If I physically move the mouse on the 13.5" Macbook, no problem. If I switch virtual screens, the Screen Sharing goes to normal processing.
I see an appearance of a compute-bound thread on the Screen Sharing client. It takes 100% CPU on one thread, the machine as a whole is 12.5% busy (the performance monitor considers all 8 threads as equal when in fact, they are not).
A few more pieces of information. The VMWare client ends up having a lot of overlapping windows with a lot of changing graphics. My mouse runs into problems especially when it is overlaying a changing plot (Perfmon running in Windows 7, or updating email client). It does turn out that VMWare has a "native" VNC server built-in and I tried to connect to the virtual screen using the Screen Sharing Client on the machine with computing problem and voila!, no problem. I end up having a Screen Sharing Client running native running screen (supposed to be VNC, but I have not verified that) sharing protocol on a virtual screen that is NOT the VMWare virtual screen and a separate session using actual VNC protocol using the VMWare VNC server. It works perfectly fine.
If I may hazard a guess, I think I know what the bug is, or at least, what is the nature of the problem that I have. The rest of you may have a different bug. When I have difficulty, it is because I am on a window that suppresses the dock, both in remote virtual screen and on the local machine showing the screen. Two docks are suppressed, one remote, one local. Throw in overlapping windows with changing graphics in the overlapped windows and toss in a mouse on top of that. I think that the Screen Sharing is trying to refresh overlapping windows with mouse and going through the suppressed dock calculations and never converging on what the picture should be. The mouse ends up being the visible cue that shows the time frame for iterating the windows - flickers with a timeframe of greater than a second. That is far greater than the screen update time. It is totally compute bound with all the overlapping stuff that it is deconflicting. At least, that is what I think is going on.
Meanwhile, the VMWare VNC server appears to send out a single graphics context and causes the Screen Sharing client to converge to a picture. Note, the mouse appearance is very different when attaching to the VMWare VNC Server rather than the ScreenSharing native server. I see two mouse renderings, the virtual machine remote and a mouse rendering from my Screen Sharing client side. They are mostly in sync in position unless I move the mouse very quickly. If I use Screen Sharing client and server instead, I usually see only one mouse, the client side's mouse rendering.
I have a solution for my problem. It is similar to using a different VNC server/client pairing. I will use a VNC server for the systems giving me trouble that is not Screen Sharing Server exercising a probable bug in the Client (though, it could be a problem in the design of Screen Sharing itself).

Can I display EyeTV's live TV over HDMI-out and be able to see my desktop using screen-sharing on a headless mac-mini used as a media-box?

Hi,
I'm thinking of buying a new mac-mini to replace my current one which acts as an iTunes server and records TV programs using eyeTV. I connect using screen-sharing/VNC to be able to do stuff on it (like handbrake etc.)
I have eyeTV with a satelite receiver and I want to change the setup so that:
- the new mac-mini continues to work as an iTunes server (and handbrake workhorse)
- I can use the HDMI output (inc. audio) to show eyeTV's live TV full-screen app
- I can connect using screen-sharing/VNC to the mac-mini and see my normal desktop to be able to maintain it etc. but this is a headless display (no screen is connected to the display-port).
- recorded media I'd play through the appleTV2 still + rentals etc. unless anyone knows if eyeTV software can offer up iTunes content? I don't like the eyeTV recordings in general as it seems very slow to me for access when there are lots of recordings and wouldn't be available in other apleTVs in the house AFAIK.
The main benefit that this gives me is that I'd no longer need a seperate satelite box to watch live TV and can add more eyeTV hardware to get additional TV channels all through the same HUD on the TV for ease of access.
Does this seem possible in theory & practice (ie are there any gotcha's to consider?)
- can I force the HDMI output resolution to 1080i as I go via an amp to the TV and the appleTV2 drops to low-res in this configuration so I have had to find a workaround for that.
- does the mac-mini have IR input that can be programmed?
- Does eyeTV software remain stable for long periods?
- Does the HDMI out have any handshake issues that would need a reset of the display (somehow)?
thanks in advance for any thoughts/contributions
Lee

I think the easiest way to do this is to have the EyeTV app running in one user account and sent via HDMI to the TV, and use a separate user account for Screen Sharing. Both logins can be active at the same time and with Lion you can connect via screen sharing to which ever login you need.
With regards to the Mac video resolution changing, when it is not the current input on your AV receiver. This is 'normal', if the Mac sees no signal it drops down the a lower level. What you need is to buy a HDMI Detective Plus which tricks the Mac in to always seeing a signal and hence it will not drop down the resolution. See http://www.gefen.com/kvm/dproduct.jsp?prod_id=8005
The Mac mini does have an IR receiver. This can be used with the EyeTV app, iTunes, and similar. Yes I believe EyeTV would run for prolonged periods quite happily, it is has been around for a long time and had most of the rough edges polished off. However one issue you will have to deal with is that it does not automatically update its program guide data. For this you might have to write or modify an AppleScript. Elgato support or their user forums will be a lot of help.
You can set EyeTV to convert recordings to an iTunes (Apple TV) compatible format and then delete them from EyeTV.
The HDMI Detective should solve your handshaking problems.

Screen Sharing hangs after a few minutes idle

I've enabled Screen Sharing on my Mac and am connecting from a Windows machine. I've tried connecting with TigerVNC, TightVNC, and TurboVNC clients but after about 10 minutes of no activity on the screen hangs. I'm able to move the mouse pointer, but no screen updates are sent over to the client. Reconnecting works, but it's a nuisance to have to connect every ten minutes
Any help on how to debug this would be appreciated. I bought my machine a month ago and I have the latest updates installed. Both the Mac and the VNC client are on the same LAN switch.
Thanks.
- Amir

You could try the Vine Server (a different VNC server).
Vine Server (aka OSXvnc)
<http://www.versiontracker.com/dyn/moreinfo/macosx/16699>
Just make sure you either give the Vine Server a different port number (for example port 5901), or you turn off the Mac OS X Screen Sharing VNC server.

Screen Sharing not working locally but fine remotely

There is a lot to this, so I'll be as brief and direct as possible.
I've been using Screen Sharing to connect to a headless Mac mini for a while now (used as file and media server).
Today I updated some Brother printer and scanner drivers in the Mac mini and all as good.
I had just finished adjusting all the settings and getting my iMac to use the new shared printers when the mini made a strange "meeep" sound like an error (the error sound is something else) - and no more Screen Sharing - locally.
I used my iPhone and VNC app to connect to mini without problem (through a different wifi network), but my local iMac cannot Screen Share. File sharing and print sharing work just fine (well, a little slow now to connect initially). Seems liek a local network problem to be but I haven't been able to resolve it.
Tried Chicken of the VNC and it times out (also shows a "second" server of the same name with Host: "address resolve failed".
All connected though Time Capsule and wifi.
Ideas?

The iMac could not screen share to the Mac mini on the samee network/subnet. So I later tried to set up another iMac on a different network to connect via VNC/BTMM through the Internet (port 5900 is open on the router/WAP) and it connected fine.
I noticed that BTMM was having problems staying stable once I used it from the other iMac. So I looked into the network to see what might need changing. I had always been running with "double-NAT" without any problems before but thought this cold be contributing to the BTMM stability issue which might translate to the issue of being able to share files and printers but not VNC/screen sgaring on the same network. After fixing that and running through a few other minor adjustments (and MANY hours of troble-shooting) it is working just fine again.
So, I'm not sure if the double-NAT was the problem (had been working fine for a LOOOONG time) or if it was something else. I know you aren't "supposed" to run a double-NAT but the different networks were segregated and should not have caused any problems like I saw. I figure some change I made with the printer/scanner driver (sharing?) must have overtaxed the router....I was also getting conatcnt polling from my iMac looking for the Brother printer on mDNS which was causing a lot of exess traffic so I deleted all Broter communicatipon software just to be safe.
Anyway, I hope if anybody else has a similar problem (file/print sharing working but screen sharing/VNC not), they can look at their network to make sure they don't have double-NAT (common on DSL Internet connections, too!).

Safari freezes inside a Screen Sharing (VNC) session

Similar Messages

Maybe you are looking for