VuhDo, ISBoxer and 132 errors like mad

For the last week or so I have been getting a staggering number of Error #132 crashes whenever my team has been in instances and needed to use VuhDo & a repeater region to heal. The crash logs suggest the problem comes about when VuhDo sends the signal to stop casting, something I do in order to prioritize healing spells. It only seems to affect 2 characters usually, which was weird but whatever. I've taken all the usual steps (nuking cache, interface, wtf, nuking the characters from ISBoxer and re-creating them in case it was a corrupt file there) and so on, but all to no avail. Happens in DX9 and DX11 mode, 32 and 64 bit mode, I've turned off any non-essential process, etc. The ONLY way I'm able to get the crashes to stop is if I remove VuhDo, so that's clearly the cause.

Does anyone else have this issue? If so, did you fix it?

Right now I'm figuring out a different solution to it - most likely modifying my pitbull layout to look like the old VuhDo horizontal bars and then throwing Clique on top of it to handle my mouseover healing etc. Hopefully that will mimic the functionality but without the issues VuhDo is giving me.

You can go with Vuhdo or Healbot or Grid + Grid Custom Layouts + Clique...
If you want to heal with addons.
Alphabetical sort (or any fixed order, that is the same across all windows).
With a Repeater Region across the zone, block local clicks and sending clicks to your healer's slot or an ATG with your healers in it.

You can use Click Bars instead, over any fixed order sort.
Whether Pitbull, Shadowed Unit Frames, Grid, whatever.
http://isboxer.com/forum/viewtopic.php?f=4&t=2911

Good stuff as always, Ualaa - I wound up going with clique on top of pitbull just since I'm super familiar with both.

On the plus side, vastly reduced the number of crashes, and it more or less works.

On the minus side, it's not quite as elegant as VuhDo was and I still get the occasional crash so maybe it's not VuhDo but rather the whole "click to heal" part where it does stopcasting or something. Someday it will work!

Sounds like a timing issue, possibly even some sort of recursion loop. You might take a look at the macros you are calling with Vuhdo (if it's even calling macros...I am unfamiliar with it) and see if you can comment out some things to see if it's some combination of things in there that aren't playing nice.