[sldev] SLDev Digest, Vol 30, Issue 47
Maggie Leber (sl: Maggie Darwin)
maggie at matrisync.com
Thu Jun 18 08:40:03 PDT 2009
On Wed, Jun 17, 2009 at 9:35 AM, Kent Quirk (Q Linden) <q at lindenlab.com>
> The bugs that were found and fixed in the next 3 RCs were minimal. On
> a global statistics level, the crash rates are lower than they've ever
> been, even when you include crashes caused by specific video cards.
Well, we can only go by our own crash rates and word-of-mouth since we don't
get to see the global stats. Our local crash rates here are still what I
would call "awful", and clearly worse on 1.23 than 1.22, with two users
making heavy use of hardware selected and purchased specifically on the
basis of the published requirements for SLV.
The crashes are almost always due --as far as I can see from the information
available-- to virtual memory exhaustion.
Perhaps I have "a specific video card". If so, I think the "specific video
card manufacturer" would be interested in hearing about a claim that their
card is crashing your app...I'd be interested in hearing the details of the
bugs you filed with them, assuming it's not constrained by an NDA.. (The
last time I dealt with a severe SLV bug that was repeatedly and strenuously
attributed to the video card driver, it turned out to be the result of a
trivial code defect in SLV, found by a third party developer).
I do hope your crash rate is calculated per session hour. Because if it's a
raw number of crashes per day or even per session, I do know that the uptake
of 1.23 in our operation was limited by the fact that the thing kept leaking
up and falling over, and if others were affected the same way then a raw
crash rate per day would be badly distorted.
Any chance you'll start publishing the viewer crash stats?
Maggie Darwin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/sldev/attachments/20090618/c082e3e4/attachment.htm
More information about the SLDev
mailing list