What Does Crash Logger Do?

That's the question, really. Does it have any function? Does anyone ever look at it? Does it just collect data that goes into a black hole (along with the flamingo and other SL animals). Does someone figure out why it's happening, or what's it's purpose? I have my preferences set to send a crash report every time I crash. I see it collecting the data and sending the data, when I log back in again and I wonder what happens after that.

Supposedly it is giving LL details about how the crash happened.

However, when it takes 4+ days to respond to a "I cannot log in because my account is ghosted in a sim" trouble ticket, leaving people unable to get into SL - it makes me doubt if they even have the time to look at crash log information at all.

I honestly wouldn't know what the Crash Logger does... except crash!

I don't really think it does anything anymore. LL is so hell bent on the JIRA that bug reporting took a step towards ridiculously complex.

Basically, it goes to the file sorter that looks an awful lot like either a shredder or a trash can.

The crash logger is extremely valuable to the QA team.

It produces a call stack. A list of the last few actions the code took before the crash. Looking at this allows them to find the source of the problem where without it they would never be able to pinpoint it.

Individual reports are not looked at. Instead, they are grouped, and combined by similarities allowing them to categorize the mess of reports into specific problem areas. Then when tracking down a specific crash cause they can look at the call stacks related to it.

The support team does not handle them. It is the developers and QA team that the reports go to.

Supports response times is unrelated.

Crash Logger is the new action figure from Mattel, a brawny, Paul Bunyanesque figure with a three-foot long chainsaw. One of the optional sets sold for Crash is the Stone Canyon Hauler, a big fifth wheel pickup with oversized knobby tires and a winch for pulling out stumps and deadfalls.

...unless you're running the Linux version; then, it literally does nothing at all!

It takes the report it makes, files it on a server somewhere in the Gobi Desert to be filed away by short-tempered marmosets, where they look at it when they get around to it. Eventually. Someday. In the future. Not quite right now, but soon. They hope. When they get there. If they can find the server. And their plane tickets. And their shoes. But first they got to turn back around & go home because they forgot the plane tickets. Yep! They'll get on those reports aaaaaaaanytime now. Just you wait & see!!! Any minute now.

Well this was fun......weeding out the serious (I know, the responses were ALL serious) it looks like maybe someone does look at the crash loggers as an entity, not individually, to try to fix crashes that are happening from same or similar reasons......Thanks. Now I understand, it ain't all about me, me me.

I've seen LL post their top-10 stack traces on the public developer mailing list.. Just tried to find an example of this on the wiki but the wiki is, apparently, toast.

This stuff actually is useful to LL and other bug chasers trying to fix viewer crashes.

edit: /me hugs google. Here's an example: https://lists.secondlife.com/pipermail/sldev/2009-July/014759.html

My correlation is that if they are so trifling about support tickets and their horrendous lack of response even when someone cannot access SL at all and may be paying monthly tier of who knows how much, that one could expect an equal trifling attitude about Crash Loggers.

I no longer look at LL the way i used to. For the first time in nearly 6 years, i am skeptical about the company, do not trust them, and find their lack of support in the "support ticket" field to be totally unacceptable.