Use the older version, once 3.0 hits, update to current version.

I am also getting the same error, and noticed it has slowed down my gameplay a bit.

The latest version is triggering a popup window in wow saying that my addons are triggering massive amounts of errors and asks if I want to disable them.

If I disable RedRange this popup does not appear.
If I disable all other addons except RedRange it still appears and the lua errors still happen.

Tested on 4 different computers, two mac, two pc.

Errors:
RedRange.lua: 27: attempt to index local 'self' (a nil value)
RedRange.lua: 4: attempt to index local 'self' (a number value) - this one doesn't go away.

Good Addon!

Worked well in CWOW 2.4.3

Tested:

Dominos

Thanks Dridzt

Have you a prefered tool for cpu measuring? "OptionHouse" tells me, RedAlert has very high cpu usage. Then i tried PerformanceFu with simmilar results. Tuller means the many querys od RedRange could bring the profilers to wrong results. i hope he was right.

Tested:
dominos
bartender (who has a rangechecker inside)
redrange
rangerecolor
icehud,bigwigs and a bunch of other addons.

Profiler: OptionHouse and PerformanceFu

At the beginning, RedRange was on the thirth place in my cpu usage Score. But this has changed fastly. I dont know why, but RedRange took from seconds to seconds more cpu. Ok, i leaved my pc a while alone und checked after a half a hour again what happend. RedRange has reached his max level of cpu usage now and didn't increase.

here are the results:
http://www.abload.de/image.php?img=performancetmb.jpg

I can't find any unneeded loops
I changed the version I updated for WotLK abit (30000.2 which hasn't been uploaded yet)
to see if I could shave off some processing time.
What I did was basically cache the results of any api calls that will not change after the first time they're called
(getting textures for buttons, checking if a button has an action etc)
so that on subsequent checks it just does 1 local table lookup instead of calling an API function.

Addon went from 2kb memory to 12kb (still very small footprint) and cpu usage was cut by 10-15% in my tests.
(40-45 c/sec -> 35-40 c/sec)
That's a rather small gain and the actual number although a little lower and less "spiky" is still relatively high compared to other addons.

My point is though... this addon is already quite efficient for what it does.
There's no big improvement to be made with the current approach unless someone finds a totally different "red out" implementation.

Other addons that do the same that I checked are basically a copy of RedRange code,
so they have similar (and in most cases worst performance).
(Eg. RangeRecolor that's part of CombatGizmo)

I, too, had to stop using this addon because of the excessive (no exaggeration) CPU use. Hopefully, someone can take a look at the code and find unneeded loops or some other CPU hog?

I've posted a beta compatible version under optional files.
Update was trivial, should appear here shortly (if approved).

Iriel, are you planning to upgrade RedRange for WotLK? I really like using it.

I love this addon, makes being a Priest alot easier in alot of ways... unfortunatly, it just uses up too much CPU.

Does NOT work in WotLK Beta

I am using Dominos.

Nice addon but ive noticed its using hell of alot of my cpu time around 80% upwards

wonderful addon, just what i was looking for on my hunter

Just wanted to say: this mod is wonderful. Very small, very simple and very effective. I love having more obvious range feedback for my hunter toon.

Thanks, Iriel.