0001582: DotNetEngine throws System.OverflowException with "Value exceeds 1500 characters"

(0003286)
melanie (administrator)
2008-06-23 06:36

This is caused by the compile errors being more than 1500 chars long. The system attempts to display it inworld, and libsl throws that exception.

(0003292)
mikem (developer)
2008-06-23 18:29

You might want to try debugging your script. See at which point it fails to compile or run.

If you're unable to narrow it down to a simple example, you can try posting the script here for someone else to have a look.

(0003796)
matth (reporter)
2008-07-15 10:45

I was just looking at/thinking about this issue. This script will cause the error:

default{
    state_entry()
    {
        not_defined0=0;
        not_defined1=0;
        not_defined2=0;
        not_defined3=0;
        not_defined4=0;
        not_defined5=0;
        not_defined6=0;
        not_defined7=0;
        not_defined8=0;
        not_defined9=0;

        not_defined10=0;
        not_defined11=0;
        not_defined12=0;
        not_defined13=0;
        not_defined14=0;
    }
}

What is the right way to handle this? Certainly throwing a server exception and doing nothing on the client isn't ideal. Is the 1500 character limit a hard limit from the SL client? At least, perhaps the error message could be truncated or broken into sections and sent. What do the developers think?

(0003803)
mikem (developer)
2008-07-15 18:26

There was a bug in handling the compiler's error message. For one reason or another, a message sent to the user in-world is limited to 1500 characters. In case the compiler returned more than 1500 characters in error messages, the string was truncated to 1501 characters, which cause the exception.

The fix ix to truncate to 1500 characters. Now the compiler errors are relayed to the user in-world.

Committed in r5483.

Issue History
Date Modified	Username	Field	Change
2008-06-23 04:34	woqpalsk	New Issue
2008-06-23 04:34	woqpalsk	SVN Revision	=> 0
2008-06-23 04:34	woqpalsk	Run Mode	=> Standalone (1 Region)
2008-06-23 04:34	woqpalsk	Physics Engine	=> BasicPhysics
2008-06-23 04:34	woqpalsk	Environment	=> Mono / Windows
2008-06-23 06:36	melanie	Note Added: 0003286
2008-06-23 18:29	mikem	Note Added: 0003292
2008-06-23 18:29	mikem	Issue Monitored: mikem
2008-07-15 10:45	matth	Note Added: 0003796
2008-07-15 18:26	mikem	Status	new => resolved
2008-07-15 18:26	mikem	Fixed in Version	=> SVN
2008-07-15 18:26	mikem	Resolution	open => fixed
2008-07-15 18:26	mikem	Assigned To	=> mikem
2008-07-15 18:26	mikem	Note Added: 0003803
2008-07-15 18:27	mikem	Status	resolved => closed

Notes
(0003286) melanie (administrator) 2008-06-23 06:36	This is caused by the compile errors being more than 1500 chars long. The system attempts to display it inworld, and libsl throws that exception.

(0003292) mikem (developer) 2008-06-23 18:29	You might want to try debugging your script. See at which point it fails to compile or run. If you're unable to narrow it down to a simple example, you can try posting the script here for someone else to have a look.

(0003796) matth (reporter) 2008-07-15 10:45	I was just looking at/thinking about this issue. This script will cause the error: default{ state_entry() { not_defined0=0; not_defined1=0; not_defined2=0; not_defined3=0; not_defined4=0; not_defined5=0; not_defined6=0; not_defined7=0; not_defined8=0; not_defined9=0; not_defined10=0; not_defined11=0; not_defined12=0; not_defined13=0; not_defined14=0; } } What is the right way to handle this? Certainly throwing a server exception and doing nothing on the client isn't ideal. Is the 1500 character limit a hard limit from the SL client? At least, perhaps the error message could be truncated or broken into sections and sent. What do the developers think?

(0003803) mikem (developer) 2008-07-15 18:26	There was a bug in handling the compiler's error message. For one reason or another, a message sent to the user in-world is limited to 1500 characters. In case the compiler returned more than 1500 characters in error messages, the string was truncated to 1501 characters, which cause the exception. The fix ix to truncate to 1500 characters. Now the compiler errors are relayed to the user in-world. Committed in r5483.

Relationships