Sky induces WoW crash on zoning & login

[Bjond]

WoW now has a very high chance of crashing on login or zoning. I disabled modules one by one until it stopped crashing. Crashes stop when Sky is disabled. Crash occurs at initialization of the chat chanels -- immediately after displaying channels joined, WoW crashes.

Crash chance is about 99% zoning or logging into IF and a fair bit less for other zones.

--
This application has encountered a critical error:

ERROR #132 (0x85100084)
Program: E:\GAMES\WOW\WoW*****
Exception: 0xC0000005 (ACCESS_VIOLATION) at 001B:69646C45

The instruction at "0x69646C45" referenced memory at "0x69646C45".
The memory could not be "read".

--

I can cut&paste the rest (stack dump / etc.) but it's all application debug info and not XML debug info.

For a fix, I would suggest decoupling the Cosmos -> Sky dependency so that most of Cosmos' Addons will still work with Sky disabled, then try to issolate and fix the precise bug.

[Sinaloit]

When you disable Sky it disables alot of other things make sure that if all those are disabled but Sky is not that you still get the error. People did use Sky on the test server w/o crashing so it should work with the new patch. If after trying what i've suggested its still sky try updating to SkyLight and see if you still get the same problem.

Also as a note were you ever in an out of zone channel?

[daikko]

OK. After the patch today, my COSMOS is totally hosed. I disabled SKY and everything that requires it. Crashes still. Got on a bird and WoW crashed. COSMOS is totally useless to me now. What happened?

[Bjond]

It is absolutely Sky. Thanks for the suggestion of SkyLight, but honestly, I just want Sky gone permanently. It is incredibly buggy even when it's not crashing WoW.

Quick Fix for removing *just* Sky (permanently :):

1. Cosmos.toc: remove Sky from dependencies.
2. CosmostMaster.lua:378: comment out call to Sky.registerSlashCommand()
3. touch Interface/Addons/Cosmos.nopatch
4. Disable 'Sky' on the Addon management page

Cosmos now works fine. 'Course some slash command functionality might not be there, but all the ones I regularly use worked just fine.

--

BTW, the downside to this hack is that you will need to manually check for upgrades to the "Cosmos" module. This is tedious. Also, while all the slash commands *I* use worked fine, this doesn't mean that the ones you use will work or that other subtle things might not work right.

Basically, apply hack at your own risk. YMMV.

--

Uh, what's an "out of zone" channel? I log in, I crash. Rinse & repeat about 10-20 times or so with various things enabled and disabled (trying to issolate module) and finally it logs in. Discover that it always works with Sky disabled, but then I can't even configure anything else in Cosmos (need Cosmos module). Re-enable sky, log in (omg, it worked). Do a few things, zone out, zone back, crash again. Try to log in, crash. Log in, crash. Hack sky out. Voila! Perfect!

[Kellisra]

Ok, thx. That did the trick. The only thing im really gonna miss now is the /tloc command. Any way of making that work?

Edit: Coords still works on the map, just not the /tloc x,y command.

[Bjond]

If some slash commands don't work, that would be what I would assume is a natural consequence of using this hack. You'll need to either do a fair bit of work yourself to split Sky.registerSlashCommand() out of Sky and put it into Cosmos or wait (and hope) that the Cosmos team will do that work.

Basically, if a /command that you like is disabled by this, you're pretty much stuck doing without it until a better fix comes along.

[Kellisra]

Hehe, ill opt for the waiting then. Besides, since the map coords still work i'll still find my way around. Its just abit more cumbersone atm. Thx for the help again. Dunno what to do without cosmos.

[Sinaloit]

Try increassing the memory available at the AddOn screen.
http://www.cosmosui.org/forums/viewtopic.php?t=9967

[nomad_wanderer]

Nice try but no cigar, I have my memory set to zero, and still can't login with sky enabled.

[zebai]

I've just logged in a bunch of times testing various combos

Sky, Sea & Chronos; crash =yes

Sea & Chronos; crash =no

Sea alone; crash = no

Renable Sky(dependences Sea & Chronos); crash = yes


The crash is definetly located within the Sky module, the bug is in the cosmos release AND Sky Lite, as i have tried the above with both.

Since pretty much all of cosmos is labaled as sky required for little to no reason, i'm going to do the above and try to edit out the sky depencies. Once bug fixed its ez enough to patch back.

PS. Mem was set to 128 and no other addons loaded.

[Bjond]

Just a quick note: the above hack is not intended as a solution for everyone. It's to help DEVELOPERS issolate the bug and for those few users out there that are comfortable hacking the source code.

Please please don't send me messages asking for "how do I fix sky" help. If the above information doesn't help you, I'm sorry, but there's nothing more I can do. You'll need to wait for a real fix.

The above "fix" isn't really a fix, too -- it almost certainly breaks a bunch of /commands and perhaps other things, too. Also, if you use this method blindly, please don't pester the developers over broken /commands. You broke them yourself. :)

[some_guy86]

If the issue is sky related, and it seems to be, and it only occurs when people are within a major town such as orgimmar or iron forge, could the problem be related with the trade channel? it seems to be the only major difference between a major town and smaller ones and also be related with sky. Perhaps blizz is handling the channel differently.

[zebai]

While i experienced the insta crashing in orgimmar & IF, i still crashed quite frequently, about 10 times on my way to warsong, which included Durotar & The Barrens(no trade chans)

I lasted in warsong for about 5min, then i started the insta crash on logon again.


Sky is disabled atm, and i edited out all dependencies...Haven't crashed yet.

[HK]

3. touch Interface/Addons/Cosmos.nopatch

what do you mean by this?

[CW]

For whatever it's worth, I thought I would relate my experience with this latest Cosmos/Sky Crash bug after the patch.

I've not yet played enough as others have to notice crashes while changing zones. But the Ogrimmar/Ironforge thing is noticable.

However... for me it also seems to be based on server and not just population. Ogrimmar and Ironforge both on Hyjal didn't give me trouble. I first noticed this with a character in Menethil on Shadow Council followed by Ironforge on Shadow Council.

The interesting thing is that Ironforge on Hyjal does not give me trouble though both appeared more or less populated.

And...

What he means by "touch cosmos.nopatch" is create a file in the AddOns directory entitled "cosmos.nopatch".

CW

[Lecin]

I fixed this problem in two ways, one of which is more permanent but with unknown reprocussions.

Safe way:
In WTF/Account/<Your account>/SavedVariables.lua

Find the section: SkyChannels (which might look as follows):

SkyChannels = {
[1] = "general",
[2] = "trade",
[3] = "lookingforgroup",
[10] = "#Sky#",
[9] = "#Party#",
}

And empty it like:

SkyChannels = {
}

Downside, you might have to do this before logging in each time you start WoW.

More permanent fix:

EDIT: My more permanent fixed worked once then never again, temp fix as above.

[HK]

And...

What he means by "touch cosmos.nopatch" is create a file in the AddOns directory entitled "cosmos.nopatch".

CW

Thought thats what he ment, but just wanted to make sure it didn't have to have any info in the file.

Thanks

[Tridus]

Same problem here, crashed in Ironforge four times in a row before it finally let me in, using SkyLight.

I don't actually use Sky for anything, why oh why do so many things depend on it that don't use it? Its the single worst thing in Cosmos.

[HK]

I was able to make those changes, but If I try to enter the cosmos menu, the frames of the UI get stuck and I'm unable to remove them.
Some how my sound also died in WoW after making a few of these changes, but I was able to re-enable it in game after I removed cosmos.

Using Alpha 06-08-05

[Sinaloit]

If anyone has followed Bjonds directions please delete your cosmos folder and repatch to the alpha. The latest alpha has Sky as an optional depedancy for Cosmos command registration due to the problems currently being exposed by having Sky enabled.

[Tridus]

That fixed it, thanks Sinaloit!

[Nephyrin]

This is a bug in WoW, not sky. Sky, however, along with several other addons, do make this bug occur much more often.

http://www.curse-gaming.com/mod.php?addid=1415
Should help lessen, if not stop, the crashes while still allowing you to use sky.

Edit:
Technical details and caveats (From Above Link):
=============================
The cause of the new #132 crashes in patch 1.5.0 have been identified as a bug in WoW itself. It arises when the user or an AddOn requests a list of players on a chat channel with a large number of players in it.

This AddOn blocks channel list requests on the Sky channel, plus the zone channels General, Trade, LookingForGroup, LocalDefense. The upside is that #132 crashes due to channel listing should be eliminated as a result. The downside is that neither the user nor any AddOns will be able to list the players joined to the abovementioned channels. Custom chat channels are unaffacted, and you are able to list players in them fine. Any AddOn that relies on receiving player listing of chat channels might have its usefulness reduced.

This AddOn achieves its goal by hooking into the ListChannelByName() API function and preventing it running for the above channels.

[Karn]

Thanks for the info. I was afraid I had a memory malfunction. I hope this will be fixed quickly as cosmos clearly is unusable with this crashes.
I uninstalled it until a workable fix is made available.
Too bad since I enjoyed all the new functions. Oh well.