Hello.I have arrived at this forum in good time. I have been using OQ since the beginning. I have noticed that the MB usage for this addon climbs out of control as more raids or events are listed in the que. It rapidly starts from 3MB to over 8-9 MB very fast during high OQ pop times. This has of late prevented me from casting more than 1 spell during a 25 man raid without a 15-20 second lockup lag spike. Late in the wee hours of the low pop times (OQ Lisitngs) The memory usage is not as bad. The event of batlenet disconnects are rapidly increasing if I log from one toon to another, and must restart the game to reconnect to battlenet. It appears (and I mean appears) as though the memory usage during a raid consumes MB usage as though more players are actually in the raid when the OQ list is wacko scrolling in high usage times. I noticed ( I have several toons) the logging from one toon to the next...Oq retains connections and the list remains without a refresh and restart of the list. This spikes Bnet connections hard and seems to cause alot of bnet disconnects. Wehn Oq was first becomming popular the high volumes times require you bedg your raid leader to allow you to not kick you from the group untill you relog and unload addon and log back in. ( became standard practice with many of us in the same situation.) The last update however I try I cannot run while actually in a raid or lockup city. As usual Bliz will incorporate an ingame addon to squash OQ as it does with all the others that people have been using eventualy. In the meantime.... I have also tried to go dark to prevent the traffic problems and its not quite the fix. I would ask that a kill addon option completely ( that would releive memory) While still ingame and a refresh or restart list when relogging to a new toon be inserted into the addon. Once you are added to a set number of Ques to raid this would allow the system to be freed up and prevent the need to log out and kill addon. ......just my thoughts ..and hope all goes well...


Edit....
I have found that inside of a raid with OQ running..If you change a talent ..wow kills the addon due to error.....I am using this technique as an addon killer..