This is what it is in the documentation. So it is always better to llSetTimerEvent(0.0) before exiting the state.

Here is an example of a script that crashes now in LSL2 that worked fine before. I routinely tell people that a "trick" in their scripts is to simply change states to clear their listeners. Here is an example of a script that now crashes right away in LSL2VM:

// ----------------------------
integer n=0;

default
{
state_entry()

}

state state2
{
state_entry()

}
// ----------------------------

default
{
state_entry()

touch_start(integer total_number)

listen(integer channel, string name, key id, string message) { llSay(0, "heard: " + message); }
}

state nolisten {

touch_start(integer num) { state default; }
}

Here's what happens when I run it:

[17:32] Lex Neva: Hi!
[17:32] Object: heard: Hi!

[I touch it, switching to state "nolisten"

[17:32] Lex Neva: This
[17:32] Lex Neva: should
[17:32] Lex Neva: not
[17:32] Lex Neva: trigger
[17:32] Lex Neva: events

(I touch it, switching back to state default)

[17:32] Object: heard: This
[17:32] Object: heard: should
[17:32] Object: heard: not
[17:32] Object: heard: trigger
[17:32] Object: heard: events

Not only is the listen still there, events are queueing up and not disappearing. Not only THAT, but they're staying in the queue through a state transition (another thing LSL2 didn't do before) and triggering when I switch to a state with a listen event.

I'm upgrading this to showstopper because this is two very significant changes in how LSL behaves. Each alone would break a lot of existing content.

Please fix this soon

A work around, define a global and store the listen handle then add a llListenRemove in state_exit

Not that requiring another global is a good fix, but....

It would be nice if, while fixing this one, the error message could be placed in the script error log??

Here is the code I checked this with:

// Simple script to demo that listens are no longer removed with state change, this is a HUGE problem!!!
// SKunkie Designs, killing lag one avie at a time!!

default
{
state_entry()

listen( integer Chan, string Name, key User, string Msg )
{
if (Msg=="test")

}
touch_start(integer total_number)

on_rez(integer start_params)

}
state Listen
{
state_entry()

listen( integer Chan, string Name, key User, string Msg )
{
if (Msg=="test")

}
}

=======

After running several tests with listen and sensor, I would say the fix that's running on aditi is looking good.
Only SVC-3036 "Listen event survives 'Script not running' setting" is still occurring.
Please visit aditi to verify.

Good news!! the new version Second Life Beta Server 1.24.4.95981 elemininate this bug!

Please follow with a quick rollback on the grid it is a major issue breaking alot of items! all of my products are affected.

The real question is how did they manage to break it? )

all my costumers leave my service ;( pls fix it ............