Welcome to the Second Life Forums Archive

These forums are CLOSED. Please visit the new forums HERE

Broken script within the last 24 hours.

Yingzi Xue
Registered User
Join date: 11 Jun 2008
Posts: 144
09-04-2008 06:48
Has anyone else noticed a stack heap collision on a notecard reading script? I have a script I've just put on the market that worked fine up until yesterday. I made no changes and I've done a lot with it, but now when I reset the script I get a stack collision error. It just stopped working without any changes. And there's plenty of room left in memory after the notecard is read. I've tried different locations and the same thing happens.
Gregory McLeod
Registered User
Join date: 21 Oct 2006
Posts: 278
09-04-2008 08:39
Is it possible that your region which has server 1.24.4 has broken it?
Yingzi Xue
Registered User
Join date: 11 Jun 2008
Posts: 144
09-04-2008 10:05
I'm starting to think the prim got bugged. I took it to a sandbox and tried it there. Same thing happened. I even created a new prim and put the script in it and got a heap collision. Then two hours later I tried it again in the original prim and it gave the same error. I tried it in a new prim and suddenly it works fine. Something flakey is going on.
Lear Cale
wordy bugger
Join date: 22 Aug 2007
Posts: 3,569
09-04-2008 11:04
Actually, after a sim was upgraded to 1.24 server, I did see a stack-heap error on a product that I know is running close to the edge, but that I'd never seen the error on previously. Perhaps the new sim takes a bit of extra script memory, or checks differently.
Very Keynes
LSL is a Virus
Join date: 6 May 2006
Posts: 484
09-04-2008 12:09
I got a Stack-Heap Collision on a device that has run non stop for 2 years. I just opened it in RC0 and recompiled with the MONO flag, been ok for 2 hours so far, so with luck that fixed it. But I am far from convinced that LL have not changed the LSL runtime despite my being shot down in other threads where I have asked about that.
Yingzi Xue
Registered User
Join date: 11 Jun 2008
Posts: 144
09-04-2008 15:47
I tried recompiling mine to MONO right after it happened and I still got the stack heap collision, with only 29k used. I ended up having to delete the prim I was using because it was somehow bugged. I knew something was wrong when I used an old version of my script (which I had used hundreds of times without incident) and it did the same thing. Somewhere between the time I was freaking out and an hour or so later they fixed the issue. I took my primary product offline because I thought it was faulty. Lets just hope the problem doesn't come back.