[Bug] Massive CRIT spam: "GetArtVariationItemInternal failed" for twister:2 hundreds per second

Apologies, this is on PC. I posted this to the wrong thread.

Getting a non-stop flood of CRIT-level errors in Client.txt related to the Twister skill art data. It's printing hundreds of lines per second and the log file is 63MB+ from a single session. The game doesn't immediately crash from it but performance tanks noticeably while it's happening and it seems to contribute to eventual instability.

MTX that is being used is called ChaosBorn Druid Twister Effect

Error (repeats hundreds of times per second):
[CRIT Client 292] GetArtVariationItemInternal failed trying to access data from index 5 of skill art data (twister:2)

When it happens:
The spam starts during gameplay and doesn't stop until the zone changes. It appears to fire every frame or multiple times per frame — I'm seeing clusters of 10-15 identical entries within the same millisecond timestamp. Normal gameplay log entries (NPC dialogue, zone transitions) still appear between the spam, so the client doesn't fully lock up, but it's clearly under significant strain.

System:
- OS: Linux Mint, kernel 6.17.0-35
- GPU: NVIDIA GeForce GTX 1080 Ti 11GB
- Driver: 535.309.01
- Proton: 9.0 (Beta) build 203
- Vulkan renderer
- 24GB RAM

What I've tried:
- Verified game files through Steam — no issues found
- Nuked the entire ShaderCacheVulkan directory (~222MB) and let it rebuild
- No mods or third-party tools installed

Additional context:
The error references twister:2 at art variation index 5, which suggests either a missing/corrupted art asset for a specific MTX variant or skill effect, or an out-of-bounds index in the art variation table after a recent patch. I'm also seeing an unrelated NVRM: Xid 8 GPU page fault in dmesg around the same timeframe, but the art spam appears independently of the GPU fault — it starts before the Xid event and continues after it.

The log also contains a separate [ENTITY2] Pipeline generation failed error for a CarverShaman fire trail effect from an earlier session, which might indicate a broader issue with effect pipeline generation this patch.

Has anyone else seen this since the latest update?