The macosxhints Forums - "Reserved Range Exhausted", what does it mean??

The macosxhints Forums (http://hintsforums.macworld.com/index.php)

- UNIX - General (http://hintsforums.macworld.com/forumdisplay.php?f=16)

- - "Reserved Range Exhausted", what does it mean?? (http://hintsforums.macworld.com/showthread.php?t=12357)

Ok. Interesting qquestion, but lets keep focused here...thanks..
So I have tried a number of other things, but none have worked:

1. Reset PRAM
2. Work with Cocoa apps only
3. Re-nstall the video card driver - ATI Raedon 9000 Pro..although the driver for this card is not supposed to be used if you have later than 10.2.2 (I have 10.2.6). I wonder...
4. Re-order the memory sticks (512,512,256).

I am beggining to think what some people have suggested; this might be a OS glitch..

ateles

Personally I think this is a non-issue. I always remember seeing some kind of complaint of the windowserver in the logs. Now I'm getting:

WindowServer[175]: orderWindow: Invalid other window
WindowServer[175]: CGXOrderWinsAndPanels: error ordering window

And in the past I have seen:

WindowServer[175]: CGXDisableUpdate: Updates disabled
by connection 0x15e77 for over 1.000000 seconds

If you're getting any crashes or strange behaviour I'm not sure it's the windowserver, seeing that others have it in their logs without il effects.

v

vonleigh,

These messages are OK and I get them at my PB all the time. But an excesive number of "Reserved range exhausted" messages, is a signal something is not right...

I think more and more that it has to do with the video card, since most people that have reported the problem have the same ATI card as I do..

Maybe ATI has not updated its drivers for OS 10.2.6??

FWIW, I get this message on an nVidia, and not on an ATI.

Quartz Extreme may be a little too extreme.

I don't have access to my logs right now, but it would be interesting to see if it's related.

I think vonliegh is right, the window buffer might be hitting a brick wall, does redraw look painfully slow and ragged when you get a plethora of these messages? My tuppence.

For what its worth, Codetek issued an update yesterday for Virtual Desktop. I haven't had it running for long, but thus far there haven't been any problems and OS X certainly didn't crash.

:)

I can produce the Reserved range exhausted console message by clicking and rolling over the menus in Camino.

Opening a new window in the Finder can also cause the messages.

I get these messages also in nearly every program. Every second or fourth click in the menu bar produces this error in console.

UPDATE:
I did a little testing on this. I had my display set to 1280x960. I switched it to 1152x960 and the messages disappeared! Tested for 5 minutes and decided to switch back. Tested for 5 minutes. No messages at all. Then I did a restart. For 10 minutes everything was fine but then I got 16 messages in 10 seconds. The next 20 minutes I got only 1 mesage.
So this seems to be related somehow.

I get these errors all the time as well. I thought it was because I modified my shared memory settings to run oracle. I guess not. I don't have an ms products on my machine so that can't be the reason. I have a G4 with dual 1.25GHZ processors and 1.2GB of RAM. Here are the results of these messages on my machine.

[username@osx /]$ uptime
7:20PM up 2 days, 19:29, 3 users, load averages: 0.00, 0.02, 0.00
[username@osx /]$ grep "Reserved range exhausted" /var/tmp/console.log | wc -l
771

As you can see, this is happening A LOT. I can't say a lot of apps crash or I have any problems. But this problem is a bit disconcerting....

J

oleaf: I also notice a decrease in the number of messages after changing the resolution, but only in the beggining. After a few hours of working on the machine, they were everywhere especially after launching new apps or saving documents...

JavaOS X: Interestingly the messages only appear in the newest Powermacs (specially dual). I repeated your commands in My Powerbook G4 (15'') and here are the results:

Code:

[plasmo:~] jorge% uptime

10:30PM  up 10 days,  1:46, 3 users, load averages: 0.27, 0.28, 0.32

[plasmo:~] jorge% grep "Reserved range exhausted" /var/tmp/console.log | wc -l

       0

Not a single one in my PB! Strange ahh? But what I have noticed in my Power Mac is that crashes have vanished, (maybe because of all the cache cleaning, renewal of preference files, etc..) although the number of "Reserved Range.." messages is quite high..Anyway..

ateles

That's interesting, so that begs the question, is anyone here having this problem with a single processor machine?

J

Quote:

Originally posted by JavaOSX
That's interesting, so that begs the question, is anyone here having this problem with a single processor machine?

Yes, I am.

Code:

% grep "Reserved range exhausted" /var/tmp/console.log | wc -l

      42

... and have done for some time.

Same here. Sometimes I get lots, sometimes I get very few.

Quote:

[null:~] yellow% uptime
9:22AM up 23:27, 2 users, load averages: 0.32, 0.54, 1.11
[null:~] yellow% grep "Reserved range exhausted" /var/tmp/console.log | wc -l
6

Quote:

[null:~] yellow% uptime
9:28AM up 23:33, 2 users, load averages: 1.44, 1.18, 1.20
[null:~] yellow% grep "Reserved range exhausted" /var/tmp/console.log | wc -l
20

Note, about 5 minutes later, 3x as many. This was reproducable only by opening 2 MS Office apps together.

After a frustrating couple of days where the 'reserved range exhausted' issue finally brought my machine to its knees (crashes, apps not opening ... and so on) I decided to do a clean install of the OS. On the assumption that 10.2.6 might be implicated I'm currently at 10.2.5 and haven't updated QT yet. However, one of the early things I reinstalled was Little Snitch and immediately started getting the 'reserved range exhausted' messages in my system log. So, of those of you who are experiencing this problem are there any of you who don't have Little Snitch installed?

Having said that, my machine hasn't been up long since I removed Little Snitch so I may well be wrong about this.

No little snitch here :(

Code:

$ grep "Reserved range exhausted" /var/tmp/console.log | wc -l

     125

Quote:

Originally posted by JavaOSX
No little snitch here :(

Code:

$ grep "Reserved range exhausted" /var/tmp/console.log | wc -l

     125

I spoke to soon. I removed Little Snitch and still have the damn things. Which, given that I've just gone through (or, more accurately am part way through) a complete, clean install, is a bit of a bugger.

However, it means we can probably stop trying to fix this as I suspect that it was a system bug introduced in 10.2.5 (or maybe earlier) :confused: :( :mad:

The only thing I turned up in my search for this was

Code:

$ grep -r "Reserved range exhausted" /System/Library/Frameworks/ApplicationServices.framework/Versions/Current/Frameworks/CoreGraphics.framework/

Binary file /System/Library/Frameworks/ApplicationServices.framework/Versions/Current/Frameworks/CoreGraphics.framework/CoreGraphics matches

Binary file /System/Library/Frameworks/ApplicationServices.framework/Versions/Current/Frameworks/CoreGraphics.framework/CoreGraphics_profile matches

Binary file /System/Library/Frameworks/ApplicationServices.framework/Versions/Current/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics matches

Binary file /System/Library/Frameworks/ApplicationServices.framework/Versions/Current/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics_profile matches

Binary file /System/Library/Frameworks/ApplicationServices.framework/Versions/Current/Frameworks/CoreGraphics.framework/Versions/Current/CoreGraphics matches

Binary file /System/Library/Frameworks/ApplicationServices.framework/Versions/Current/Frameworks/CoreGraphics.framework/Versions/Current/CoreGraphics_profile matches

But there isn't source available for this, that I know of. So it's dead end unless someone feels like reverse engineering it.

J

Quote:

Originally posted by JavaOSX
But there isn't source available for this, that I know of. So it's dead end unless someone feels like reverse engineering it.

Yep, I agree, though one final thing that might be worth reporting is that since I reinstalled my entire system I'm still getting a slew of these errors:

Code:

grep "Reserved range exhausted" /var/tmp/console.log | wc -l

      67

The above only three hours after a reboot.

But, I didn't reinstall any of the Unsanity haxies (or their Application Enhancer) and my system, despite all the reserved range errors, seems way more stable. So, for anyone still suffering with this problem it might be worth uninstalling any Unsanity products to see whether it makes any difference.

nVidia cards are part of the problem

To wind up this issue: I spoke to someone I know who works for the Apple Seed Programme and asked him if he knew anything about this problem and if it could cause any serious problems. This is what he had to say:

I just checked our bug database on this, and, in general, it could end up crashing applications, but usually wouldn't (programatically, it could happen by sending AppleEvents with references it shouldn't - that could happen with drag & drop/copying things into the pasteboard, etc). Reading through the engineering notes- they believe that NVidia graphics cards are 'burning up most of shared address space'. There are things developers can do to reduce the occurrences of this happening due to their applications. The good thing is that Panther changes some underlying core graphics routines which seems to alleviate this particular error (among others).

When I asked him if I could quote his message here and if he knew why this seemed to be seemed to be such a problem with recent versions of 10.2 he replied:

Sure- I'm not sure if it will actually help people to know that it's (probably) an nVidia specific problem, but certainly, you can give them hope that Apple has looked into it, and Panther should improve on this. Looking at the bugs, it looks like there are reports on it since 10.2, and not just recently- perhaps your activities have changed somewhat recently so you see it more? or maybe some specific applications are causing this to happen more frequently.

So, that’s that I guess, other than I might try and do a bit more troubleshooting to see exactly which apps throw up this error more than others (which I suspect may be a futile exercise). So it’s either wait for Panther in the hope it fixes this issue, or fork out for an equivalent card (e.g. the Radeon 9000). Panther will probably be the cheaper option so I think I’ll probably try and wait for that. Having said that it’s worth emphasising a part of the comment above: “the good thing is that Panther changes some underlying core graphics routines which seems to alleviate this particular error”. Note that the word used is “alleviate”, not “eradicate” (or it’s equivalent).

On a more general note, I think that Apple have had problems with the nVidia cards (and from the above it seems as though they still have). When I first got my machine I had problems with the 4MX and weird glitches on my monitor – this was later resolved by Apple as a problem with the 10.1 drivers for the card. There were also problems with the 10.1 driver for the 4Ti. I would have included a link to the Apple board discussions but they both seem to have been deleted.

<edit>
duh ... I've just read back through this thread and realised that at least some of the people experiencing this problem are using ATI cards. Hmmm ... I'll get back to the guy I know at Apple.
</edit>

I am using an ATI mach64 3DU card, I still get these errors on my log. I'm not sure if this is really a hardware specific issue as more of a software issue. Maybe it is a bug common to all their graphics drivers for both ATI and NVidia.

Anyone know if Apple distributes the code for their graphics drivers?