artificeren

Still get crashes
Don't have compendium installed.
I play with the following plugins running:
BuffBars, BuffMonitor (only some characters), Challenge Tracker (only some characters), Combat Analysis, and TonicBars

Garan

Thanks for the info. I had disabled Compendium while testing AltInventory. I have not yet been able to reproduce the additional crashes being reported since 2.11b (I have been able to access Vault and Shared Storage in every combination I can think of with no crashes). There is no direct integration between AltInventory and Compendium (there is integration with Compendium and MoorMap) but they both consume a fairly large amount of memory. I will try some more debugging with Compendium also running after the weekend (daughter's 6th birthday takes priority ). Hopefully this can shed some light on the remaining elusive crashes.

Topi

First I'd like to thank you very very much for this great plugin. I hope I can use it now with the latest update as I did before RoR.

I just read your plannings for the release 2.12 and I'm looking forward to using that version.

Have a nice day.

Topi

Aurel

For anyone having issues with client crashes...:

I had problems with crashes caused by "alt inventory". they continued after this plugin was updated. interesting enough - the last plugin being unloaded which was mentioned in the chat was "compendium".
I disabled "compendium" to check if something might change...and...no more crashes.
I don`t want to say that there is a problem with "compendium" - as noone here saying something about it - but it might happen in combination with "alt inventory".

Cheers
Aurel

Vreejack

I will see if this works for me.

And while I am thinking of it, could you try to fix the way carriage returns work in the notepad? They are really screwy.

Oh wow, I am dating myself. I mean newlines.

artificeren

Firstly, just wanted to say that everybody appreciates how much work you've put into this plugin. I've really been missing it since rohan released. Unfortunately, I have to report that I'm still getting crashes about 50% of the time on logout with 2.11b. I have 11 characters with lots of space upgrades, and I usually log out while standing near a vault-keeper, if that helps. Is there any debug info I can acquire for you?

Garan

Thanks for the feedback. I haven't noticed any difference running as admin or as a regular user, they were both crashing with ver 2.11a and both ran fine with 2.12b. I have to check further into another report that the client crashed after accessing the Vault/Shared Storage which seems like a more likely culprit since they also have event handlers that could have a similar issue to the Update handlers.

Garan

Over the last few versions, I've been slowly but surely separating the inventory and other functionality with exactly this in mind. Ver 2.12 allows the user to select whether to display, track only, or completely disable each panel. This was originally driven by the desire to make the system more modular to make adding new modules easier, but has also been driven by the crowding of the UI for users that don't use the additional modules. In ver 2.12 there will likely be at least two new panels, Quests and Deeds, as well as potentially an additional panel for Mounts although at this time I'm not sure there is really a need for a Mounts panel. I've also considered splitting off most of the non-inventory info into a separate plugin and dropping the quantity tracker altogether as it seems to cause way more problems than it's worth. Unfortunately, until the crash issue is completely resolved I won't be making any more changes since it's a bit of a pain to keep two code bases, the current version plus fixes and the 2.12 version plus fixes.

While RecipeTracker is a fine plugin, it indeed has the limitation that it does not show all available recipes. Hopefully I will be able to get all of the new recipes into ver 2.12 (most of that is automated now with a couple of utility plugins I use for capturing and maintaining that data).

syahwhit

One thing I was thinking about regarding this wonderful plugin (which I haven't been using for the last month, and this makes me sad) is to divide it up a bit? Maybe have an option to disable some of the features that someone doesn't use, thereby reducing the memory usage from the game. Not sure if it's the size of the plugin that contributes to the crashes or not, but just thought this might be a way to work around the problem.

Also, I've found RecipeTracker (a rather new and simple plugin) to work great for checking recipes. The only thing it doesn't have that I'd like is a full list of all recipes to easily and quickly see which ones are missing. That way I can know which ones to look for, as well as which scroll cases to even bother opening. (Some of my alts have started getting stacks of cases up to 25, which I think is max stack on those... Talk about vault consumption.)

Sir Valiant

This is not the case for me. I have NO characters, nor did I ever, that have notes, but I still crashed.

I think it may have something to do with permissions. I have started the game running as admin and I no longer crash, well so far anyway. Hope this helps narrow down the problem.

Val

Garan

Yes, there are some logging and memory utilization features, but unfortunately they are not very useful in the case of client crashes.

magill

Is there any kind of "Logging" available -- like (especially) memory utilization. Or is it strictly up to whatever "writes" the developer puts into the plugin?

Garan

I was wondering if the Mac client had a similar issue. I've been able to crash the client by alt-tabbing out of the application a couple times and then switching toons, even with no plugins loaded. The memory leak issues made this hard to troubleshoot since the more memory you use, the sooner you crash and AltInventory uses quite a bit of memory when you have several alts worth of data.

As to the resize location, I tried testing it and had trouble with the bottom and corner until after I successfully grabbed the right side near the top. Once I had grabbed the right side, the bottom and corner worked fine. I'll have to investigate more but it looks like one of the graphics or container controls is too large and catching mouse events incorrectly.

For those wondering what I changed to avoid the crashes, I had to explicitly remove all of the event handlers that accessed Turbine objects such as the localPlayer object or the Chat window in the plugin.Unload event by explicitly setting them to nil. It seems Turbine changed the way Lua fires events causing some handlers to be called after the plugin is already unloaded thus causing the client crash. Explicitly setting them to nil prevents them from being incorrectly referenced in the underlying client code after they no longer exist. The lesson here is never, ever trust the "sandbox", always clean up after yourself.

magill

Keep in mind that it is NOT plugins alone which cause the crash-on-logout issue.

Granted, I'm using the Mac Client, however I can reliably reproduce the crash on logout by simply switching characters multiple times... no logout as such involved.

magill

I haven't been able to find the "sweet spot" to allow window resizing with the latest version.

The sweet spot has always been "very small" -- maybe only 1 or 2 pixels in size, but I'm not finding any at all... either horizontal or vertical, nor the corner to allow both directions.