Well my system has frozen twice today...

sometimes it goes weeks without a freeze... and then only a few hours!!

:( :( :(

--Zed :cool:

I guess the obvious question would be what are you doing that's different? But I suspect that the answer is nothing - at least my experience of trying to troubleshoot these errors is that there seems to be no rhyme or reason to them or what impact they have on the system. I'm still waiting on my contact at Apple to get back to me as to whether there's any more information on this.

<edit/afterthought>

In an effort to monitor these errors I've written a Konfabulator widget that puts the total number of errors on the desktop. If anyone would like a copy, drop me a line.

Your right... nothing different...

the last few freezes all I've had running is:

Mulberry - mail client
Terminal
Fire - IM message client
iChatAV
Safari
iCal
AddressBook
Stickies
ICA client
ITV - TV card viewer..

nothing too exciting...

Cheers,
--Zed :cool:

What Unsanity stuff do you have loaded?

nothing...

I've stayed away from anything too doggy...

I think it might be memory related... I never shutdown my system and I never even logout..

I do monitor it using top but so far not seen anything that looks odd :-(

---Zed :cool:

Oh well, so much for that hunch. My own experience is that the errors do increase over time and do seem to occur more readily when you get down to relatively small amounts of free memory. Having said which, the number of errors and the amount of free memory are both time related and there's no real reason to suppose that one can cause the other.

I've just had a thought...

My G4 2x1Ghz Quicksilver which does freeze has been upgraded from 10.1..

Were as my G4 powerbook 12" was clean installed with 10.2 and does not freeze

Anyone else have the same, ie the freezing system is upgraded? I'm wondering if it could be an artifact from this upgrade route..

Cheers,
--Zed :cool:

My PowerMac which has a clean install of Jaguar, shows the errors all the time...Looking at some messages back, I think it is going to be graphics-card related (although I have an ATI Raedon, not NVIDIA, as suggested to be the culprit)...Well, lets wait for Panther..

ateles

Well, I think I finally found the problem with my crashes, and as some of you suggested it had nothing to do with the "Reserved Range Exhausted" message. I still get that a lot of them, but since I removed one of my 256 MB dimms the crashes have dissapear. General conclusion: The RRE messages do not seem to be of major concern and as some have pointed out there might be some problems with certain graphic cards in certain systems that might contribute to it, but they don't neccesarily bring the system down once every day...bad memory does!

thanks to everybody who contributed to the discussion.

ateles

I get them ALL THE TIME on my 2x1.25Ghz G4.

No pattern I've been able to find, and I'm not sure they really hurt anything.

Mike

I get them on a 2x142 with two monitors and a single processor laptop, but the former more frequently. They show up in 10.2.4 and 10.2.6 with clean installs and no 3rd party hardware.

I have been on to Apple support about it (****-hot, expensive extended support at that), but no luck yet. Getting a different support rep each time who begins by asking me to do quite simple things that a child of four months would already have done doesn't help. I would posit that with the impending release of 10.3, curing such problems in 10.2.x is low priority.

I would suspect that if the console is actually reporting them, the situation isn't as dangerous as if memory writes were stepping out of bounds and not being detected. I don't like it though.

They do seem to be related to memory reservations for new windows. Simple test: open Textedit and make 150 or so new windows. See how many Reserved Range Exhausted messages you get. Now, close all those windows. Not a one.

Me neither, I've currently been up for just under 12 hours and have 79 of them. Before I rebooted (with an uptime of five days - damn that kp) I had approaching 1500. Anything that generates that many errors, while obviously not immediately fatal, certainly can't be helping things tick along smoothly.

Well here is a definitive from Ars Technica:

http://arstechnica.infopop.net/OpenT...1&m=9670962145

So it seems that this is a warning rather than an error, as I suggested previously, and it's not a worry.

Still irritating though.

Thanks for that. And yes, it is irritating - I use Desktop Console to tail my system log and reading hundreds upon hundreds of these entries is really rather tedious. All we need now is for someone to patch the windowserver to stop it generating these errors ;)

Yes, it's very annoying, I grep it out:

Let's hope this thread dies now too : )

v

It might be better to use:
... that way you don't dump all the WindowServer messages. Not that any of them seem all that interesting ...

Well, the windowserver is whiny:

"orderWindow: Invalid other window" and also "error ordering window". After I while I just decided to ignore the whole process. It's never really given me an interesting or useful error message anyway.

Plus no point in setting such a large n if I keep the window open always, a screenful is enough.

v

I guess you're probably right - perhaps I'm just living in hope that one day it will say something interesting ;)

I was hoping that this might be fixed in 10.2.8, but no - 102 'reserved range exhausted' errors with an uptime of 2 hours and 42 mins. Oh well :(

It will take a major overhaul of the WindowServer to actually fix the error, but it could be glossed over by reducing its log level or hushing its output a bit.