Not signed in (Sign In)

Support::Auctioneer: EnhTooltip 3.6.1 Crashes Wow

Bottom of Page

1 to 10 of 10

  1.  
  1.  
    I just downloaded and installed the 3.6.1 Auctioneer pack. When I went to the mailbox and moused over any items in the mailbox, the WoW client crashed.

    I disabled all addons except for EnhTooltip and Stubby and attempted to pinpoint the issue. It is indeed whenever I try to mouse over any item that may be in the inbox of my ingame mail. Blizzard just added recently the ability to get a tooltip when you mouse over the mails that include items. Other tooltips do not produce the crash.

    Is anyone else seeing this or should I continue QA by trying to update my drivers or maybe run Memtestx86?

    Edit: I've run the latest available version (3.4.2) from curse-gaming and it does not seem to have this problem.
  2.  
    i would first redownload auctioneer, in case something got corrupted.

    then i would wait a few hours. there is sometimes odd behavior in the few hours after a server reboot, although i've never heard it being a problem in the mailbox.
  3.  
    Define crash. There is one type of crash that results in an error message and the game quitting abruptly. There is another type of crash that all it does is boot you off the server with the "Disconnected from Server" message. Which one is it?
  4.  
    It's an access violation in wow.exe. The normal Windows XP access violation dialog shows as does Blizzard's memory dump dialog to report the error back to them.

    Text of message as follows:
    -------------------------------------------
    This application has encountered a critical error.

    ERROR #132 (0x85100084) Fatal Exception
    Program: C:\program files\world of warcraft\wow.exe
    Exception: 0xC0000005 (ACCESS_VIOLATION) at 001B:0048D62E

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

    Press OK to terminate the application.
    --------------------------------------------

    So yeah, it's an access violation and wow.exe terminates.

    I've tried to download the other distributables from you guys and all of them (the ZIP, TAR, and EXE) all exhibit the same behavior.

    Test process:

    Send yourself something in wow mail with an item attached. (In my case it was an iteam listed on the AH which had expired.)
    Exit Wow.
    Delete Interface\AddOns folder.
    Download 3.6.1 package.
    Install Auctioneer Pack.
    Run Wow
    Disable Auctioneer, Enchantrix, Informant, and Beancounter leaving only Stubby and EnhTooltip loaded.
    Go to the nearest mailbox.
    Mouse over item sent in the first step.
    Access Violate.

    I've set the maximum script memory usage at 64, 128, 256, and 0 (unlimited). I still see the problem at any memory level.

    Let me know if you need more information. I'm open to suggestions you guys want me to try.

    UNRELATED ISSUE:
    I'm also seeing another Access Violation when I'm trying to scan the Terenas Alliance AH. I've narrowed that one down to when I scan armor. I've done all the above steps (removing the addon folder). I blew away my SavedVariables\Auctioneer.lua because I thought maybe something got corrupted in the data file that was causing the crash, but it still acess violates when I have new or no data. It's only when I try to scan armor. Only armor.

    At this point all I want is someone else out there to say they're seeing the same behavior because debuging issues that happen on one machine and only on that machine is difficult to say the least.
  5.  
    in the past i have heard the devs say that it is impossible for an addon to cause a wow access violation such as the one you describe. all addons are run in a sandbox, and should not be able to hard crash the wow program.

    you may wish to wait for a dev's answer, but imo it's more likely you have some corruption in your base wow files than with an addon. as proof, i submit that many of us are running the 3.6.1 version with no such tooltip crash problems.

    i might suggest reinstalling the game.
  6.  
    Yes, that is what I was afraid to hear. I might just go ahead and blow away the entire machine and wipe the partition if nobody else has seen this which I fear is a likely event.
  7.  
    if you do go that route, please remember to backup your data first. no sense in losing all your historical data!
    • CommentAuthorblahblah
    • CommentTimeAug 20th 2006
     
    ERROR #132 is not related to the addon at all, it probably has to do with a corrupted install or corrupted RAM. You can get memtest86 and run it for a few hours to rule out memory errors, and I think Repair.exe will fix any issues with a faulty install. YMMV

    My experience with ERROR #132 was that my laptop had clogged vents and was overheating, which caused random crashes. Your problem seems to be related to a certain texture or memory address since you can reproduce it.
    • CommentAuthorblahblah
    • CommentTimeAug 20th 2006
     
    Just reading your update, if only armor will crash your game, try deleting the WDB folder, it stores texture cache and can sometimes be screwy.
    • CommentAuthorsham
    • CommentTimeOct 11th 2006
     
    My wife is having this exact same problem, we narrowed it down to enhanced tooltip and informant. It happens when she mouses over any item in the mailbox. She can turn the two tools off and no problems.

    Deleting the WDB folder worked. Thanks blah :)

1 to 10 of 10

  1.  
World of Warcraft™ and Blizzard Entertainment™ are trademarks or registered trademarks of Blizzard Entertainment, Inc. in the U.S. and/or other countries.