Firestorm crashes in crowded events due to buffer overflow - LLTemplateMessageReader::getData
tracked
lLeora Resident
Hello Firestorm Support Team,My viewer is constantly crashing whenever I visit crowded events or parties, but it works perfectly fine when I am alone at my home region.The viewer triggers a buffer overflow protection error with the following message: "LLTemplateMessageReader::getData : Msg ObjectUpdate variable Data is size 16128 but copying into buffer of size 16".It seems like a corrupted or oversized attachment/object from another avatar is triggering this network message error and bringing down the viewer.
Photo Viewer
View photos in a modal
Log In
Sora Firehawk
Same crash on Firestorm 7.2.4 (80712), standalone install, Linux (Bazzite 44).
Hardware: Ryzen 7 9800X3D, Radeon RX 9070 XT, Mesa 26.2.2, kernel 7.2.7.
Errors (first seen Sep 26, 2026):
- lltemplatemessagereader.cpp(109) getData: Msg ObjectUpdate variable Data is size 4080 but copying into buffer of size 16
- same error with size 51254
- llnamevalue.cpp(589) getString: AttachItemID not a string! (once, while wearing a default avatar)
Pattern:
- Crashes at login, after teleports, and randomly.
- Depends heavily on the sim. Two busy sims crash 100% of the time (a large store sim and a warehouse sim; I can't stay more than a second). Another sim has had zero crashes. My own sims are about 0-20%.
- Not caused by a worn outfit: it continues with the default system avatar. It started around the time I wore a certain avatar, which may be coincidence.
Already tried: cleared viewer cache and inventory cache, installed a fresh copy of Firestorm. No change.
Comparison: an older Windows 10 PC (i7-4770K, RTX 2070 Super) running the same Firestorm 7.2.4 (80712) does NOT crash in the same situations, including the sims that crash 100% on Linux.
I had used this Linux setup for almost a year with no crashes before this started.
New test:
I also logged in with a completely different account and avatar on the Linux machine: same crashes, same sims. The same test on the Windows PC (all caches cleared) does not crash. So it is not tied to the account, avatar, attachments or inventory. It only happens on this Linux install.
Kyle Linden
Merged in a post:
crashing both viewers sl and firestrom
RhondaRenea Resident
every time i go in to area with a lot of people my viewers craah and i log back in stay on 3 to 4 mns and crash again im not the only one this is happening to my friend and i both did factory resets on our pcs and we still have the issue but if we sit at home we are good
its been going for over 6 months for me on my end and it recently started for my friend
Dan Linden
updated the status to
tracked
Dan Linden
Thank you for the report, lLeora!
I've reopened the Second Life version of this crash at https://github.com/secondlife/viewer/issues/6383 (updated).
lLeora Resident
Dan Linden of nothing, will this be solved??
Bavid Dailey
You know there' a place to report Firestorm bugs to the firestorm team ?
Hecklezz Resident
Bavid Dailey The issue isn't with Firestorm and occurs on all viewers, it is an issue with their simulators and there is already a report here-
LL released a simulator update on September 23rd to address this- https://releasenotes.secondlife.com/simulator/2026-09-22.35767837201.html
But It seems to have not worked and bugsplats are still coming in from users on this new simulator.
lLeora Resident
Bavid Dailey Yes, I've done that well.
lLeora Resident
Hecklezz Resident I don't know what else to do!
Hecklezz Resident
lLeora Resident There isn't anything you can personally do, Linden Lab needs to push out a simulator update that fixes the problem.
lLeora Resident
Hecklezz Resident my game was running normally, and that started out of nowhere. I already tested the official one too and it closes the game in the same way, is there no other version of the game that doesn't have this problem?
Hecklezz Resident
lLeora Resident The issue isn't the viewer. As I have said twice now, the issue is with the simulators. It is server-side, LL's servers are sending invalid data to the viewers which causes them to throw an error and close.