Anyone who had problems with system crashing or black screen after closed lid in public beta 1 who has seen this solved in PB2?
As I noted above, Time Machine in PB2 is now running, I have seen it complete several backups so far, it seems to take a long time in "Cleaning Up" mode but that is not really a significant issue. I still would not use this Beta on any machine that is critical to anyone's use.Yahoo, the Apple has been fixed problem with backup
Yes, its been fixed for me in HS PB 2. YMMV
[doublepost=1499973402][/doublepost]
As I noted above, Time Machine in PB2 is now running, I have seen it complete several backups so far, it seems to take a long time in "Cleaning Up" mode but that is not really a significant issue. I still would not use this Beta on any machine that is critical to anyone's use.
The black screen problem is apparently not fixed.Yes, its been fixed for me in HS PB 2. YMMV
[doublepost=1499973402][/doublepost]
As I noted above, Time Machine in PB2 is now running, I have seen it complete several backups so far, it seems to take a long time in "Cleaning Up" mode but that is not really a significant issue. I still would not use this Beta on any machine that is critical to anyone's use.
This sounds like a widespread printing problem we ran into a few years ago. What helped was was these instructions (directly from Apple's support site), I hope this is different from the reset that you already performed.Next little issue is on printers. I cannot get the print utility to set a default printer or to update the last printer used to the last printer actually used. ...
... The most annoying one is the Safari one, even with no tabs open Safari uses 100% CPU and open Safari results in a spindump so there goes another 100-200% cpu usage ...
same result, high cpu usage, empty new tabs - already reported that more then a week ago
The software fixes for Beta testing is always gradually addressed. First stage: It takes a lot of time to sort through all the reports from the Public Beta testers plus the internal testers (employees), to figure out what is important, this is essentially a Triage Stage, then there is an analysis of the estimated time it takes to fix each bug. Management then takes these (and possibly other) factors into account they apply a healthy dose of Black Magic™️ and then they send the software engineers a prioritized list of the bugs that are allowed to fix, the order in which to fix them and often how much time they get to fix them. Then those fixes have too be tested internally, very quickly, by executing remade test scripts. If the fix passes through the test script without glitches then its added to the next candidate for a Beta update. This system is not perfect but is essentially how all the companies in Silicon Valley do it. Of course at some point a manager feels that there are enough fixes completed and they instruct the engineer in charge to release another Beta. The engineers continue working on their priority list while we (and several employees) perfume testing on the Public Beta. The glitches that we (and tear employees) find are then routed through the triage system, the manager merges the new reports with the old reports, re-prioritozes everything and then the engineers receive an updated priority list. This usually makes the engineers lose a little bit of their hair, if nothing else, because often (too often) the bugs they are working on lose priority and they have to stop all their work and switch to fixing a completely different bug. Its an exhausting process that I'm glad I'm not doing any more, but hopefully this sheds a little light on why its so hard (impossible) to get all the bug fixes out immediately and why we often see on thing fixed but not several others. There is also the issue of "dependencies", they can't fix one thing without breaking another, so more time has to be added to fix all the dependencies. Sometimes a piece of software that was suppose too be in the OS did not make it on time, but another piece was added that depends on the first piece, and of course it breaks. This nearly impossible complexity is nearly enough to make an engineer go crazy. Give it time, send it well thought out Beta reports (with screenshots and details of what you were doing which apps were open, and how to trigger the bug to repeat itself) and keep your fingers crossed that your bugs get fixed sooner rather than later.Perhaps this is being gradually addressed? ...
The black screen problem is apparently not fixed.
I've had similar problems. I have found that the High Sierra version of Safari Technology Preview works much better than the regular version of Safari.I'm seeing the 100% CPU usage issue but it doesn't happen all the time. I can surf for quite a while ad it behaves normally (and seems noticeably faster than Safari 10) but once its triggered it will use over 100% CPU and stay that way unless I quit Safari.
I haven't seen the tab issue at all.
I've had similar problems. I have found that the High Sierra version of Safari Technology Preview works much better than the regular version of Safari.
Reinstall beta 2... I had the same issue, tried iTunes12.6.1 after removing iTunes with AppCleaner only the reinstall of beta 2 helpedAnyone having trouble getting their iDevices to show up in iTunes? My iPhone shows up in System Information but never shows up in iTunes.
Switching to the Safari Technology Preview, as suggested by @tedson, above, cured the excess CPU and heat problems for me.I am running High Sierra on my 2017 MBP with TB. My laptop gets very hot with very common tasks. Safari uses a lot of CPU power.
Switching to the Safari Technology Preview, as suggested by @tedson, above, cured the excess CPU and heat problems for me.
Thanks. Issues with CPU usage are indeed solved with Safari Technology Preview. Don't like the purple logo though...