Second Life Forums Archive - States and free memory bugs

Cory Linden

Linden Lab Employee

Join date: 19 Nov 2002

Posts: 173

04-01-2004 09:55

I ran Christopher Omega's state transition script and didn't see any of the problems that he reported. Christopher, perhaps if you're one line we could take a look at the problem at the same time to see if it is related to network issues.

On llGetFreeMemory, I just ran several spin down scripts that slowly ate up their internal memory. They seemed to perform as expected, so if someone has a simple example of the Stack-Heap collision problem when the free memory is reporting 8k, I'd really appreciate it either being posted or sent to me. Note that stack-heap collisions can also be a sympton of a different class of bugs, so simple repro cases are extremely helpful.

Thanks!
Cory

Huns Valen

Don't PM me here.

Join date: 3 May 2003

Posts: 2,749

Re: States and free memory bugs

04-03-2004 14:23

From: someone

Originally posted by Cory Linden
On llGetFreeMemory, I just ran several spin down scripts that slowly ate up their internal memory. They seemed to perform as expected, so if someone has a simple example of the Stack-Heap collision problem when the free memory is reporting 8k, I'd really appreciate it either being posted or sent to me. Note that stack-heap collisions can also be a sympton of a different class of bugs, so simple repro cases are extremely helpful.

Thanks!
Cory

sent

_____________________

[ huns? || words || 1TBS KREW || VHI Aircraft || Whitepaper on Aircraft Physics ]

Make yourself and your objects immune to llPushObject().

Kex Godel

Master Slacker

Join date: 14 Nov 2003

Posts: 869

04-03-2004 18:32

Keep in mind that if you write a short program to eat up memory, the problem won't be visible.

The problem occurs when you have a bunch of code written, because the compiled code seems to be what's not factored in to the free memory size.

Huns Valen

Don't PM me here.

Join date: 3 May 2003

Posts: 2,749

04-03-2004 21:59

From: someone

Originally posted by Kex Godel
Keep in mind that if you write a short program to eat up memory, the problem won't be visible.

The problem occurs when you have a bunch of code written, because the compiled code seems to be what's not factored in to the free memory size.

DING DING DING

_____________________

[ huns? || words || 1TBS KREW || VHI Aircraft || Whitepaper on Aircraft Physics ]

Make yourself and your objects immune to llPushObject().

States and free memory bugs
Cory Linden Linden Lab Employee Join date: 19 Nov 2002 Posts: 173	04-01-2004 09:55 I ran Christopher Omega's state transition script and didn't see any of the problems that he reported. Christopher, perhaps if you're one line we could take a look at the problem at the same time to see if it is related to network issues. On llGetFreeMemory, I just ran several spin down scripts that slowly ate up their internal memory. They seemed to perform as expected, so if someone has a simple example of the Stack-Heap collision problem when the free memory is reporting 8k, I'd really appreciate it either being posted or sent to me. Note that stack-heap collisions can also be a sympton of a different class of bugs, so simple repro cases are extremely helpful. Thanks! Cory
Huns Valen Don't PM me here. Join date: 3 May 2003 Posts: 2,749	Re: States and free memory bugs 04-03-2004 14:23 From: someone Originally posted by Cory Linden On llGetFreeMemory, I just ran several spin down scripts that slowly ate up their internal memory. They seemed to perform as expected, so if someone has a simple example of the Stack-Heap collision problem when the free memory is reporting 8k, I'd really appreciate it either being posted or sent to me. Note that stack-heap collisions can also be a sympton of a different class of bugs, so simple repro cases are extremely helpful. Thanks! Cory sent _____________________ [ huns? \|\| words \|\| 1TBS KREW \|\| VHI Aircraft \|\| Whitepaper on Aircraft Physics ] Make yourself and your objects immune to llPushObject().
Kex Godel Master Slacker Join date: 14 Nov 2003 Posts: 869	04-03-2004 18:32 Keep in mind that if you write a short program to eat up memory, the problem won't be visible. The problem occurs when you have a bunch of code written, because the compiled code seems to be what's not factored in to the free memory size.
Huns Valen Don't PM me here. Join date: 3 May 2003 Posts: 2,749	04-03-2004 21:59 From: someone Originally posted by Kex Godel Keep in mind that if you write a short program to eat up memory, the problem won't be visible. The problem occurs when you have a bunch of code written, because the compiled code seems to be what's not factored in to the free memory size. DING DING DING _____________________ [ huns? \|\| words \|\| 1TBS KREW \|\| VHI Aircraft \|\| Whitepaper on Aircraft Physics ] Make yourself and your objects immune to llPushObject().

Welcome to the Second Life Forums Archive

States and free memory bugs