Experiment:
The hope is the system will crash just as it did when they were loaded previously as that's the evidence needed to hang them.
The problem may be SafariRestore which re-opens the tabs open the last time Safari was running. However, Safari will do that anyway if you select that option in its general preferences. Therefore, that one should be installed again even though it is known it is not necessary because it was running the last time so it is a possible perpetrator.
This article will be updated with the result. Yosemite 10.10.3 has been running for well over eight hours without those extensions and now they're back. We shall see.
Result:
Yosemite crashed within five minutes after reloading the extensions. Back in IBM mainframe sysfrog world, that's enough evidence for a hanging. We made the observation. We removed the potential cause and saw no problem for over eight hours. The extensions were reloaded and the system crashes within five minutes.
That's a hangin'. This is actually outstanding news for me as the bad news would be if it didn't crash. The extensions are now pulled so there is everyone reason to believe it will remain stable.
The news will be relayed to Apple tech support as there's a high probability many of the people running Safari also run these extensions, at a minimum they likely run AdBlock.
The workarounds for any of those extensions:
SafariRestore: it serves no purpose as Safari can perform the function without external software
AdBlock: avoid sites serving cancer cookies (i.e. low-rent sites with cheap advertising as all of them put cancerous tracker cookies into your browser). Either that or turn off cookies unless visiting a trusted site.
Translate: really not necessary as Google Translate can do it and the extension was just a shortcut
Status:
Nothing will be done just as before and this is to observe for stability. No more software can be added at this time but there's good reason for optimism I can continue after a period of observation to verify stability returns.
I'm really extremely happy at this result as this one doesn't throw another mystery in my face. Yep, this is enough evidence for a hangin'.
Updated Again After Multiple Crashes:
Happy might have overstated things as Yosemite 10.10.3 crashed three times in quick succession on restart. The status now is the extensions are uninstalled but the system crashed two more times after that. For the third start, I said I wanted no windows re-opened to prevent Safari from starting and the system now stays up.
It's not perfectly clear what happens but there's no question Safari is in the thick of it.
Note: this system is extra-virgin as there is zero software beyond the base Yosemite. Apple owns it but it's still not 100% clear where the fault lies but the extensions triggered it easily and I see the system has just crashed again. I'm using my friend's computer now and I'm very close to the point of abandoning this as there's no question Apple broke it and the system is close to useless. Apple has run three different types of hardware diagnostics and they see no problem.
It's looking like time to punt as this is just wasting my time with no significant accomplishment. If I wanted that, I'd go back into systems programming.
System Running in Safe Mode
No good idea of the next move. Time Machine has been shut down and the most recently added disk drive has been disconnected.
Other than Apple Yosemite 10.10.3, there's just nothing on this system.
The hope is the system will crash just as it did when they were loaded previously as that's the evidence needed to hang them.
The problem may be SafariRestore which re-opens the tabs open the last time Safari was running. However, Safari will do that anyway if you select that option in its general preferences. Therefore, that one should be installed again even though it is known it is not necessary because it was running the last time so it is a possible perpetrator.
This article will be updated with the result. Yosemite 10.10.3 has been running for well over eight hours without those extensions and now they're back. We shall see.
Result:
Yosemite crashed within five minutes after reloading the extensions. Back in IBM mainframe sysfrog world, that's enough evidence for a hanging. We made the observation. We removed the potential cause and saw no problem for over eight hours. The extensions were reloaded and the system crashes within five minutes.
That's a hangin'. This is actually outstanding news for me as the bad news would be if it didn't crash. The extensions are now pulled so there is everyone reason to believe it will remain stable.
The news will be relayed to Apple tech support as there's a high probability many of the people running Safari also run these extensions, at a minimum they likely run AdBlock.
The workarounds for any of those extensions:
SafariRestore: it serves no purpose as Safari can perform the function without external software
AdBlock: avoid sites serving cancer cookies (i.e. low-rent sites with cheap advertising as all of them put cancerous tracker cookies into your browser). Either that or turn off cookies unless visiting a trusted site.
Translate: really not necessary as Google Translate can do it and the extension was just a shortcut
Status:
Nothing will be done just as before and this is to observe for stability. No more software can be added at this time but there's good reason for optimism I can continue after a period of observation to verify stability returns.
I'm really extremely happy at this result as this one doesn't throw another mystery in my face. Yep, this is enough evidence for a hangin'.
Updated Again After Multiple Crashes:
Happy might have overstated things as Yosemite 10.10.3 crashed three times in quick succession on restart. The status now is the extensions are uninstalled but the system crashed two more times after that. For the third start, I said I wanted no windows re-opened to prevent Safari from starting and the system now stays up.
It's not perfectly clear what happens but there's no question Safari is in the thick of it.
Note: this system is extra-virgin as there is zero software beyond the base Yosemite. Apple owns it but it's still not 100% clear where the fault lies but the extensions triggered it easily and I see the system has just crashed again. I'm using my friend's computer now and I'm very close to the point of abandoning this as there's no question Apple broke it and the system is close to useless. Apple has run three different types of hardware diagnostics and they see no problem.
It's looking like time to punt as this is just wasting my time with no significant accomplishment. If I wanted that, I'd go back into systems programming.
System Running in Safe Mode
No good idea of the next move. Time Machine has been shut down and the most recently added disk drive has been disconnected.
Other than Apple Yosemite 10.10.3, there's just nothing on this system.
No comments:
Post a Comment