Same thing happening to me here.
Problem persist even after multiple resets.
Definitely a Daylights savings time bug.
Problem persist even after multiple resets.
Definitely a Daylights savings time bug.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
systemUIserver and High CPU in Snow Leopard - Help!
- Thread starter nope7308
- Start date
- Sort by reaction score
Seriously, people
Seriously, people, is it really a big deal? I mean, a bump up on CPU one hour every YEAR, at midnight. Apparently, the system was just confused since it had gone through the same hour over again. Seems like the end of the world in this forum.
Seriously, people, is it really a big deal? I mean, a bump up on CPU one hour every YEAR, at midnight. Apparently, the system was just confused since it had gone through the same hour over again. Seems like the end of the world in this forum.
Dybbuk
macrumors 6502a
when a computer gets confused by its own clock on "the world's most advanced operating system" to the point of running the cpu past 100% and overheating, yes it's kind of a big deal
creator2456
macrumors 68000
I know it's not that hot, but without ramping the fans up I was getting to mid 80's. Thats a whole lot hotter than the normal 55ish I have ran at for 3.5 years.
I just did a clean instal of SL and the problem was still there. Next thing I am trying is rebuilding my entire spotlight index as that was acting strange.
doug in albq
Suspended
You have something else specific to your machine going on here. Your issues seem to not have anything to do with the "DST bug" that happened last night.
gr8tfly
macrumors 603
It might not have even been noticeable, except for possibly increased fan speed. Our MBA was running during the "witching hour", but I didn't notice any lack of responsiveness, even accessing it through screen sharing.
I had this problem and all I had to do to solve it was to disable the iStat Pro widget... I hope your problem is something as simple as that. 😱
creator2456
macrumors 68000
After a new install and reindexing Spotlight, it seems I have solved the problem. Not sure what was going on there, or why it decided to pop up when it did.
Thanks to those who helped me get through it.
Thanks to those who helped me get through it.
doug in albq
Suspended
glad your personal issues went away. Your postings in this thread are borderline "thread-hijacking" IMHO.
____________________________________________________
I wonder if Apple will make a statement about this funny DST bug that affected a huge group of computers last night?
I was using my computer throughout the night last night - did not encounter any problems, slow-downs, or anything else unusual...
doug in albq
Suspended
I guess Apple got to sneak this OS bug in "under the radar" as no tech news outlets touched this story today, at all.
I am a bit surprised that an Anti apple tech site like the Enquirer did not jump on this glitchsimply to jab Apple a bit.
I am a bit surprised that an Anti apple tech site like the Enquirer did not jump on this glitchsimply to jab Apple a bit.
I guess all the tech news outlets had the wisdom to see that this "bug" would not be fire and brimstone coming down from the skies…rivers and seas boiling…forty years of darkness…earthquakes, volcanoes…the dead rising from the grave…human sacrifice, dogs and cats living together...mass hysteria!
So much for big news on Monday…
So much for big news on Monday…
at least a clue that seems to work
I just turned off "set date and time automatically" and set the clock manually to 2 am next day. The CPU suddenly stopped spiking! What a CPU hurry for nothing? We are just entering DST in Brazil tonight
I just turned off "set date and time automatically" and set the clock manually to 2 am next day. The CPU suddenly stopped spiking! What a CPU hurry for nothing? We are just entering DST in Brazil tonight