Error when switching pets or when pet classes exit veichles. #68


  • Defect
  • Fixed
Closed
Assigned to _ForgeUser117147
  • _ForgeUser1990418 created this issue Jan 9, 2010

    There's a bug that occurs whenever someone instnatly changes pet, or when pet classes exit veichles. This is because of an assertion in GridRoster that assumes that if a unit pet event occurs the pet should either be the same as the previous pet or nil.

    The easiest way to test this is to party with a Warlock and have him cast eye of killrog.

    Here's the error:

    Message: Interface\AddOns\Grid2\GridRoster.lua:173: assertion failed!
    Time: 01/09/10 13:55:15
    Count: 2
    Stack: [C]: in function `assert'
    Interface\AddOns\Grid2\GridRoster.lua:173: in function `?'
    ...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:147: in function <...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:147>
    [string "safecall Dispatcher[2]"]:4: in function <[string "safecall Dispatcher[2]"]:4>
    [C]: ?
    [string "safecall Dispatcher[2]"]:13: in function `?'
    ...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:92: in function `Fire'
    Interface\AddOns\Ace3\AceEvent-3.0\AceEvent-3.0.lua:120: in function <Interface\AddOns\Ace3\AceEvent-3.0\AceEvent-3.0.lua:119>
    
    Locals: (*temporary) = false
    

    To fix this, remove line 173 of GridRoster.lua, seems to work fine regardless.

  • _ForgeUser1990418 added the tags New Defect Jan 9, 2010
  • _ForgeUser1990418 edited title Jan 9, 2010
  • _ForgeUser117147 posted a comment Jan 11, 2010

    Fixed in rev305.

  • _ForgeUser117147 removed a tag New Jan 11, 2010
  • _ForgeUser117147 added a tag Fixed Jan 11, 2010
  • _ForgeUser117147 closed issue Jan 11, 2010

To post a comment, please login or register a new account.