3 hours to track down the CTD
 

now i can be sure its this addons



if i turn OFF ANY OF THIS ADDONS - CDT GONE

how to reproduce
- steal some items
- pay the guard, in the moment you will pay and guard will take away stolen goods - you will got CTD

any ideas how to fix?

could you disable cmld? it has not been updated, i must to do this, but don't have really time, maybe today, tomorrow, don't know.

I CTD'd last night when a guard took seven items off of my body for the Indecent Exposure achievement and one other item out of my inventory. The only addons I share with that list are AwesomeGuildStore and Sous Chef.

yes

just now i turn all my other 20+ addons for alt character
but turn off AGS

guess what? CTD too:mad:(must be smthing else)

but 20+ addons without CMLD all okay

with this set of addons like in first post i got 100% chance of CTD :(

btw if i replace FilterIt with Advanced filters CTD gone too

might be smthing in new stolen subfilters in FilterIt

AGS itself does not do anything outside of guild stores.
The bulk of it's code is only initialized when you visit a guild store for the first time after a UI load.

The only thing that might have something to do with the crashes is libFilters, which gets initialized immediately:

My crash to desktop does happen if I open a guod store and play a bit with the different tabs, close it, do something else, open it again -> At this point sometimes the CTD happens

Got another strange problem:
If I do a /reloadui I crash back to the login mask sometimes and it tells me the server can't be reached.
Ot it tells me some other error message.

I tried to turn of all addons and this fixes it. HAve to test each I guess :(

I also crash quite often when I switch tabs in guild store since the patch. Not sure why or how I can reproduce it though. :(
It would be so much easier if we got some kind of crash log which shows the call stack leading to the CTD. Maybe a certain person reads this and gets creative? ;)

I had these crashes already before the patch 1.6.
Can't reproduce it with all chars but with some of them. It happens most of the time if I try to change a tab to the "Materials" tab (or some subfilters of AdvancedFilters.
Or if I open the guild bank and it was still at the materials tab or a subtab (like smithing crafting materials).

I guess it has to do with the materials somehow, because it never seems to happen if I am at another tab (armor, weapons).
Maybe it is just an endless looooooooooooooooop :rolleyes: like Garkin has told me before and will just happen if there are many stacks of materials, which won#t happen with armor/weapons.

well you ar right, but if you try to delete all addons from the folder, except this four
and run the behaviour i describe - i bet you will get CTD
and if you disable AGS or one of those addons - CTD gone:)

I installed all of those & tried the steps you posted over & over, it never crashed. I tried it at least 10-15 times. I don't know which of your addons is causing it, but my guess is that it is the same problem that some addons had with swapping horses (only its much worse here).

When you swap horses that change your carrying capacity the game updates every slot in your backpack.

When you get caught and pay a bounty, the game updates all slots in your BACKPACK & BANK so its much worse than the horse problem. Although I don't know why it would update slots in the bank...you can't deposit stolen items in the bank can you??

My guess is some addons your using are not excluding old items in the SingleSlotUpdate event and then somethings going wrong when they are all trying to update every slot in the backpack & bank at the same time.

EDIT: I forgot to mention, the stolen items filters in FilterIt would have nothing to do with it. They don't do anything unless you press one of the stolen item buttons.

mby the matter in bag space? i have 80 on this alt hero i tested, and you? will test on my main with 170 slots only when my 30k bounty will dissapear:D

No, you can't put stolen items in your bank. Updating the bank is completely unnecessary...

Maybe they use it to refresh the shared_inventories somehow. But for me it makes no sense.

@Circonian
-> Are we able to pre-hook this and abort the bank scan somehow?

That's an idea. Maybe we can get @merlight to throw it into his random ZOS fixes addon too :D

I tested it on a char that has 80 backpack slots with 120 bank slots, but my backpack only had like 15 items in it. The bank is completely full.
The slots only get updated if there is an item in the slot so whether or not those slots have items in them will also make a difference.

Why don't you just fence: sell/launder off your stolen items & then go kill yourself, its quicker than waiting :P

*cough* :p

I don't think so.

Ok, are we able to detect if we get caught and prevent executing our addon functions etc. to each bag and bank item by help of a variable we set, if we get caught?
Is there an event if we get caught and after we payed or run away?

There is no event & no "specific" InteractionType for it, and we don't have access to any of that code.

The only thing I could think of (is very sloppy) Surely theres a better way than this, but maybe it will spark an idea. I didn't test any of this, its just an idea.

To detect getting caught you could do something like hook the INTERACT_WINDOW:BeginInteraction() and check to see if GetInteractionType() returns INTERACT_CONVERSATION, and then check the chatter: ZO_ChatterOption1:GetText() and search the string for some text related to getting caught, something like: "Clear my bounty"
Or maybe just the INTERACT_WINDOW:SelectChatterOptionByIndex(optionIndex) and if the optionIndex == 1, then check the chatter text.

I couldn't think of a decent way to know when its done updating. Only thing I could think of would be to just block your code for some set amount of time with a flag. Like when you get caught set: dontRunCode = true and then On EndInteraction() do a callLater and after a few ms set it back to false.

But if you exclude code from running on old items in the EVENT_INVENTORY_SINGLE_SLOT_UPDATE, none of this matters.
If you need to run code on old items it might be easier to find a different way to handle that instead of inside that event. It would just depend on what you need updated and when does it really need to be updated.