• All submissions to this site are governed by Second Life Project Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.
Issue Details (XML | Word | Printable)

Key: SVC-1118
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Critical Critical
Assignee: Unassigned
Reporter: Nexeus Fatale
Votes: 2
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
2. Second Life Service - SVC

objects with descriptions set to over 127 characters by a LSL script cause the object to become unstable (affects vary)

Created: 26/Dec/07 08:39 PM   Updated: 02/Feb/08 11:39 PM
Return to search
Component/s: Scripts
Affects Version/s: None
Fix Version/s: None

Environment:
Second Life 1.18.6 (76116) Dec 19 2007 09:54:25 (Second Life WindLight)

You are at 261779.7, 256749.5, 57.6 in Skiddaw located at sim60.agni.lindenlab.com (64.154.220.27:12035)
Second Life Server 1.18.6.75511

CPU: AMD (Unknown model) (2211 MHz)
Memory: 2048 MB
OS Version: Microsoft Windows XP Service Pack 2 (Build 2600)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce 8500 GT/PCI/SSE2/3DNOW!
OpenGL Version: 2.1.1
LLMozLib Version: 1.1.0 (Mozilla GRE:1.8.0.12_0000000000)
Packets Lost: 31/86375 (0.0%)
Viewer Digest: 6b35fccc-b104-8755-e4b8-145f94ebc10d
Issue Links:
Relates
 


 Description  « Hide
After placing more than 127 characters into an objects description while using an script the object becomes unstable, observed results include:
  • Fields in the object unable to be edited
  • Object is returned from negative locations

The object 'Second Life' has sent you a message from Second Life:
Your 5 objects have been returned to your inventory lost and found folder near parcel 'Serenity Park ~ By Alyssa Bijoux ' at Skiddaw 1.9e-05, -0.000443 because it went off-world.

= Second Life is owned by (unknown)
= Location unknown.

The object 'Second Life' has sent you a message from Second Life:
Your 5 objects have been returned to your inventory lost and found folder near parcel 'Serenity Park ~ By Alyssa Bijoux ' at Skiddaw 6e-06, 0.066284 because it went off-world.

= Second Life is owned by (unknown)
= Location unknown.

The object 'Second Life' has sent you a message from Second Life:
Your 5 objects have been returned to your inventory lost and found folder near parcel 'Prim Works Store' at PrimWorks -0.00032, -8e-06 due to parcel auto return.

= Second Life is owned by Prim Works
= Location unknown.

The object 'Second Life' has sent you a message from Second Life:
Your 5 objects have been returned to your inventory lost and found folder near parcel 'Prim Works Store' at PrimWorks 0, 4e-06 due to parcel auto return.

= Second Life is owned by Prim Works
= Location unknown.

 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
[ Permlink | « Hide ]
Drew Dwi added a comment - 02/Jan/08 09:42 AM
can't repro this issue, believe this has something to do with your script or where your dropping the objects.

[ Permlink | « Hide ]
Nexeus Fatale added a comment - 04/Jan/08 07:56 PM
So I think I found the root of it. It has to deal with when a script adds more than information into the description section of an object. Somethings causes the object to just go haywire.

[ Permlink | « Hide ]
Celierra Darling added a comment - 04/Jan/08 10:27 PM
Reopening and linking to SVC-186 based on last comment.

[ Permlink | « Hide ]
Celierra Darling added a comment - 04/Jan/08 10:29 PM
What exactly do you mean by "more than information"?

[ Permlink | « Hide ]
Celierra Darling added a comment - 04/Jan/08 10:31 PM
(moving down to critical for now, perhaps back up if there's more evidence of prim corruption)

[ Permlink | « Hide ]
Nexeus Fatale added a comment - 04/Jan/08 10:44 PM
So, descriptions are limited to 127 characters. It seems that if a script attempts to force more than 127 characters into an the description section of an object, something very weird happens at that point, in both my testing, two objects became un-editable - I could not edit the description - these two objects were always routinely returned to me.

There is also a possibility that the # causes some problems, but I haven't tested, or tried that out yet.


[ Permlink | « Hide ]
Drew Dwi added a comment - 05/Jan/08 08:54 AM - edited
this I have reproduced we should change the title to reflect the error.

objects with descriptions set to over 127 characters by a LSL script cause the object to become unstable (affects vary)?

the LSL code should throw an error, or SL should auto crop extra characters to prevent unintended side effects.


[ Permlink | « Hide ]
Nexeus Fatale added a comment - 05/Jan/08 10:00 AM
That's a great idea, title changed to better reflect the issue.

I think one way to handle it is one of a few things:
1) Increase the amount of space that the description field can hold
2) Change the behavior of llSetObjectDesc so that it automatically trims the string to 127
3) Create a separate object field for script data - a place where script can hold bits of information.

The reason I suggest 3 is because most scripters are using the description area as a place to hold script information about the object (being as you can't really write to a note card). It could be a solution to have a separate area to hold specific information for scripts.

Also, I wonder - does the same thing happen to the object name field?


[ Permlink | « Hide ]
Nexeus Fatale added a comment - 05/Jan/08 10:03 AM
Description of the problem was also updated.


[ Permlink | « Hide ]
Celierra Darling added a comment - 02/Feb/08 11:39 PM
This seems to have been fixed - see http://blog.secondlife.com/2008/02/01/scripters-object-name-and-description-changes/ .


Powered by Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.13.2-#335) - Bug/feature request - Atlassian news - Contact Administrators