This site makes extensive use of JavaScript.
Please enable JavaScript in your browser.
Classic Theme
Thottbot Theme
Looter for 3.3 causing client lockups at login
Post Reply
Return to board index
Post by
Farmbuyer
Been having this problem since the uploader last night grabbed the latest addon version. Trying to log into any character while in Dalaran causes the game to lock up. I sit at a full-bar loading screen for a few minutes before eventually tabbing out and killing the game client ("this program is not responding").
Deleting both the common and per-character savedvariables files does not help.
Disabling only Wowhead Looter lets me login on any character with no trouble.
Enabling the looter and logging in outside of Dalaran has been working so far (on those toons which happened to be camped elsewhere).
Post by
Tertius
I have been having the same problem as well since the latest update for the WoWheadlooter. I just finished running the WoW repair tool to clear out my cache, WTF, interface folder, etc. and reinstalled WoW and I'm still encountering the problem as long as WoWhead looter is enabled. I've also noticed that this only happens on my main character - the only one at lvl 80 - and regardless of whether he's camped in Dalaran or an old world location outside any cities or towns. Other characters camped in Dalaran are not having this problem.
Edited to apologize for not adding my system specs:
Windows Vista Ultimate 32-bit
Intel Core2 Quad Q6600 2.40Ghz 3Gb RAM
Post by
Moklar
There is certainly something fishy going on with the addon.
I all of a sudden got the 132 wow-crash error doing different stuff, so I tried to disable my addons and then I didn't get it so it had to be an addon.
So I went to check all my many addons one by one so I could see which one caused it and it's the "wowhead looter" that causes this.
So for now I have to disable it :(
Post by
Gryphon
To add more data to find a solution; I am running about 110 addons in addition to the Looter on 3 computers, 2 on Win 7 64bit and 1 on Vista 32 bit, and haven't had any issue.
Post by
Moklar
Well it's hard for us mortals to say anything more than there is a problem with the addon.
.... and that it happened with the latest update.
Actually maybe this will be useful:
I can provoke the error by clicking the +/- (expand/collapse) buttons in the reputation pane on my char and wow will close down with the 132 error.
Post by
250218
This post was from a user who has deleted their account.
Post by
Tertius
Sorry in advance to post this as a reply instead of an edit, but I figured it would stand out more as opposed to possibly being skipped if were just another edit to my previous post.
I've narrowed it down to only happening when Questhelper and WoWhead Looter are enabled, even when they are the
only
two enabled. If I reload the UI using Addon Control Panel or by using the /reload command in the chatbox I will
always
get Error #132 "access violation in C:\Users\Public\Games\World of Warcraft\Wow.exe" (the default path for WoW in Vista). Using ACP I also noticed that when renabling WL by itself then reloading the UI, I get 10 to 15 seconds of latency that I do not see if WL is disabled. When QH is enabled (even by itself or at game start), the loading screen takes longer to go away and from comments I've seen on Curse and elsewhere, QH is known to be a process hog.
Is it possible that WL and QH are both attempting to access data at the same time as some new process introduced by 3.3? This might explain the Error #132 access violation if addons have data locked out when a game process is trying to access it. Or vice versa, if the game starts up, and the addons are locked out of accessing data, then the game sits waiting for them to finish, hence the eternal loading screen.
Post by
Auben
I have the same problem, I can't log into Dalaran (but other cities and non-Northrend zones are fine), when I have both Wowhead looter AND Pitbull 4.0 loading. Disabling the PVP icon module in Pitbull 4.0 works oddly enough, so it does seem like there's a mod clash somewhere there.
Post by
123325
This post was from a user who has deleted their account.
Post by
Farmbuyer
(OP here.)
I don't use QuestHelper or anything like that. I do know from previous experience that a common cause of error 132 (wow's generic "something broke" error number) is addons blowing up memory. I don't know if that's the case here or something completely unrelated.
Running the client just now downloaded new addon files. I wish I'd kept the old ones around for comparison. Anyhow, I'll be re-enabling the collector and trying again when I get online later, see what happens then.
Post by
Malgayne
I can confirm that the looter locks up the client on 3.3 even on a mac pro. Running a fresh install, with zero addons besides the looter, and a clean WTF still causes the client to crash at the end of the load bar.
I also noticed that I started getting this error when I launch the uploaded app.
2009.12.10 05:30:19 PM: The file “wowhead-logo-64.blp” does not exist.
This occurs even with a new download of 1.1.1 from the website.
This is definitely a problem with the fact that the looter hasn't updated yet, which is a known bug in the mac client which we're trying to get fixed but in order to do that we need to get in touch with the volunteer who coded it originally.
The other troubles are hard to trace, because some users are reporting no problems, some are reporting a conflict with xperl, some are reporting a conflict with PitBull, some are reporting an error with the looter alone. I'll definitely see what we can do.
Post by
Farmbuyer
Running the client just now downloaded new addon files. I wish I'd kept the old ones around for comparison. Anyhow, I'll be re-enabling the collector and trying again when I get online later, see what happens then.
Still hangs and crashes on the same 80 druid as before, but the 80 DK could log into Dalaran with no troubles. I'll be disabling the looter again for a while.
I haven't looked at the code, but if the looter is set up to hook into calls and register for events right away, maybe you could delay all of the hooks/registration for a while after login? Blizzard has a one-shot 15 second countdown for just such things (AutoCompleteInfoDelayer in FrameXML/AnimTimerFrame.xml), and I've taken advantage of that a couple times to hook into things that need to wait until initial data churn has settled down.
Post by
bkp57
I am having the same problem. I started getting lockups with 3.3, and random DC's... I eventually deleted my whole Interface and WTF and started rebuilding piece by piece. When I installed the wowhead client, it downloaded an update which put the looter mod in place... after that I could not log into any of my toons in Northrend. Toons in Azeroth cities seemed fine. I don't use QuestHelper or PitBull (but I do use a lot of other things :) )
bkp57
Post by
Farmbuyer
Was gone for a few days, came back today and ran the uploader and found that a new looter addon had been updated. So I re-enabled the addon and found:
1) No change to lowbies logging in outside of Northrend. Everything works fine.
2) No change to level 80 chars trying to log into Dalaran. Full loading bar and then nothing; killing the game client from the task manager warns me that "this task is no longer responding".
Looter is disabled again. :-(
Post by
SwiftHunter
Ok I too am having lock-ups with full bar on loading screen. I get no errors, just lock-up. The last update of wowhead looter caused the lockups I am having.
I disable looter till the problem is fixed.
Post by
mjrshake
I have the same issue here as well. I recently changed most of my UI mods over the past 2 days and decided to try the WL again. It still locks up with the full loading bar. Just disabling that mod will let me load.
Post by
Farmbuyer
WL_VERSION 30306 seems to have fixed the lockups during login for me, although I do see some debugging stuff printed at login now ("character data for ____ has been collected successfully") and while training up a lowbie alt, I get a Lua error:
: +Wowhead_Looter-30306\Wowhead_Looter.lua:626: Missing on/off parameter in SetTrainerServiceTypeFilter
+Wowhead_Looter-30306\Wowhead_Looter.lua:626: in function `?'
+Wowhead_Looter-30306\Wowhead_Looter.lua:1965: in function <Interface\AddOns\+Wowhead_Looter\Wowhead_Looter.lua:1963>
Going to leave it running for now so that at least icc25 stuff can be uploaded.
Post Reply
You are not logged in. Please
log in
to post a reply or
register
if you don't already have an account.
