Not sure what the issue is but when I play in OSX my worlds are completely blank, except the player and particles such as rain. After about 30 sec the game crashes with one of two different messages: Internal Exception: io.netty.handler.timeout.ReadTimeoutException or Internal Exception: java.io.IOException: Operation timed out
OS: OSX 10.9.2
Java: 1.6.0_65
MC version: 14w08a (tried others including 1.7.4/5, same issue)
I noticed the following lines in the MC Dev Console:
[12:12:03 INFO]: Client> 2014-03-04 12:12:03.062 java[440:ef03] Persistent UI failed to open file file://localhost/Users/XXXXXX/Library/Saved%20Application%20State/com.apple.javajdk16.cmd.savedState/window_1.data: Permission denied (13)
[12:12:21 INFO]: Client> [12:12:21] [Client thread/INFO]: Stopping!
I know my java version is outdated, it always is using the ones through Apple. However, I have two MacBook Airs. Both running Mavericks and java 1.6.0_65. One works perfectly, while the other is described above. I'll update the one to the newest java and see if that helps.
Ok, updated to java 1.7.0_51. The MC launcher still reports using the older 1.6 version but under advanced settings I've directed the profile to use the 1.7 version. After doing this I tested MC and it ran fine....just quickly opened and closed MC to test it. Now it doesn't work again. Load a world, and it's blank. Getting the same messages as before.
This is hard to say then, because I do not know your machines configuration.
May need to verify/repair permissions using Disk Utility.
What is happening is obvious. "Your" profile does not have the required permission to access some files in the java installation after first run. As to why this may be occurring, I cannot say. But we can try repairing permissions with Disk Utility first after verifying. This will not cause harm as it simply ensures permissions of who should own what is correct.
This is why I will not update my OSX to Mavericks (10.9+) because it seems to have issues in this regard. For it tends to have permission issues.
I personally have 10.8.3 as nothing in .4 or .5 is of use to me so I did not update.
But yes, moving on.
To Verify and Repair permissions do these.
Applications > Utilities > DiskUtility
Select the Disk that your OS is installed on. Should be fairly obvious labeled.
On the First Aid tab, there is Verify Disk Permissions and Repair Disk Permissions.
You absolutely want to Verify first, if no issues found, leave it alone and we can try something else.
If errors are found, then proceed to Repair Disk permissions.
OS: OSX 10.9.2
Java: 1.6.0_65
MC version: 14w08a (tried others including 1.7.4/5, same issue)
I noticed the following lines in the MC Dev Console:
[12:12:03 INFO]: Client> 2014-03-04 12:12:03.062 java[440:ef03] Persistent UI failed to open file file://localhost/Users/XXXXXX/Library/Saved%20Application%20State/com.apple.javajdk16.cmd.savedState/window_1.data: Permission denied (13)
[12:12:21 INFO]: Client> [12:12:21] [Client thread/INFO]: Stopping!
http://javadl.sun.co...?BundleId=83377
This link is direct link to the OSX 10.7.3+ java download on Java Website.
May need to verify/repair permissions using Disk Utility.
What is happening is obvious. "Your" profile does not have the required permission to access some files in the java installation after first run. As to why this may be occurring, I cannot say. But we can try repairing permissions with Disk Utility first after verifying. This will not cause harm as it simply ensures permissions of who should own what is correct.
This is why I will not update my OSX to Mavericks (10.9+) because it seems to have issues in this regard. For it tends to have permission issues.
I personally have 10.8.3 as nothing in .4 or .5 is of use to me so I did not update.
But yes, moving on.
To Verify and Repair permissions do these.
Applications > Utilities > Disk Utility
Select the Disk that your OS is installed on. Should be fairly obvious labeled.
On the First Aid tab, there is Verify Disk Permissions and Repair Disk Permissions.
You absolutely want to Verify first, if no issues found, leave it alone and we can try something else.
If errors are found, then proceed to Repair Disk permissions.