> Data is collected about viewer sessions that end in a successful logout, and
> it's examined in much the manner you propose. I believe the aggregate data
> is shared with Third Party Viewer teams and/or at the Open Source office
> hours. I'm not sure if the lab has shared a recent breakdown again
Not that I have allot of standing to voice my thoughts in the matter, but I
would like to see some detailed stats and some analysis on other things besides
crashes. Freezes, disconnects, stalls, and memory usage come to mind. In fact
more then just analysis, I would love to see some cutting a
Good to hear. But I was also thinking of the graphics settings. There are
all those proven and unproven theories about VBO on, but not with AA, and
only on alternate TuesdaysI know I have some of them myself. I have
convinced myself that VBO is bad on my ATI 2600Pro iMac.
On Tue, Aug 9, 2
---
This is an automatically generated e-mail. To reply, visit:
http://codereview.secondlife.com/r/435/#review960
---
Ship it!
Looks good -- make sure to ask QA to do a performance A/
On Mon, Aug 8, 2011 at 9:24 AM, Lee ponzu wrote:
> I just had a sort of strange idea, but maybe this is alrady common
> practice. Just thought I would ask.
>
> Collect data about viewers that didn't crash. After some time cutoff, send
> the didn't crash data (with permission of the user, of cou
It's not a daft idea. It's good science.
On 9/08/2011 2:24 AM, Lee ponzu wrote:
> I just had a sort of strange idea, but maybe this is alrady common
> practice. Just thought I would ask.
>
> Collect data about viewers that didn't crash. After some time cutoff,
> send the didn't crash data (with
---
This is an automatically generated e-mail. To reply, visit:
http://codereview.secondlife.com/r/435/
---
Review request for Viewer and David Parks.
Summary
---
Fixed a crash c
