Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

User profile for user: Nynshari
Nynshari Author
User level: Level 1
0 points

Javascript suddenly stopped working

Macbook Pro w/ Retina, Mid-2014, OS X Mavericks 10.9.5, Safari 7.1.3.

Safari security settings: enable Javascript checked, allow plug-ins checked, under manage website settings, Java set to allow.

Security software: Kaspersky* (recently removed - see below)


The day before yesterday I was watching a show on Hulu. The settings were set as above, along with the security software. Everything worked fine. When I was done, I closed Safari and shut down the computer. Neither I nor anyone else turned on or used the computer in any way until today. I turned it on, logged on, and opened Safari. When I went to Hulu, however, it said that Javascript was not being allowed to run. I checked my settings, and they were (and still are) set as listed above. I removed the Kaspersky software, to see if that was the problem. It then began to load Hulu, but froze in the middle of loading. It did this also with Netflix, Crunchyroll, and Vudu. I decided to check other, non-video sites. Some of those (such as Amazon and my local library website) either never loaded or loaded very slowly with errors (no graphics, etc), while others (such as my school website) loaded just fine.


It isn't the internet connection at my location. I have tried those sites with 2 other devices: an ethernet-connected desktop Windows computer (chrome) and a wireless connection through my iPhone (safari). Both display all sites just fine. So I know it's a problem with Safari on my Macbook.


Any help would be very much appreciated.

MacBook Pro (Retina, 15-inch, Mid 2014), OS X Mavericks (10.9.4)

Posted on Mar 5, 2015 8:50 AM

Reply
Question marked as Best reply
User profile for user: Linc Davis
Linc Davis
User level: Level 10
209,547 points

Posted on Mar 5, 2015 2:16 PM

Please read this whole message before doing anything.

This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.

The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.

Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you turn on the computer, and again when you log in.

Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.

Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.

The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.

Test while in safe mode. Same problem?

After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

View in context
6 replies
Question marked as Best reply
User profile for user: Linc Davis
Linc Davis
User level: Level 10
209,547 points

Mar 5, 2015 2:16 PM in response to Nynshari

Please read this whole message before doing anything.

This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.

The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.

Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you turn on the computer, and again when you log in.

Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.

Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.

The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.

Test while in safe mode. Same problem?

After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

Reply

Javascript suddenly stopped working

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.
Learn more Sign up