Hey,

I get a WoW crash when leaving a vehicle. It doesn't happen all the time, but nevertheless is very very annoying (and even prevents finishing certain quests. I'm looking at you, Chen's brewery story!).

I'm pretty sure this issue is not per se your fault, however until 5.0.26 it would work when not using the default Blizzard override bar.
In Blizzard's crash report those are the lines with "most" information (sadly):

Current Addon: (null)
Current Addon function: OverrideActionBar:Hide
Current Addon object: (null)

App:         /Applications/Games/World of Warcraft/World of Warcraft-64.app
Exception:   EXC_BAD_ACCESS
Error Code:  0x85100086
Error:       KERN_INVALID_ADDRESS at 0x0000000000000130

So I suspect Blizzard's Mac team didn't do their homework ...

I'd love to use the default OverrideBar, however it becomes unplayable :( Is there anything you could do for me? As I said, using Dominos's OverrideBar worked fine until yesterday.

This happens only on some vehicles. For me it crashes all the time at my Farm leaving a tentacle or from pulling bad crops. Darkmoon Faire on the other hand it worked. (Mac OS 10.8.2 64bit wow client)

I am also having this problem, it happens when the blizzard action bar override option is used or not, you can get into the "vehicle" ie the vine, fine but when you jump off wow crashes

Current Addon: (null)
Current Addon function: OverrideActionBar:Hide
Current Addon object: (null)

Exception Raised!

App: /Applications/Games/World of Warcraft/World of Warcraft-64.app
Exception: EXC_BAD_ACCESS
Error Code: 0x85100086
Time: 2012-10-14 08.57.07 PDT

Error: KERN_INVALID_ADDRESS at 0x0000000000000020
Crashed Thread: 0x00000a07

hope this helps

Experiencing the same exact problem here running 64-bit mac client on OS X 10.7.5. Using the latest Dominos 5.0.28 crashes happen on the farm as described by Sirlon above, as well as some other quests like Scouting Report in Jade Forest during vehicle dismount. I tried clearing cache, WTF, Interface, re-installing WoW, etc with no improvements. Yesterday, I re-installed Dominos 5.0.25 and haven't experienced any crashes yet on the farm or elsewhere.

I had been having the same issue on 10.8.2 and as nlvyper said above, reverting back to Dominos 5.0.25 has fixed the random crashing issue for me when exiting a vehicle like object (tillers roots, wind serpent faction quests etc.)

I am seeing this issue as well - the latest dominos causes issues with leaving vehicles. I've also managed to create a reasonably reproducable way of causing the crash.

You'll need:

• Access to Kelari Featherfoot at 18.2, 63.6 the Vale of Eternal Blossoms. This NPC is only available if you're revered with the Golden Lotus & have completed the three "battle armor of the storm king" quests from Zhi the Harmonious.
• Dominos 5.0.26 or later
• Optional: 2 person mount (sandstone drake, obsidian Nightwing, etc)

Method to re-create:

• Enter the game; mount the two person mount, fly around about, etc.
• Optional: use the 2 person mount, fly around a bit, then dismount (reason below)
• Speak to Kelari Featherfoot and take the "Let's roll." conversation to start
• Just let yourself fall off the wall - you'll do this if you don't do anything when you start

The game will not necessarily crash right away, it'll take a couple of tries to do this.

It seems that using a 2 person mount - eg Sandstone Drake, Obsidia Nightwing - before taking the rolling will cause the crash to happen a lot faster. Without mounting up first it can take 6-8 attempts rolling off the wall before the bug will happen. If you do it after using a 2 person mount - which are implemented as vehicles - the crash will happen faster. Normally within 2-3 attempts.

Whilst this may sound like a pain to need access to Kelari Featherfoot, this NPC hands out the "Roll Club: Serpent's Spine" daily quest which is basically Sonic the Hedgehog. Blizz implemented this as a vehicle, with a vehicle action bar.

The reason I picked this NPC is that you can ask to do the rolling again at any time by speaking to tthem which means that we have an easy way to get a vehicle with an action bar.

I came across this as there is an achievement for completing the run in under 70s.... it was chasing after that achievement that I found the easy to cause the crash.

I've not been able to re-create the crash using 5.0.25, although my char got a little tired of roling off the wall into the Dreadwastes on the 25th time!

I have been getting this error pretty frequently of late on Mac OSX 10.8.2. I'll try using version 5.0.25 of Dominos to see if I get any relief.

I can reproduce the problem pretty reliably when creating a new goblin and exiting the mount the player receives in Kezan (and can use only in Kezan). It might take a few times, but I find it happens really often once I exit a mount and immediately toggle the World Map.

In addition, I ran into this problem planting crops in Sunsong Ranch: the runty crops and the wild crops seem to be vehicles from the perspective of the game.

My logs aren't getting sent to Blizzard either in the event of a crash. The two functions that seem to be cropping up often in the logs are OverrideActionBar:Hide and UIParent:Hide.

Just chiming in to say that I'm having all the same crash issues as already discussed above. I even had the client crash during the "Savior of Stoneplow" quest when the player has to punch out of the guts of the mantid colossus.

The crashes seem to be most easily reproducible when player is automatically dismounted from some "vehicle", i.e., at the end of the Savior quest; and when returning a yak to the washer in Kun-Lai.

I'm on OS X 10.7.5, using the 64-bit WoW client with Dominos 5.0.28 as distributed by Curse. Will give 5.0.29 a shot!

Try 5.0.29. I'm not sure if it'll fix crashes, but I did redo the code at least 🐼

I'm using 5.0.29. It seems to be working fine so far.

5.0.29 looks good. (I'm still on the Yak Wash quest.) Was crashing consistently before w/ 5.0.28, but so far I've managed to return 3 more yaks without incident. :-)

I just switch to 5.0.29 & tried doing various bits in game - poking at the farm, then flying on a two person mount followed by doing the rolling along the spine twenty times. Given that the game would crash wtihin 2-3 tries of roll along the spine, I think 5.0.29 has fixed it.

Thanks!

From my testing last night, it appears 5.0.29 had corrected this issue. I've only tested on farm dailies, though.

calling this one closed for now :)

Haven't had a crash since 5.0.29. Awesome, thanks a lot!

I'll see if I can reproduce the issue on my macbook.

I'm not able to reproduce this in the darkmoon faire. I'm running Mac OS 10.8.2 /w the 64bit wow client.

I just reinstalled my WoW again today and did some testing on the airship guns of "Hellscream's Fist" when you first fly into Pandaria.

• "Use Blizzard Override Action Bar" disabled, I entered the vehicle and left it again using the red button. On the second try, WoW crashed.
• "Use Blizzard Override Action Bar" enabled, I entered the vehicle and left it again using the yellow button. On the second try, WoW crashed.
• "Use Blizzard Override Action Bar" enabled, only AddonLoader+AddonControlPanel+Dominos (w/o extra modules), I entered the vehicle and left it again using the red button. Once on the second try, once on the fifth WoW crashed.
• "Use Blizzard Override Action Bar" enabled, only AddonLoader+AddonControlPanel+Dominos (w/o extra modules), I entered the vehicle and left it again using the yellow button. On the second and third try, it still worked. On another WoW launch it crashed on the ~fourth try.

I can't really get a pattern out of this ... This is definitely strange! Oh, and I'm using a MacBookPro late 2010 + external monitor. Just for completeness' sake, as I don't expect any hardware debugging from you ;)

On another note, I just did the Yak wash quest (where you get to retrieve 6 dirty yaks to have them scrubbed in Kun-Lai Summit) and it crashed on the fifth return.
While I was inside the "yak vehicle", my micro button bar was a) missing the pvp button and b) shown at ~200% size with 100% alpha. I usually have it set to 60% size/20% alpha so that was hard to miss ;) When leaving the vehicle, everything goes back to normal.