Unfortunately I don’t know of any solution that works. There are a lot of threads about it and a response on the weakaura github once commented that it was a bug on Blizzard’s end that they need to fix related to sound caching.
opened 07:07PM - 23 Mar 25 UTC
closed 07:53PM - 23 Mar 25 UTC
🐛 Bug
⏱ Awaiting Response
### Is there an existing issue for this?
- [x] I have searched the existing ope… n and closed issues.
### Description
Since the beginning of S2, I'm having issues with some weakauras - issues that dit not appear before the season 2. Sometimes, when a weakaura "happens" during an encounter (example : I get PI, which trigger one of my weakaura), I get a freeze for 3 to 5 seconds, which seems to happen either at the beginning of a raid night or randomly during a key. I don't get any lua error (except "script ran too long" from Weakauras).
I guess it happens because of Weakauras, because whenever it happens, I know that I'm receiving a buff that triggers one of my Weakauras.
Example of the PI Weakaura, which did not cause any issue prior to season 2 (It had an update since season 1, but it just moved the anchor point, which should not cause issues) : https://wago.io/aoeHwl9Hc
Note that it happened before and after I did a graphic card driver update, just in case.
Here are examples of errors happening in bugsack when the issue occurs:
```
1x WeakAuras/WeakAuras.lua:4866: script ran too long
[WeakAuras/WeakAuras.lua]:4866: in function 'SendDelayedWatchedTriggers'
[WeakAuras/WeakAuras.lua]:4976: in function 'UpdatedTriggerState'
[WeakAuras/BuffTrigger2.lua]:2013: in function <WeakAuras/BuffTrigger2.lua:2005>
[WeakAuras/BuffTrigger2.lua]:2508: in function <WeakAuras/BuffTrigger2.lua:2501>
Locals:
Skipped (In Encounter)
```
```
1x WeakAuras/GenericTrigger.lua:1030: script ran too long
[WeakAuras/GenericTrigger.lua]:1030: in function 'ScanEventsWatchedTrigger'
[WeakAuras/WeakAuras.lua]:4866: in function 'SendDelayedWatchedTriggers'
[WeakAuras/WeakAuras.lua]:4976: in function 'UpdatedTriggerState'
[WeakAuras/BuffTrigger2.lua]:2013: in function <WeakAuras/BuffTrigger2.lua:2005>
[WeakAuras/BuffTrigger2.lua]:2508: in function <WeakAuras/BuffTrigger2.lua:2501>
Locals:
Skipped (In Encounter)
```
### WeakAuras Version
WeakAuras 5.19.5
### World of Warcraft Flavor
Retail (Default)
### World of Warcraft Region
EU
### Tested with only WeakAuras
I got this issue with only WeakAuras enabled
### Lua Error
```Text
1x WeakAuras/GenericTrigger.lua:1030: script ran too long
[WeakAuras/GenericTrigger.lua]:1030: in function 'ScanEventsWatchedTrigger'
[WeakAuras/WeakAuras.lua]:4866: in function 'SendDelayedWatchedTriggers'
[WeakAuras/WeakAuras.lua]:4976: in function 'UpdatedTriggerState'
[WeakAuras/BuffTrigger2.lua]:2013: in function <WeakAuras/BuffTrigger2.lua:2005>
[WeakAuras/BuffTrigger2.lua]:2508: in function <WeakAuras/BuffTrigger2.lua:2501>
Locals:
Skipped (In Encounter)
```
### Reproduction Steps
1. Play an encounter (dungeon, raid).
2. Have a WeakAura trigger (ex.: get a buff).
3. Sometimes, the game game will hang up for 3-5 seconds (but seems to occur most of the time at the beginning of a session).
### Last Good Version
WeakAuras 5.19.3
### Screenshots
_No response_
### Export String
```Text
```
### Bisector Report
```Text
```
Someone commented:
That lua error is most likely caused by a bug in the wow engine, which has to do with playing sounds. If a sound file is not cached, sometimes the wow engine takes a long time to load the sound and causes freezes. We can’t do anything about that, it’s for blizzard to fix.
Here’s a tech support thread with over 200 replies about it:
Ever since 11.1 hit, my game will freeze during big pulls in M+ and during boss fights in Raids.
I found this post on the eu forums about the same issue.
Is anyone else experiencing this?
other threads:
So let me preface this with a lot of information to save you a lot of time. When I say I’ve gathered information and I’ve tried just about everything I mean it. I used to write a tech YouTube channel when I would build and design systems to benchmarking etc and I used to build systems to sell in excess of over 100 per year. So I have a plethora of parts and components available to me for testing at a given notice.
Since patch 11.1 I’ve noticed in group content raids and Mythic plus that I won’t…
Hello, i’ve been experiencing a rare bug that freezes my screen for about 5 seconds… It only happens in dungeons. I already did the repair thingy, updated all my drivers and addons, etc. I don’t know what else to do because it happens at the worst moments and its very very upsetting.
Edit: Checked in Event Viewer to see if it was something related to an unwanted update or whatever from my computer but nothing showed up while the dungeon (and freeze) was happening.
Edit: Also happens in raids.
I made this post in the tech forum not realizing Blizzard doesn’t monitor it.
Is anyone else having this issue in M+ and Raids where the game will just lock up entirely for about 1-2 seconds in instanced content like M+/Raid/Delve?
The person in the tech forums suggested going back to the early Feb drivers from Nvidia but those were the drivers I had when I first noticed the problem once 11.1 hit and updating to the latest drivers hasn’t fixed it.
Some people will blame addons since it tends to happen when an addon is playing a sound, but many people who don’t use the same addons also claim to have the issue. One person in one of the threads claimed it happens only when they have chrome open, which seems odd.
I think it happens so infrequently that people just try to attribute it to something but can’t accurately tell for sure it’s that thing since it doesn’t happen often enough. I tend to think the response on the weakauras github is probably right and it’s something Blizzard needs to address. Unfortunately they’ve never acknowledged the existence of the problem as far as I know and have no idea if they’re even trying to fix it.