Open Aiue opened 5 years ago
Except when used with Questie, it has been reported that when using AQT alone the client stops and terminates as unresponsive.
I've experienced the same phenomenon, but I'm not sure if it's because of AQT because there are more normal loadings.
When you select a character on the character selection screen and log in, it freezes after loading the screen.
I'm not sure what would cause this, if it at all is AQT. I'll go over my iterators and recursive functions, but all of them should have sufficient protection against running infinitely.
Are there any progress made on this issue? From the report, it seems like you're freezing not only right after you log in, but also during the quest.
One Korean user installed only AQT and Questie, deleted both the cache folder and the WTF folder and tested it. Rogues have three quests, Hunter has five quests and Priest has five quests to test, but only the priest had this issue.
Among other users who play an average of 10 quests as Rogue, this issue has emerged.
Is there any way I can help you with this issue?
Hmm. Initially I would've said to individually disable calls during OnInitialize() and OnEnable(), but if it also happens at other times as well, it's suggestive something else is at play.
https://github.com/Aiue/AQT/blob/cb7fb16ccbfeb6d205c223103d537f5e8d19979b/Core.lua#L987
This could be of interest. It's possible that for some reason it's not a sufficient base case in some situations. Not sure whether or not it would help to change that line to something along the lines of if not qTitle or qTitle == "" then break end
or if not qTitle or qTitle:len() == 0 then break end
. It would be worth trying, nonetheless. There could be other things to look at as well, but that's probably a good starting point.
Two users who gave feedback to the Korean WoW community requested a test. I asked the user to report a code that does not have an issue and to test if the same issue occurs even after the two codes are corrected.