Random UI Errors

[CaptainBlagbird]

Hi there

So after logging in or reloading UI, I sometimes get random UI Error messages like this:

17552056426385430174:3: attempt to index a nil value
stack traceback:
	17552056426385430174:3: in function '(main chunk)'

As you can see, it doesn't happen in a specific add-on file, but I still think it is caused by an add-on (and probably by one of mine ). Could that happen by using zo_callLater, or does anyone know how it happens?

As I said, I can't reproduce it because it happens randomly (as it seems). I'm trying to track it down to one add-on, but that takes some time (and maybe it isn't even caused by an add-on).

(Sorry if that has been answered already, I did a quick search and couldn't find anything related.)

[sirinsidiator]

Errors like this are usually produced by functions that are called from xml handlers.
Maybe one handler is called before the corresponding lua code is initialized?

[QuadroTony]

i meet it often

bug catcher can help you

it can catch only this obsolete errors and keep showing errors from addons, for example

[CaptainBlagbird]

Originally Posted by sirinsidiator Errors like this are usually produced by functions that are called from xml handlers. Maybe one handler is called before the corresponding lua code is initialized?

Good hint, I'll check that.

Originally Posted by QuadroTony i meet it often bug catcher can help you it can catch only this obsolete errors and keep showing errors from addons, for example

Nice, I'll install it out right away

[Garkin]

Originally Posted by QuadroTony i meet it often bug catcher can help you it can catch only this obsolete errors and keep showing errors from addons, for example

I think hiding error is not a solution. Errors should be fixed not just ignored.

And as sirinsidiator said, this error comes from XML file. One of handlers calls function which is not defined yet because it is initialized after XML file is loaded or which doesn't exist at all (typo in name).
I'd start with all XML files with OnUpdate handler, most of the errors comes from this handler.

[CaptainBlagbird]

Originally Posted by Garkin I think hiding error is not a solution. Errors should be fixed not just ignored.

Yes, I realised that BugCatcher only suppresses the messages. I thought it'll give a hint about where the bug occurred. I'll go through all XMLs.

[merlight]

If it happens often enough, you can try this add-on I've just hacked http://www.esoui.com/downloads/info1...lsCatcher.html
Just wait for the error to pop up, then type: /undefs
With some luck, there'll be a familiar name with a typo at the bottom of the list.

[CaptainBlagbird]

Cool thanks, I'll give it a try