WoW locks with cosmos on logon - with SOME characters

[RadioActiveLamb]

With Cosmos loaded, "Release" or "Alpha", with some of my characters, WoW freezes as soon as the character enters the realm. Other characters, it's fine. I've tried this on another computer, same issue with the same characters. My sister-in-law has the exact same problem with her primary character. She hasn't run cosmos in months. My primary just recently started experiencing this problem. The ONLY way to play with these characters is to delete the interface folder and launch WoW*****. I've tried deleting the WDB folder and Interface, with a fresh Cosmos install, but no-go. it locks EVERY time. Anyone else having this, or know how to fix it?

[RadioActiveLamb]

Me and my sister-in-law are the only ones, huh?

[Thorarin]

I've had 2 lockups over the past few days, but they weren't after login.
I have no idea if they're Cosmos or other addon related yet.. so I think it would be presumptuous to assume this is the same problem.

[RadioActiveLamb]

No, not the same problem. We're seeing the world drawn, but then no HD activity. Others in the guild see me log-in, but if I leave it alone forever, they see me disconnect/log-out. To get out, 3-finger-solute, task manager, and end WoW. Chokes with my 60 Priest, works fine with all my other characters.

[morbid_o]

do you have 'keep interface directory clean' checked?

[RadioActiveLamb]

Yes, I sure do. Also, as I stated in my first message, I've tried deleting the WDB folder and Interface, with a fresh Cosmos install. Both "release" and "alpha" have the same result.

[morbid_o]

this error isn't new, but it's a weird one, and AFAIK, there's no band-aid solution for it. have you tried raising your script memory? I say this because it seems like it's always on a person's main character that this problem occurs, and it makes sense to me that your main might have more 'going on' (memory-wise) at any given time.

[RadioActiveLamb]

I got it figured out!

"Look Lock" is the culprit. I removed that from the addons, and POW! I can use Cosmos again!

[mugendai]

I can not give you any reason why LookLock could cause this. Unless you have some non Cosmos addon that somehow manages to make LookLock do it.. But I've never been able to identify such a situation.

However, I can tell you that Libram can cause this. I have identified a bug in Libram, that if your character has two or more of a quest with the same name, your game will lock up when you log in. Disabling Libram will fix this issue, and once you have only 1, of any quest in your list, you can safely re-enable Libram.

[RadioActiveLamb]

I can't explain it, but I narrowed it down to Look Lock. I added in groups of 10 addons until it choked. Down to the possible 10, I added a few at a time and narrowed it down to just one addon.

My wife's main is now afflicted with this lock-up disease on her computer/account.

[RadioActiveLamb]

Well, this started locking again, even with Look Lock disabled. This time, as was suggested, the culprit is Libram.

Easy work-around...

[morbid_o]

for one, it doesn't behave properly if you have 2 quests with the same name.

[NaVie]

Libram was the problem for me too. I still have it disabled.

[Teego]

I was having the same issue on my Main character.

Thanks, BUNCHES for pointing out LIBRAM as the culprit!

I disabled it and am logged in with no problem.

Once I was logged in and working, I was able to discover that I had picked up the Quest, "Unfinished Gordok Business", TWICE! Two instances of it were listed in my Quest log. I abandoned one, logged out, enabled Libram and I'm logged in and working, again.

[zappe]

"If you have any Interface layout issues:

1. Delete World of Warcraft\WTF\Account\<AccountName>\<PlayerName>\layout-cache.txt"

always works for me when i have a lookup on startup.

[morbid_o]

"If you have any Interface layout issues:

1. Delete World of Warcraft\WTF\Account\<AccountName>\<PlayerName>\layout-cache.txt"

always works for me when i have a lookup on startup.

if it's the libram bug, this wouldn't help at all.

[NaVie]

i had libram disabled for a long time because it was crashing my game, and then one day i decided to turn it back on cuz i wanted the party quests interface back, and it didn't crash anymore.

so I don't think the libram bug is a problem anymore.

was this bug ever fixed? it could be that i completed or removed the quest that it didnt like.

[PleegWat]

Libram doesn't like if you have 2 quests with the same name.