|
I am getting the same error (I wouldn't say "all the time" but once every hour or two) with nUI5.
Just speculating, but it may have nothing at all to do with any specific addon. The recent pattern seems to be that some valid calls to Blizzard addons just fail for no apparent reason. It could simply depend on where various addons are loaded in memory, and have nothing to do with their actual code. In other programs I've debugged, this type of behavior can result from data or pointers getting corrupted or improperly initialized (in this case, probably inside the client rather than Lua code).
Since nUI has a relatively large memory footprint compared to most other addons, it would probably be more likely to be "in the wrong place at the wrong time" in memory.
|