Crashes with 1.10.0.32 - any tips?

I have had a problem with crashing in 1.10.0.32 after about a minute, when flying...

I have set my graphics stuff down, but no improvement yet...

Does anyone have tips on this?

The end of my last log was:

2006-05-24T18:05:01Z WARNING: Octree leaf got invalid object position.
2006-05-24T18:05:03Z WARNING: Could not remove drawable from spatial group
2006-05-24T18:05:03Z WARNING: Could not remove drawable from spatial group
2006-05-24T18:05:03Z WARNING: Could not remove drawable from spatial group
2006-05-24T18:05:03Z WARNING: Could not remove drawable from spatial group
2006-05-24T18:05:03Z WARNING: Could not remove drawable from spatial group


Debug Log:

SL Log: /home/helmut/SecondLife_1_10_0_32/SecondLife/logs/SecondLife.log
Second Life version 1.10.0 build 32
Can't get terse CPU information
RAM: 0
OS: Linux 2.6.13-15.8-default #1 Tue Feb 7 11:07:24 UTC 2006 i686
GL_VENDOR NVIDIA Corporation
GL_RENDERER GeForce 6800 GS/AGP/SSE/3DNOW!
GL_VERSION 2.0.2 NVIDIA 87.56
Allocated 0 bytes of AGP memory
Attempting login as: Angel Sunset
Userserver: 66.150.244.151
AgentID: b95d2297-6626-4946-aeed-7f8699d53308
SessionID: 5ffda4f0-5ad4-42d8-85b2-6840bc30e54b
Viewer exe: /home/helmut/SecondLife_1_10_0_32/bin/secondlife-bin@t^_A^A
Cur path: /home/helmut/SecondLife_1_10_0_32


World Info:
Region: 72.5.12.207:13003:Cosy Cove
Handle:242688:250624

the same here

I am sending in a bug report; I suggest others do that too...

It definitely sems to be a problem with trees...

This is my last crash (with tree deatil set to lowest):

2006-05-24T18:14:11Z INFO: process_crossed_region()
2006-05-24T18:14:11Z WARNING: Octree leaf got invalid object position.
2006-05-24T18:14:11Z WARNING: Octree detected duplicate child center and gave up.
2006-05-24T18:14:11Z WARNING: Failure adding drawable to object partition!
2006-05-24T18:14:11Z WARNING: Octree leaf got invalid object position.
2006-05-24T18:14:11Z WARNING: Octree leaf got invalid object position.
2006-05-24T18:14:11Z WARNING: Could not remove drawable from spatial group
2006-05-24T18:14:11Z WARNING: Octree leaf got invalid object position.
2006-05-24T18:14:11Z WARNING: Octree leaf got invalid object position.
2006-05-24T18:14:11Z WARNING: Could not remove drawable from spatial group
2006-05-24T18:14:11Z WARNING: Could not remove drawable from spatial group
2006-05-24T18:14:11Z INFO: process_agent_movement_complete()
2006-05-24T18:14:11Z INFO: Changing home region to 242688:250624
2006-05-24T18:14:11Z INFO: Moving agent into region: Cosy Cove located at 72.5.12.207:13003
2006-05-24T18:14:11Z INFO: Shifting octree: { 256, 0, 0 }
2006-05-24T18:14:11Z INFO: AssetStorage: Setting upstream provider to 72.5.12.207:13003
2006-05-24T18:14:11Z INFO: Sending throttle settings, total BW 1.5e+06

I had the same problem, try switching the client back to 16mb video ram. Actually, that only allowed me to stay connected for a couple of mins.

2006-05-24T18:21:02Z INFO: Moving agent into region: Kang Nae located at 72.5.12.30:13003
2006-05-24T18:21:02Z INFO: Shifting octree: { 256, 0, 0 }
2006-05-24T18:21:02Z INFO: AssetStorage: Setting upstream provider to 72.5.12.30:13003
2006-05-24T18:21:02Z INFO: Sending throttle settings, total BW 1.5e+06
2006-05-24T18:21:02Z WARNING: !!! OCTREE REMOVING FACE BY ADDRESS, SEVERE PERFORMANCE PENALTY |||
2006-05-24T18:21:02Z WARNING: !!! OCTREE REMOVING FACE BY ADDRESS, SEVERE PERFORMANCE PENALTY |||
2006-05-24T18:21:02Z WARNING: !!! OCTREE REMOVING FACE BY ADDRESS, SEVERE PERFORMANCE PENALTY |||
2006-05-24T18:21:02Z WARNING: !!! OCTREE REMOVING FACE BY ADDRESS, SEVERE PERFORMANCE PENALTY |||
2006-05-24T18:21:02Z WARNING: !!! OCTREE REMOVING FACE BY ADDRESS, SEVERE PERFORMANCE PENALTY |||
2006-05-24T18:21:02Z WARNING: !!! OCTREE REMOVING FACE BY ADDRESS, SEVERE PERFORMANCE PENALTY |||
2006-05-24T18:21:02Z WARNING: Could not remove drawable from spatial group
2006-05-24T18:21:02Z WARNING: !!! OCTREE REMOVING FACE BY ADDRESS, SEVERE PERFORMANCE PENALTY |||
2006-05-24T18:21:02Z WARNING: !!! OCTREE REMOVING FACE BY ADDRESS, SEVERE PERFORMANCE PENALTY |||
2006-05-24T18:21:02Z WARNING: !!! OCTREE REMOVING FACE BY ADDRESS, SEVERE PERFORMANCE PENALTY |||
2006-05-24T18:21:02Z WARNING: !!! OCTREE REMOVING FACE BY ADDRESS, SEVERE PERFORMANCE PENALTY |||
2006-05-24T18:21:02Z WARNING: !!! OCTREE REMOVING FACE BY ADDRESS, SEVERE PERFORMANCE PENALTY |||
2006-05-24T18:21:02Z WARNING: !!! OCTREE REMOVING FACE BY ADDRESS, SEVERE PERFORMANCE PENALTY |||
2006-05-24T18:21:02Z WARNING: !!! OCTREE REMOVING FACE BY ADDRESS, SEVERE PERFORMANCE PENALTY |||
2006-05-24T18:21:02Z WARNING: !!! OCTREE REMOVING FACE BY ADDRESS, SEVERE PERFORMANCE PENALTY |||
2006-05-24T18:21:02Z WARNING: !!! OCTREE REMOVING FACE BY ADDRESS, SEVERE PERFORMANCE PENALTY |||
2006-05-24T18:21:02Z WARNING: !!! OCTREE REMOVING FACE BY ADDRESS, SEVERE PERFORMANCE PENALTY |||
2006-05-24T18:21:02Z WARNING: !!! OCTREE REMOVING FACE BY ADDRESS, SEVERE PERFORMANCE PENALTY |||
2006-05-24T18:21:02Z WARNING: !!! OCTREE REMOVING FACE BY ADDRESS, SEVERE PERFORMANCE PENALTY |||
2006-05-24T18:21:02Z WARNING: !!! OCTREE REMOVING FACE BY ADDRESS, SEVERE PERFORMANCE PENALTY |||
2006-05-24T18:21:02Z WARNING: !!! OCTREE REMOVING FACE BY ADDRESS, SEVERE PERFORMANCE PENALTY |||
2006-05-24T18:21:02Z WARNING: !!! OCTREE REMOVING FACE BY ADDRESS, SEVERE PERFORMANCE PENALTY |||
2006-05-24T18:21:02Z WARNING: !!! OCTREE REMOVING FACE BY ADDRESS, SEVERE PERFORMANCE PENALTY |||
2006-05-24T18:21:02Z INFO: remove_marker_file()

Why wasn't there a Linux client for the preview grid

Doesn't seem to have an effect for me.


Octrees I believe are part of a polygonial sorting mechanism not limited to rendering of in-game trees.


"WARNING: !!! OCTREE REMOVING FACE BY ADDRESS, SEVERE PERFORMANCE PENALTY |||"
(no kidding, performance literally crashes here ;)

Occlusion culling sounds kinda right by this error.
There were murmurings of it being horribly broken earlier on IIRC.

This is just the beginning of a theory, but it seems like a problem with occlusion culling.. if I look over a bare area, I'm good.. the second I look in the direction of a nearby building with things behind it.. I'm dead.

It's not the trees... I walked underwater, and still crashed

latest log, from Bug Report to crash:

2006-05-24T18:18:40Z INFO: Saving snapshot to: report_screenshot.bmp
2006-05-24T18:18:41Z INFO: *** Uploading:
2006-05-24T18:18:41Z INFO: Type: texture
2006-05-24T18:18:41Z INFO: File: report_screenshot.bmp
2006-05-24T18:18:41Z INFO: Dest: /tmp/ab372dd0-d7f0-dba1-6d86-cbdb2b7768d5.tmp
2006-05-24T18:18:41Z INFO: Name: screenshot_name
2006-05-24T18:18:41Z INFO: Desc: screenshot_descr
2006-05-24T18:18:41Z INFO: LLAssetStorage:toreAssetData (legacy)44a2ccd6-d803-e2fa-5d14-9769f52dc0e3:texture
2006-05-24T18:18:41Z INFO: LLAssetStorage:toreAssetData 44a2ccd6-d803-e2fa-5d14-9769f52dc0e3:texture
2006-05-24T18:18:41Z INFO: xfer request id: 9149789278533287429 to 72.5.12.207:13003
2006-05-24T18:18:41Z INFO: starting vfile transfer: 44a2ccd6-d803-e2fa-5d14-9769f52dc0e3,texture to 72.5.12.207:13003
2006-05-24T18:18:42Z INFO: Circuit: 72.5.12.207:13003 resent 9 packets
2006-05-24T18:19:48Z INFO: Got screen shot 44a2ccd6-d803-e2fa-5d14-9769f52dc0e3
2006-05-24T18:21:34Z INFO: Saving snapshot to: report_screenshot.bmp
2006-05-24T18:21:35Z INFO: *** Uploading:
2006-05-24T18:21:35Z INFO: Type: texture
2006-05-24T18:21:35Z INFO: File: report_screenshot.bmp
2006-05-24T18:21:35Z INFO: Dest: /tmp/fd1832b1-c3d4-8285-b74e-40f9502964ec.tmp
2006-05-24T18:21:35Z INFO: Name: screenshot_name
2006-05-24T18:21:35Z INFO: Desc: screenshot_descr
2006-05-24T18:21:35Z INFO: LLAssetStorage:toreAssetData (legacy)cd061e2a-39d6-2419-9b3f-6f0757741fa1:texture
2006-05-24T18:21:35Z INFO: LLAssetStorage:toreAssetData cd061e2a-39d6-2419-9b3f-6f0757741fa1:texture
2006-05-24T18:21:36Z INFO: xfer request id: 17190498359895169699 to 72.5.12.207:13003
2006-05-24T18:21:36Z INFO: starting vfile transfer: cd061e2a-39d6-2419-9b3f-6f0757741fa1,texture to 72.5.12.207:13003
2006-05-24T18:21:42Z INFO: Circuit: 72.5.12.87:13004 resent 4 packets
2006-05-24T18:21:42Z INFO: Circuit: 72.5.12.207:13003 resent 3 packets
2006-05-24T18:23:12Z INFO: Circuit: 72.5.12.87:13004 resent 1 packets

I was in a very heavily treed area when I logged in, I logged into the Mature Sandbox using the new login feature and didn't crash, went to debug menu and turned off trees and now I am logged in.

Looks like this client is DOA, I cannot find any setting combinations that will keep me in world for more than a couple of mins. When it does work local lighting and floppy prims work very well, most impressive...

On the upside, my ctl key works now!

Thanks! One step further... I hope mainstream clients also have this problem - and I am nmot trying to be mean

Looks like we will be bringing a bottle on Saturday, to the LUG meeting

I cannot try this out right now, but anyone try doing CTRL-SHIFT-o (or choosing the associated menu option presuming it exists) and seeing if that makes a difference?

Thanks,

Val

Ok -

1) Clt-shift-O does not seem to work.. Need to get the actual option setting from windows to turn this off

2) The problem with crashing seems to be directly related the complexity of the area around you. I've stayed in SL for a good 10-15 minutes easy, and I'm working on testing longer. Setting graphics memory to what my graphics memory helps. I'm sittin on a platform looking at space, and it seems to be stable.

First try with CTRL SHIFT o - the client runs for a bit, then uses up ALL available memory, X freezes, then it crashes

Well, glad to have made such a wonderful suggestion.

Heh

--Val

Ctrl Shift O doesnt seem to do anything, cant find it in the menu either,
I had a couple of crashes at first, but seem stable now, dont know whats diffrent really.
It does seem to crash whenever I try to teleport, if I loging again it drops me of the place I tped to.
maybe its the amount of objects?
I hope they come with a fix soon

I've taken to setting my far clip way down (like 4) in my .ini

I got in once spent a few moments enjoying the scenery then it crashed. I can get passed the login screen but it crashes before I rez. I did notice some OpenGL errors in the log. . .

2006-05-25T00:24:18Z INFO: Failed to find OpenGL symbol 'glNewObjectBufferATI' in '(default OpenGL library)
2006-05-25T00:24:18Z INFO: Failed to find OpenGL symbol 'glUpdateObjectBufferATI' in '(default OpenGL library)
2006-05-25T00:24:18Z INFO: Failed to find OpenGL symbol 'glFreeObjectBufferATI' in '(default OpenGL library)
2006-05-25T00:24:18Z INFO: Failed to find OpenGL symbol 'glArrayObjectATI' in '(default OpenGL library)
2006-05-25T00:24:18Z INFO: Failed to find OpenGL symbol 'glVertexAttribArrayObjectATI' in '(default OpenGL library)
2006-05-25T00:24:18Z INFO: Loaded OpenGL symbol 'glXGetCurrentDisplay'.
2006-05-25T00:24:18Z INFO: Loaded OpenGL symbol 'glXQueryExtensionsString'.
2006-05-25T00:24:18Z INFO: Loaded OpenGL symbol 'glXGetProcAddressARB'.
2006-05-25T00:24:18Z INFO: Couldn't initialize mipmap generation
2006-05-25T00:24:18Z INFO: Couldn't initialize GL_EXT_paletted_texture
2006-05-25T00:24:18Z INFO: Couldn't initialize GL_NV_vertex_array_range
2006-05-25T00:24:18Z INFO: Couldn't initialize GL_NV_fence
2006-05-25T00:24:18Z INFO: Couldn't initialize separate specular color
2006-05-25T00:24:18Z INFO: Couldn't initialize anisotropic filtering
2006-05-25T00:24:18Z INFO: Couldn't initialize GL_ARB_occlusion_query
2006-05-25T00:24:18Z INFO: Couldn't initialize GL_ARB_shader_objects
2006-05-25T00:24:18Z INFO: Couldn't initialize GL_ARB_vertex_shader
2006-05-25T00:24:18Z INFO: Couldn't initialize GL_ARB_fragment_shader
2006-05-25T00:24:18Z INFO: Restoring GL during resolution change
2006-05-25T00:24:18Z INFO: Restoring GL...
2006-05-25T00:24:18Z INFO: Rebuilding bitmap for glyph
2006-05-25T00:24:18Z INFO: Rebuilding bitmap for glyph
2006-05-25T00:24:18Z WARNING: Couldn't load font ヒラギノ角ゴ Pro W3.otf
2006-05-25T00:24:18Z INFO: Rebuilding bitmap for glyph
2006-05-25T00:24:18Z WARNING: Couldn't load font ヒラギノ角ゴ Pro W3.otf
2006-05-25T00:24:18Z INFO: Rebuilding bitmap for glyph
2006-05-25T00:24:18Z WARNING: Couldn't load font ヒラギノ角ゴ Pro W3.otf
2006-05-25T00:24:18Z INFO: Rebuilding bitmap for glyph
2006-05-25T00:24:18Z WARNING: Couldn't load font ヒラギノ角ゴ Pro W3.otf
2006-05-25T00:24:18Z INFO: Rebuilding bitmap for glyph
2006-05-25T00:24:18Z WARNING: Couldn't load font ヒラギノ角ゴ Pro W3.otf

I also see the Octree leaf warning.


Just an FYI for whoever might be reading these.

I found turning off Occlusion helped me alot.. its not 100%, but I can survive on the ground in a moderately primmy area that I wouldnt last in for long before..

If shift-ctl-O doesnt work to turn off occlusion, add:
UseOcclusion FALSE
to you settings.ini.. Note that between UseOcclusion and FALSE, is a tab, not spaces.

I'm still experimenting, but I'm pretty sure it'll make things more survivable.

If all else fails, fly up until there's not alot of prims around you..
I made a platform at 500m and hung up there with no problem for a long time.

There are quite a few bugs in this one. Either SL itself closes or it brings the whole system down.
System goes down with this:

May 24 18:22:30 localhost kernel: [ 304.136023] secondlife-bin[5430] trap invalid operand rip:55d083f8 rsp:ffffbf2c error:0

Or there are octree errors which seem to be used the calculate shadows. No option to kill shadows, that makes me sad. Look in the debug menu for octree, draws all sorts of boxes and pretty things to look at but I have found little explaining more on that other than searching the forum. Runitai Linden made a post on the 5th about such things, though it is not related to this bug. Just a bit of info on octree. The exe is not a debug version so it is rather hard to discover what the problem is here but a total system lock up is a bummer.

Ubuntu Dapper 6.06 Athon64 X2, Geforce 7900GT.

--ADD

Enabling 'Debug Permissions' seems to help keeping the octree from being the souce of a crash and the other lockup as well. Slight penalty in frame rate. Though sometimes it appears the simulator double logs and boots the user. Also, change to night time. The sun seems to cause a lockup.

It seems others have a problem too. The OSX people have been told SL is broken, a new release (including octet trees problems) is on its way.

I am still sorry they did not include a linux preview!

The Linux Users in my experience test hard and report well; if they had had us in preview, we could have caught this LONG ago! (Except for the "last minute fix - we would have caught that at the last minute )

It seems SL removes the line from my settings.ini if I add it
Yes I did use a TAB not spaces.
I'll try playing iwth it some more. does it need to be at a specific line?

I agree.

Thank you! This is very useful!

Maybe we wil be included in the Mac OS X update, scheduled Friday. I HOPE so!

I was in SL Linux with the new 8762 drivers, did not move much, just editing (adding Light to my lights ), and it crashed once after 5 minutes, and then was stable for 25 minutes, when I logged out.

And that was before using the "Debug Permissions" setting.

We are CLOSE to a stable release, but not there yet.

1.10 rocks, from the features