Random InventorySlot.lua error after update...
 

Trying to track this down and not having much luck. Maybe someone here can help?

After the Homestead update I started getting this error at random when double-clicking or dragging to delete items from my inventory. Right-click then selecting use item from the menu also causes it.



I deleted all saved variables including ZOS ingame settings, and disabled all addons, then started enabling one by one and it seemed that EMACS was causing it, which seemed unlikely since all it does is return true for the KEYBINDING_MANAGER:IsChordingAlwaysEnabled() function. But then after a few reloads it came back. Then it went away.

It doesn't actually seem related to any one addon, as far as I can tell.

I'm really glad to see this is somewhat widespread. Inventory Grid View is currently crippled by this sort of issue.

So something changed such that practices we've been using over the last few years is now considered insecure. As best I can tell, for Inventory Grid View at least, it may be an issue with insecure items being allocated in a resource pool that is assumed to be completely secure. This is similar to the context menu problem that LibCustomMenu solves.

Or maybe it has to do with hooking inventory slot setup callbacks.

I'm still largely stabbing in the dark.

The strange (and infuriating) thing about it is that it seems completely random. I have have a "safe" set of addons loaded and everything works fine. Using items from my inventory works fine. Then suddenly, it stops working.

Sometimes it can go for hours before it breaks, making testing addons one by one a prohibitively time consuming process.

I'll have to track down the post with the specific API changes this patch makes and try to make some sense of it, because like I said, it is infuriating! I ended up having to disable all addons just to drink an XP potion!

O.o

I noticed that issue too when I tried to open a container. Unlike before with the long standing refresh issue that we recently solve, this one does not go away when I move the mouse to a different item.

After reloading the UI, I had no problem to open the container, which makes me believe that after using the game for a while something happens which causes this issue.

I just got the same error at random when depositing to the bank with either double click, menu option, or keybind. Reloadui solved it for now.

I was getting it constantly with CraftBagExtended before I patched. The odd thing is, the code that seemed to cause the error was related to prehooking menubar tab buttons' callbacks, which shouldn't have anything to do with the slot actions. To work around it, I removed my prehooks and worked with scene fragment shown/hidden callbacks instead.

Just posting silvereyes' stack traceback so I don't lose it in Gitter:

This is what led me down the corrupted object pool path:

With Inventory Grid View active, the first 12 to 13 item slots in the grid function as expected. 12 - 13 is the number of items that are normally visible in the default list view. The rest produce the "attempt to access a private function" error when trying to use/bank/etc. If you bank the 13th item, the previously 14th item (13th after the list is refreshed) becomes valid.

In my modified scroll update function I utilize the inventory slot object pool - inventorySlot.dataTypes[typeId].pool. Maybe the number of preallocated (and thus secure) objects here was reduced?

If that is the case, I'm not sure how to make the insecure slots actionable.

I think you are on to something here. I have been trying to narrow down the steps that lead this to occur and it seems a similar issue as you describe with Advanced Filters.

If I have an item deep in my bags, say slot 20, and I filter by armor, then by heavy, using advanced filters, and try to deposit that item in my bank, I get the error.

If I reload and scroll through my whole inventory to the item without filtering, no error. This has happened three times now though it is not 100% repeatable, so I can't say with 100% certainty it is the culprit.

However what you described does indeed seem like a prime candidate.

This is driving me crazy!

This is still an issue. Did nobody find a cure?

It's again an issue due to s ZOs bug. See FCOItemSaver comments and first "sticky" post.
Or other forum threads about error messages/insecure here at esoui.

Thanks. This is the thread that Google brought me to.