Open DoctorVanGogh opened 10 years ago
Sinaloit
commented
10 years ago I'm fairly sure this is related to an issue I experienced with CallbackHandler. I sent Bitwise an example addon a while ago but the issue still seems to be occuring. I guess I'll try poking him through twitter too or something :(
DoctorVanGogh
commented
10 years ago Actually I found the exact line of code to trigger the crash - new version of my addon surprisingly no longer has it ^^
If you use the exact changeset and comment this line https://github.com/DoctorVanGogh/Newton/blob/39483d65c4b49629c5235daacbb681595425952e/Newton/Newton.lua#L518, obviously some ui things don't work any more, but there are no more crashes.
Really weird that calling SetData() would make the client unstable... I've now worked around this by just stuffing indexes in there instead of whole objects :(
It seems I tend to do nasty things with Wildstar ;). Now I've stumbled over a crash issue that in all likelihood is in no way caused, but still nicely illustrated through AddonsMonitor.
It seems my new version of Newton (http://wildstar.curseforge.com/ws-addons/220458-newton/files/2209283/download) does something which may trigger a crash issue both in the default system menu (ESC key) and with AddonsMonitor. Basically four out of five times I press ESC the game crashes - now with AddonsMonitor enabled the game directly crashes on login yay ;)
My assumption is there's some function that's both called by the default system menu (Addons list) and AddonMonitor that throws up.
First I'd like to check if you can reproduce this - if so I'd suggest to escalate this directly to someone at Carbine - I trust NCSOFT's support monkeys about as far as I can throw them ;)