adult crash heap error

[Orridion]

hi does any one know how to fix this error?

It's NOT Mine! Complete Body ***** System [script:~INM ***** Voyeur v3.6.4] Script run-time error
Stack-Heap Collision

[Frionil Fang]

That basically means the script has run out of memory. It could be due to a programming error or unexpected conditions, and there's not a lot an end-user can do to fix it:

• If the object is modifiable, scripts inside it can be reset (even if the script itself isn't modifiable). Open the object with the build tool, go to the Content tab. Depending on your viewer you may need to open the script (it'll tell you you're not allowed to view it, but you should be able to press the Reset button) or just click "Reset Scripts" in the object contents window directly, or possibly viewer's Build menu->Scripts->Reset scripts.
• If the object is not modifiable, you need a fresh copy that has a non-crashed script. If the object is copiable, rezzing it and duplicating it inworld (not in inventory!) via shift-dragging or control-D should create a copy with a restarted script. If all else fails, get a redelivery.

Naturally, if any settings were stored only in the script's memory and not saved in some kind of more permanent storage, they will be lost.

Edited October 20, 2023 by Frionil Fang

[Rolig Loon]

If that's not your script, you probably don't have permission to view it or modify it, so the short answer is that you can't "fix" it.  Frionil is right. Your script has run out of memory, probably because it has been saving information in internal lists and it has saved so much information that it is choking on it. I doubt that you will be able to reset the script by the methods Frionil suggests, but go ahead and try anyway. If you don't have permission, the reset options should not be available for you. You will need to rez a fresh copy of the script.

[Orridion]

Tried a redeliver and ran into the same issue i guess the script is just broken?

 

[Rolig Loon]

10 minutes ago, Orridion said:

Tried a redeliver and ran into the same issue i guess the script is just broken?

Unlikely, although you should probably contact the scripter directly to see if s/he has any suggestions (or has perhaps been working on an update). It's more likely that you are accidentally overloading it somehow.  Trying to feed it too much data? Feeding it data in the wrong format? Unfortunately, since you can't see the script itself there's no way you can do the sort of debugging that would give you clues about why it's overloading.

[Love Zhaoying]

Oh..I finally realized, it's the "It's Not Mine" system. (Not that it was "not the OP's script".)

Funny how that system comes up on occasion, in different contexts!

[Quistess Alpha]

11 hours ago, Orridion said:

Voyeur

I'm not familiar with that specific part of the product, but if it involves looking into people's RLV folders, then looking at someone who's RLV folders have a lot of children directly under the root folder (not uncommon for people who really like to play with "traps" that add folders directly) can easily crash anything that isn't extremely careful with its memory management.