WoW-Pro Guides

WoW-Pro Guides

3M Downloads

trouble with talador

deathmessinger opened this issue ยท 14 comments

commented

every time i go to load the guide for talador on my horde toon my game freezes :( it is only with this one guide the rest load just fine

commented

Oh, pooh. Since it happens with 6.1.0, I can't blame the ACE addons.

Sounds like we must be tickling a Blizzard Client PC problem.

I'll see if I can reproduce it on my PC laptop.

But first, I have to chop ice around an outlet and a water spigot so the "Ice Dam Man" can steam them away on my house.

commented

The guide hangs on my PC laptop, but not my Mac Desktop using a stock 6.1.1 and a copy of my config files from my Mac.

It has to be a Blizzard problem, but we must be tickling it.
Sigh. Let me investigate some more.

commented

OK. I need a bit more information.

  1. PC or Mac?
  2. What version of the addon are you using?
  3. What other addons do you have?
  4. When you say "freeze" please be more precise. Does the game instantly die? Do you get the funny cursor after awhile? Do you still get sounds? Does the game eventually exit or crash?
  5. Can you load the guide on another Horde toon, even if under-level?
  6. Can you try turning on debugging on the addon and seeing what is the last thing printed to the console?

FWIW, I loaded Talador on my own horde toon loads fine.

commented

Same problem. Something loops infinitely.

PC, occurs with 6.1.1 and 6.1.0 but not with previous versions, freezes immediately after "initializing guide" with debug on and doesn't return, confirmed with no other addons than WoW-Pro and TomTom and on two different characters.

Reverted to a previous version of just that guide (from commit 3883619) when it happened and did half the zone, still freezes when I switch to the latest.

commented

The problem occurs when when we call the AceEvent:SendMessage() function. It returns, but then the machinery goes off the deep end. I will see if I can reduce it to a test case that I can submit as a ticket.

PS: I need to run some more tests, but this should NOT be specific to the Talador guide. It should happen to any guide. Unless something really weird is going on.

commented

Tested every 85+ guide, Talador is the only one that does it. So I guess really weird is it.

commented

Hmm. In terms of size, 95_96_Emmaleah_Talador.lua is smaller than 92_94_Emmaleah_Gorgrond.lua or 92_94_Emmaleah_Gorgrond.lua, so that cant be it. But Talador is one of the largest, so I can't discount memory manager issues.

Now going to put debug messages in the ACE3 code.

It is at points like this that I wish I had my old MS Studio developers environment so I could attach to the process and see what was up. But it is a new laptop and I have a sucky DSL link that will take all weekend to download it. I'll bring it to work on Monday and do the downloads then if I cant figure it out by then.

commented

BTW, Do you also get a hang loading the Neutral Netherstorm guide?

Strangely I can load all guides including the Neutral Netherstorm from an Alliance toon.
Loading the same Netherstorm guide fails on Horde toons, but succeeds on Alliance toons!

This is very interesting.

commented

Every other levelling guide loads without a freeze. Also confirmed it happens on a fresh level 1 with no other addons loaded.

commented

I have reports of non-WoW-Pro users with similar symptoms. I am hoping that we can find another addon with the same problem and find that it uses a suspicious ACE library in common.

The fact that you can load Netherstorm and I can't makes it more likely to just be some third party library.
I have no evidence that any WoW-Pro code runs after the call-out to the ACE library.

commented

The freeze is triggered by the error in line 452

commented

Hmm, interesting. That would imply that on Windows, the LUA engine is running asynchronously from the logging output, as it shows that the parsing has not happened. Worse yet, that line should have been flagged by the new parser on the Mac.

commented

Threep, edit the file and make that line look like:

l Treasure of Ango'rosh|QID|34257|

I can now make the Mac client also fail at the same point, but it only happens 1 out of 5 tries. Looks like memory corruption.

commented

This should now be fixed in the GitHub version.