High Sierra freeze

I can confirm that 10.13.1 public beta 5 has no fix for this issue. Freezes are identically same with that release. So not much hopes from Apple to fix this in 10.13.1.

But so far it seems that this issue only affects those Mac devices with nVidia video card like my MBP 15" mid-2014

I think Apple knows about this. Atleast when I opened bug via bugreport.apple.com they closed it quite fast with message "Engineering has determined that your bug report (34985149) is a duplicate of 34714347 and will be closed."

What? Have you ever filed any bug on Apple's system? If you had, you would know its pointless and sometimes only serves you to get really ****** off. I have and none, I repeat, *none* have been fixed, and I'm talking 2011 bugs and similar ones. This particular bug took 5 years for them to say that it was solved in 10.8, saying that my bug was a duplicate of another bug. Well, guess what, it wasn't, because it's still quite alive. When I filed the bug, it was still old, it only took me years before finding patience to file the bug (for instance, just go to Apple support site or any other and try and find a link to the bugreport site. There's no; I never found, maybe I'm not patient enough), had to use Google search for that:-( ). If you're curious, go to your Calendar utility, use the Month View and try to insert an event on Oct, 22nd. What you get is an event that lasts 8 full days, no matter what you try. You simply have to avoid particular days of this week, since it varies as the years go by, must be related to a being a Sunday in that week or something like that. Let me correct myself in stating that none of my 6 bugs reported (8 different filings): one was solved, but by myself. Apple never helped, it was only thanks to this forum that I found the culprit. It was a magnet in a shorts pocket lid that I used quite often at home and cause the machine to suddenly go to sleep. A more recently filed bug got to a point in which the engineer asked me to run a command (beyond sysdiagnose and similar ones): "sudo ktrace artrace". It so happens that the command "ktrace" has been gone from macOS for almos 8 years. I tried to use dtruss in its place, but didn't know the proper switch stance to get the required behavior and then "artrace" was not to be found. When I asked the guy to get down on his feet and supply me with the proper command, I was simply directed to to this: "Please write a new bug for new request about the performance tools.". You've gotta be kidding, right? When I finally

get to talk to a technical guy, some dumb dude gets in the middle and destroys the long awaited conversation.

The bugs that I reported and were closed by a "duplicate of bug xyz" can't be followed to see what Apple is doing with them. When you expect a link to follow the proper bug, there's only plain text, you hover over the text and notice that there is no link behind. You are stubborn and try and click on the text, but to no avail. You go on steroids with you stubborness and try and search for the given bug number and the only result you get is your own bug, closed by the virtue of the previous "duplicate of xyz".

In short, don't waste your time. I repeat, none of my bugs have been seriously dealt with by any real technical person.

pldg wrote:

What? Have you ever filed any bug on Apple's system? If you had, you would know its pointless and sometimes only serves you to get really ****** off. I have and none, I repeat, *none* have been fixed, and I'm talking 2011 bugs and similar ones. This particular bug took 5 years for them to say that it was solved in 10.8, saying that my bug was a duplicate of another bug. Well, guess what, it wasn't, because it's still quite alive. When I filed the bug, it was still old, it only took me years before finding patience to file the bug (for instance, just go to Apple support site or any other and try and find a link to the bugreport site. There's no; I never found, maybe I'm not patient enough), had to use Google search for that:-( ). If you're curious, go to your Calendar utility, use the Month View and try to insert an event on Oct, 22nd. What you get is an event that lasts 8 full days, no matter what you try. You simply have to avoid particular days of this week, since it varies as the years go by, must be related to a being a Sunday in that week or something like that. Let me correct myself in stating that none of my 6 bugs reported (8 different filings): one was solved, but by myself. Apple never helped, it was only thanks to this forum that I found the culprit. It was a magnet in a shorts pocket lid that I used quite often at home and cause the machine to suddenly go to sleep. A more recently filed bug got to a point in which the engineer asked me to run a command (beyond sysdiagnose and similar ones): "sudo ktrace artrace". It so happens that the command "ktrace" has been gone from macOS for almos 8 years. I tried to use dtruss in its place, but didn't know the proper switch stance to get the required behavior and then "artrace" was not to be found. When I asked the guy to get down on his feet and supply me with the proper command, I was simply directed to to this: "Please write a new bug for new request about the performance tools.". You've gotta be kidding, right? When I finally

get to talk to a technical guy, some dumb dude gets in the middle and destroys the long awaited conversation.

The bugs that I reported and were closed by a "duplicate of bug xyz" can't be followed to see what Apple is doing with them. When you expect a link to follow the proper bug, there's only plain text, you hover over the text and notice that there is no link behind. You are stubborn and try and click on the text, but to no avail. You go on steroids with you stubborness and try and search for the given bug number and the only result you get is your own bug, closed by the virtue of the previous "duplicate of xyz".

In short, don't waste your time. I repeat, none of my bugs have been seriously dealt with by any real technical person.

i think you are confused

pldg wrote:

Please enlighten me. I'll all ears. Exactly where you think I'm confused? I'm only reporting my experience with bug report, and was looking in real time at my filed bugs window in bug report...

for starters, your hilarious claim about "october 22" is absolutely wrong and exclusive to your own personal situation

We are not good to argue upon technicalities. It is fine.

Every bug report get prioritized based on the number of systems affected and the severity. Yours received low priority because not many people reported such bug...

Never said that. Read my post again. I was just justifying why its a waste of time trying to file bugs at Apple's site. And, let me be clear, with hard facts. You can try the Calendar bug right now, for instance...

pldg wrote:

Never said that. Read my post again. I was just justifying why its a waste of time trying to file bugs at Apple's site. And, let me be clear, with hard facts. You can try the Calendar bug right now, for instance...

yes I tried your goofy calendar bug already. it is goofy and untrue

Well, I never had any return about this bug. You way its my own personal case. Just for my own benefit, you did try before saying that, right? In Month View? Well, if it's true, then Apple itself was wrong in 2016, since they wrote for this 2011 bug "The original report on this issue, Bug ID 10009710, is closed. It was fixed years ago, in 10.8.". So, did you actually tried? I'm not challenging you in any way, it's just that if you do confirm that the bug doens't happen to you, that is useful info for me and leads me to think that it's a localization problem. It has nothing to do with the current freeze bug, but at least I get some small step toward solving another bug, which Apple seems incapable of.

Guess I'm the unlucky ******* then. Tonight I learned that: i) One of my reported bugs only happens to me, though Apple thought it was a real bug; ii) Others aren't so unlucky and their bugs actually get fixed. Thanks, will do my own experiment with the Calendar bug, by doing some kind of backup, removing all files and test that condition again to be sure. Than file another bug or add an extra info since previous entries in my Calendar might be causing problems to the functioning of the utility.

Oh, BTW, not running Safari at all and using only Chrome has turned things a little bit better. It's now about 30 hours without a freeze (was having once or twice a day). Fingers crossed :-)

I have a freezing problem also. Today alone the computer froze up 6 times so far. Usually it happens after it goes to sleep, I have to restart. Now it has taken to doing it whenever. The last 4 times of the 6 I had to shut down

via the on/off button because the mouse was not on the screen and didn't come up. Sometimes I have to restart/shut down two times in a row for my computer to work properly. It is so annoying to have to constantly restart or shut down every hour or less. I have had issues with this computer since opening the box. The transfer of files from one computer to another froze up for 2 days, and I had to take the computer into an authorized service rep for them to transfer files. Not long after the files were transferred this happened. My computer worked fine until I installed HS (computer did not come with HS installed). These computers are so expensive. Some people, like myself, save up for over a very long time just to buy one and then this happens. I am so disappointed with Apple. I have an iPhone 8 plus and the darned thing is not working as it should either. I am not tech savvy at all and every time something happens I have to spend hours on the phone with Apple. Waste of my good time, and money.

I'm fairly confident my solution from earlier in this thread has worked permanently on my own machine.
I would advise the rest of you to at least try it.
I'm running 4 displays on a 2017MBP while doing audio/video production. There is a grand total of 36 devices connected to this mac right now via various interfaces and hubs.

It has been stable as **** for the past 2 weeks in High Sierra 10.13.0

Hi kallisti, I am not sure to which solution you are referring to but I followed some of the most promising “solutions“ on the community forum, upgrading the NVidia driver from NVidia directly (no luck there), stop using Safari (no luck either), reinstalls, ...

I am trying since I do believe that, regardless of believing it is a major macOS bug, since it does not affect every single user, there must be some way to replicate whatever the lucky ones have in their computers — I have in my office 4 other Macs (one twin system to mine and 3 very different machines) and mine is the only one affected.

Lately freezes are affecting mouse too.

Force restarts tend to affect Adobe CC installation, requiring it to fix Adobe Creative Cloud either by Re-installing it or, at least, re-signing in.

I'm attempting your solution to see what happens. Also, using only Chrome instead of Safari didn't help, so I'm also doing the opposite to speed things up, since it's getting impossible to do some real work :-(

My last resort is to attempt the beta version, even with one negative result post. After all, eventually Apple will have to fix it and using betas is a faster way of getting there.

pldg wrote:

I'm attempting your solution to see what happens. Also, using only Chrome instead of Safari didn't help, so I'm also doing the opposite to speed things up, since it's getting impossible to do some real work :-(

My last resort is to attempt the beta version, even with one negative result post. After all, eventually Apple will have to fix it and using betas is a faster way of getting there.

Let me know how it goes
it's been over 2 weeks since my last lock-up