Callback Handler Issue #5


  • Defect
  • Waiting
Open
Assigned to _ForgeUser131699
  • _ForgeUser141488 created this issue Sep 10, 2012

    What steps will reproduce the problem?
    1. Multiple mobs, switching between them.
    2. Use ElvUI
    3. Get error msg.

    What is the expected output? What do you see instead?
    Timer correct instead of every 5 seconds, play nice with other addons

    What version of the product are you using?
    Latest 1.5

    Do you have an error log of what happened?

    Message: integer overflow attempting to store inf
    Time: Mon Sep 10 00:07:35 2012
    Count: 1
    Stack: (tail call): ?
    [C]: ?
    Interface\AddOns\TimeToDie\TimeToDie.lua:194: in function `?'
    ...vUI\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147: in function <...vUI\libs\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 `?'
    ...vUI\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:92: in function `Fire'
    ...face\AddOns\ElvUI\libs\AceEvent-3.0\AceEvent-3.0.lua:120: in function <...face\AddOns\ElvUI\libs\AceEvent-3.0\AceEvent-3.0.lua:119>

    Locals: No locals to dump

    Please provide any additional information below.

    To be honest, since the error message mentions ElvUI I'm honestly unsure which add-on is the culprit...ElvUI or TimetoDie.

  • _ForgeUser141488 added the tags New Defect Sep 10, 2012
  • _ForgeUser131699 posted a comment Sep 10, 2012

    This is rather strange, can you see if you can reproduce this error with just TimeToDie enabled?

    I think what may be happening is that TimeToDie is being blamed for another addon's error.

  • _ForgeUser131699 removed a tag New Sep 10, 2012
  • _ForgeUser131699 added a tag Waiting Sep 10, 2012

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