Just to throw my two cents in, I'm getting the same issue.
Seems to be on my first login. I also use Bagnon.
|
Greetings, guest! Welcome to Stormspire.net, your #1 resource for WoW and Diablo 3 Gold, Professions, and everything in between! Enjoy what the site offers? Consider Premium Membership if you wish to get the most out of the site. Premium Membership benefits include the acclaimed Goblineer's World of Warcraft Gold Guide, private forum access, a complimentary high-quality avatar, and much more! If this is your first visit, make sure to check out the Stormspire.net Survival Guide for a quick site orientation. You may also register to unlock all standard forum features, and to get rid of these lovely ads! We proudly host the Official forums for TradeSkillMaster, The Undermine Journal, and WoWuction. |
Just to throw my two cents in, I'm getting the same issue.
Seems to be on my first login. I also use Bagnon.
I've been experiencing the same issue. Yes, opening/closing bag first mitigates it. For those experiencing the problem, what OS are you using? Just wondering if it might be a Mac issue.
here is my console message:
[CODE]10/25/12 6:12:59 AM [0x0-0x2b02b].com.blizzard.worldofwarcraft[353] ================================================== =======10/25/12 6:12:59 AM World of Warcraft[353] *** __NSAutoreleaseNoPool(): Object 0x2659e960 of class NSCFData autoreleased with no pool in place - just leaking
10/25/12 6:12:59 AM [0x0-0x2b02b].com.blizzard.worldofwarcraft[353] Exception Raised!
10/25/12 6:12:59 AM [0x0-0x2b02b].com.blizzard.worldofwarcraft[353] App: /Applications/World of Warcraft/World of Warcraft.app
10/25/12 6:12:59 AM [0x0-0x2b02b].com.blizzard.worldofwarcraft[353] Exception: SIGTERM
10/25/12 6:12:59 AM [0x0-0x2b02b].com.blizzard.worldofwarcraft[353] Error Code: 0x85100086
10/25/12 6:12:59 AM [0x0-0x2b02b].com.blizzard.worldofwarcraft[353] Time: 2012-10-25 06.12.59 MST
10/25/12 6:12:59 AM [0x0-0x2b02b].com.blizzard.worldofwarcraft[353] Error: Terminated from com.apple.dock[146]
10/25/12 6:12:59 AM [0x0-0x2b02b].com.blizzard.worldofwarcraft[353] Crashed Thread: 0x00000000[/CODE
I'm sure this does not help, but I just wanted to doc it.
Last edited by Koko; October 25th, 2012 at 08:16 AM.
Ok, if i open TSM in a separate window, the crash does not happen, even with all modules on, and all bagnon modules on.
One thing I've noticed is that if you open the Ah with TSM attached, the first time, it will show the browse tab, the second time you open it, it will show the TSM tab.
Last edited by Koko; October 25th, 2012 at 08:34 AM.
OK, this is strange. Once I had TSM loaded in a sep window, doesn't matter which addon I have on. No crash. I have them all on. I reverted back to having TSM in the same window. No crash.
And now, when I open the AH, the default is not the browse tab, it is the TSM tab, even attached. I think it may be a TSM issue with that checkbox.
ETA I have never had TSM in a sep window until today using that checkbox.
ETA2: All my alts are fine too.
Last edited by Koko; October 25th, 2012 at 09:05 AM.
@Sapu94 - Used all my alt posters today without a hitch, whereas before I had to use the open/close bag trick everytime. I'm sure that having previously opened the TSM AH window in it's own window, you haven't seen the issue.
There is a checkbox in Bagnon for "Enable frame fading" which I had on before the issue, and had turned off after the issue with no results.
I can't test the issue anymore, as it has disappeared after I had TSM by default open in a new window.
Here's how I solve this problem:
Before opening the auction house window, make sure you've opened bagnon on that toon. Otherwise my game crashes. This my help yours!
This is really what I meant to write
Here's how I solve this problem:
Before opening the auction house window, make sure you've opened bagnon on that toon (as in, open your bags). I'm guessing the scripts for bagnon interfere with TSM in some way... This prevents my game from crashing. I also turned off all the auto open settings on bagnon. Hope this helps!
Just wanted to say I am also having this problem. Is there no way to get a crash log or something?
Cheers
add me to the list of four i agree you have to be able to replicate an issue to resolve it as i have worked industrial maintenance for years and run into ghost issues operators complain about but i can fix if i cant see it.