You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an error occurs frequently (every frame) and the callstack context is long, opening BugSack can cause huge frame drops.
As a proof of concept if you import this WeakAura it will trigger an error every frame in a long function. Opening BugSack while the errors are still being generated freezes my game to <5 FPS. I know this is an artificial example but I have encountered this issue in the wild several times.
I have traced the issue to colorStack, which was taking 200ms/call with this example. Specifically this line:
ret = ret:gsub("([^\\]+%.lua)", "|cffffffff%1|r") -- Lua files
causes a lot of backtracking. Replacing it with
ret = ret:gsub("\\([^\\]+%.lua)", "\\|cffffffff%1|r") -- Lua files
fixes the problem.
The text was updated successfully, but these errors were encountered:
When an error occurs frequently (every frame) and the callstack context is long, opening BugSack can cause huge frame drops.
As a proof of concept if you import this WeakAura it will trigger an error every frame in a long function. Opening BugSack while the errors are still being generated freezes my game to <5 FPS. I know this is an artificial example but I have encountered this issue in the wild several times.
I have traced the issue to
colorStack
, which was taking 200ms/call with this example. Specifically this line:causes a lot of backtracking. Replacing it with
fixes the problem.
The text was updated successfully, but these errors were encountered: