[sldev] SLDev Digest, Vol 30, Issue 47

[Joel Foner]

Is a crash of the Vivox/SL Voice subsystem considered a "crash" in crash
rate stats? I and others I know have been having repeated voice subsystem
crashes at a higher rate than previous viewers (Windows XP popup explaining
that voice module has crashed while the viewer is still apparently running),
and I'm wondering if this is transparent to the crash logging. Perhaps it's
just better error reporting and the crash rate of voice is the same - not
sure - but it is visible more frequently. In addition, I've been regularly
getting crashes/lockups on startup (before splash screen is fully rendered)
that do not seem to trigger a crash report.
Just a couple notes from the outback,

Joel

On Fri, Jun 19, 2009 at 11:17 AM, Nexii Malthus <nexiim at googlemail.com>wrote:

> Yes, please start publishing these global stats, ESPECIALLY for custom
> channels, let the client developers see their own crash rates, we could
> REALLY need that.
>
> - Nexii Malthus
>
> On Thu, Jun 18, 2009 at 4:40 PM, Maggie Leber (sl: Maggie Darwin) <
> maggie at matrisync.com> wrote:
>
>>  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
>>
>> _______________________________________________
>> Policies and (un)subscribe information available here:
>> http://wiki.secondlife.com/wiki/SLDev
>> Please read the policies before posting to keep unmoderated posting
>> privileges
>>
>
>
> _______________________________________________
> Policies and (un)subscribe information available here:
> http://wiki.secondlife.com/wiki/SLDev
> Please read the policies before posting to keep unmoderated posting
> privileges
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/sldev/attachments/20090619/be06a00f/attachment-0001.htm