Blizzard_TimeManager error

Gaenjin · 11-01-10, 09:03 AM

Would you own this?

Code:

Date: 2010-11-01 07:56:03
ID: -1
Error occured in: Global
Count: 1
Message: ...AddOns\Blizzard_TimeManager\Blizzard_TimeManager.lua line 674:
   attempt to index global 'BlizzardStopwatchOptions' (a nil value)
Debug:
   [C]: ?
   ...AddOns\Blizzard_TimeManager\Blizzard_TimeManager.lua:674:
      ...AddOns\Blizzard_TimeManager\Blizzard_TimeManager.lua:650
AddOns:
  Swatter, v5.9.4961 (WhackyWallaby)
  nUI, v5.07.06 (Development)
  BlizRuntimeLib_enUS v4.0.1.40000 <us>
  (ck=6b)

Its a total PITA to repro, and I mostly get it just by logging in and out of different characters. As you can see, I've narrowed it down to just nUI and Swatter running. I've tried to get the default Blizz UI to throw the error, but I just can't figure out the trigger.

I have searched the web, high and low and I can only find one instance of this reported back in early 2010... and that person just happened to be using nUI as well.

Over time, Swatter will fill up with these errors. It mostly occurs just logging in and out of different characters, but that is not 100% reliable.

My concern is over the cause of this error and if its affecting any performance of the UI (as in mem leakage) or functionality of any addons, in an adverse way.

spiel2001 · 11-01-10, 09:19 AM

Yeah... I think this is some kind of odd conflict between nUI and the default UI. I have been able to determine that it occurs only on logout... but have not yet figured out why. I don't *think* it has any runtime impact on the game at all, but could be missing something there.

Gaenjin · 11-02-10, 03:16 AM

Ok, good to know. Its been driving me nuts because there are just no reports of it to be found anywhere, and trying to get a solid repro on it has been a /wrist.

One of my problems, is that I can't figure out how to configure Swatter! to have the error pop up, or send it to Chat so I can see when it happens. I'd *like* to say that I have had it occur by clicking on the clock and playing with the Alarm and Stopwatch settings, but...

spiel2001 · 11-02-10, 04:26 AM

Yeah... like I said, it appears to only occur on logout which means that it's too late to put it in the chat frame or a popup as you've already closed the world frame. It has made it terribly difficult to run down what the problem is, to be sure.

schmitty · 11-03-10, 01:55 AM

I'm not sure about Swatter, but BugSack keeps a history of errors between sessions. This may help with tracking down the problem.

spiel2001 · 11-03-10, 04:17 AM

Yeah... Swatter does as well. The issue is in trying to track down what's throwing the error when you're in a phase that you can't interact with the game.

Gaenjin · 11-03-10, 11:03 AM

The problem I have with Swatter! is that I do get this TimeManager error other than while logging out, but Swatter! does not pop up an error window or send anything to Chat. There might be some settings to change that, I'll have to look.

I was able to verify yesterday that this error will occasionally occur at or right after login for me. I'm still unable to find a reliable repro, however, but I had a clean error log when I logged in, and when I checked the log a couple of minutes after logging in, I saw there was a TimeManager error entry, with the timestamp matching my time of login.

I do set my nUI Clock settings for "Both", since I'm PST and play on a CST server, but the error does occur on bank mules that I haven't changed anything on.

Did I mention that I have gotten the error while playing with the Alarm and Stopwatch UI? I can't find a reliable repro for that either, I just happened to noticed a new entry in the error log after I was playing with the settings for Alarm and playing with the Stopwatch.

I'll find some good info eventually. Its the only error I get now, so its a matter of time and patience. I'll post what I find.