[BUG-133987] "Unable to create object ' ' that caused problems on this region" error flooding our Homestead, preventing us to rez objects

[sl-service-account]

Steps to Reproduce

I was logging into SL when it suddenly happened on our rented homestead. The first thing i noticed was that my avatar didn't load properly. i tried rezzing objects on the ground: Rezzing from inventory didn't work anymore. Building new objects on the other hand worked perfectly fine. So I went to the sim of our Rental estate company to get some help. On their sim my Character rezzed completely (mesh clothing, prim objects, etc). I asked them for help. They restarted the sim. I went back home: everything back to normal, but not for long...

Actual Behavior

Unable to create item '' that has caused problems on this region Unable to create item '' that has caused problems on this region Unable to create item '' that has caused problems on this region Unable to create item '' that has caused problems on this region Unable to create item '' that has caused problems on this region Unable to create item '' that has caused problems on this region Unable to create item '' that has caused problems on this region Unable to create item '' that has caused problems on this region Too many errors... dropping further messages until the flood stops

This is flooding us for the last weeks. We cannot find the source, since the message displays a blank as object. Rezzing is no longer possible, putting on clothes is no longer possible.

Expected Behavior

I was expecting, that by restarting the sim, the error would disappear. But well, the next day, everything is flooded with this message again. Same Error, same problems, same issues.

Other information

We don't know what to do, in order to solve this issue on our own. The message didn't give us exact information on what is causing this flood. We really need help, since it's ruining our experiences with SecondLife. Is there any way to fix this in an upcoming patch?

Original Jira Fields

| Field | Value | | ------------- | ------------- | | Issue | BUG-133987 | | Summary | "Unable to create object ' ' that caused problems on this region" error flooding our Homestead, preventing us to rez objects | | Type | Bug | | Priority | Unset | | Status | Needs More Info | | Resolution | Unresolved | | Reporter | KainHawkins (kainhawkins) | | Created at | 2017-07-10T01:53:50Z | | Updated at | 2017-07-21T22:35:14Z | ``` { 'Business Unit': ['Platform'], 'Date of First Response': '2017-07-10T00:18:00.318-0500', "Is there anything you'd like to add?": "We don't know what to do, in order to solve this issue on our own. The message didn't give us exact information on what is causing this flood.\r\nWe really need help, since it's ruining our experiences with SecondLife.\r\nIs there any way to fix this in an upcoming patch?", 'ReOpened Count': 0.0, 'Severity': 'Unset', 'System': 'SL Simulator', 'Target Viewer Version': 'viewer-development', 'What just happened?': "Unable to create item '' that has caused problems on this region\r\nUnable to create item '' that has caused problems on this region\r\nUnable to create item '' that has caused problems on this region\r\nUnable to create item '' that has caused problems on this region\r\nUnable to create item '' that has caused problems on this region\r\nUnable to create item '' that has caused problems on this region\r\nUnable to create item '' that has caused problems on this region\r\nUnable to create item '' that has caused problems on this region\r\nToo many errors... dropping further messages until the flood stops\r\n\r\nThis is flooding us for the last weeks. We cannot find the source, since the message displays a blank as object. Rezzing is no longer possible, putting on clothes is no longer possible.\r\n", 'What were you doing when it happened?': "I was logging into SL when it suddenly happened on our rented homestead.\r\nThe first thing i noticed was that my avatar didn't load properly. i tried rezzing objects on the ground: Rezzing from inventory didn't work anymore. Building new objects on the other hand worked perfectly fine.\r\nSo I went to the sim of our Rental estate company to get some help. On their sim my Character rezzed completely (mesh clothing, prim objects, etc). I asked them for help. They restarted the sim. I went back home: everything back to normal, but not for long...", 'What were you expecting to happen instead?': 'I was expecting, that by restarting the sim, the error would disappear. But well, the next day, everything is flooded with this message again. Same Error, same problems, same issues.\r\n', 'Where': 'http://maps.secondlife.com/secondlife/Blue%20Coral%20Sea/200/39/2227', } ```

[sl-service-account]

Whirly Fizzle commented at 2017-07-10T05:18:00Z

Hiya Kain,

Your region is suffering from BUG-772. The Memory Allocated on the region is currently 416.5 MB, which is way over the limit for a Homestead region. When the memory is over the limit, the region shuts down the ability to rez to protect itself. You will be able to build fresh prims via the build tool, but those prims will have no physics.

You can see the Memory Allocated reading in the viewer statistics: CTRL+SHIFT+1 -> Simulator -> Physics Details -> Memory Allocated. On a Homestead region, once the Memory Allocated reading gets to ~230MB, this problem will happen. The only fix is to restart the region.

Since this problem keeps happening again after restarting the region, you need to find what's causing the memory to run out so quickly. The usual cause of this is the navmesh being constantly dirtied & rebaking, caused by lots of terraforming. Has anyone on the region been doing lots of terraforming? Check that there is not a land flattener tool left rezzed out on the region or buried in the terrain.

[sl-service-account]

KainHawkins commented at 2017-07-10T09:25:24Z

That could be it, our neighbors left and the sim got flatened on the remaining parcels (except ours) But what really strange is, that the object that is supposed to cause it is displayed as a Blank ' ' as mentioned in my description. Therefore finding the culprit for this flooding is nearly impossible for a person like me, with basic knowledge about such stuff. isn't there some kind of Script reset tool, script stop tool or atleast some kind of tracking device? Just something to find the Object that's causing it. I already tried to search the entire sim for invisible stuff (with the "show invisible objects" command). We found nothing on our side, but also seem to cannot enter the other parcels

[sl-service-account]

Whirly Fizzle commented at 2017-07-10T20:34:50Z

I just went back to look at your region & the navmesh was dirty & prompting for a rebake. The memory allocated is only at 70MB currently, but the region was restarted 9 hours ago.

I did have a look yesterday to see if I could see a land flattener object on the region & I couldn't see one.

The object giving you the error messages was likely worn on your avatar. That object isn't the cause of the problem, it's just giving the script error because of the state of the region at the time. I think any attachment that's scripted will give that error message when the region is in this state. The attachment may have no name/blank name, you can set an object to have no name with a script.

Keep an eye on the Memory Allocated reading in stats & see if it starts going above 70MB.

[sl-service-account]

KainHawkins commented at 2017-07-11T10:58:53Z, updated at 2017-07-11T11:09:13Z

So, if I understood that correctly. There might be an Object on my avatar (or my wife's) that is constantly activating a script that fills the Memory? Does that mean it attempts to rez something, or requests to rez? Or what is filling this parameter? (Trying to understand the mechanic behind it) Because if so, I might have a vague guess what might cause it. I'll keep you informed if my theory is true.

On the other hand, the Sim is already flooded in errors when i come online or my wife does, which means It continues even if i'm not around. So that could mean, that it might not be an attachment in the first place.

I'll make some tests and we'll see :)

[sl-service-account]

Whirly Fizzle commented at 2017-07-11T18:29:55Z

I went back to check the region & the memory Allocated reading is still stable at 70MB & the region hasn't been restarted since I checked yesterday. Just to clarify - are you still seeing these "Unable to create item '' that has caused problems on this region" errors today? If you are then it's not caused by the region being out of memory.

[sl-service-account]

Mazidox Linden commented at 2017-07-12T16:46:55Z

Hi Kain,

Could you clarify as Whirly asked above if you are still seeing this issue even after the most recent region restart?

[sl-service-account]

KainHawkins commented at 2017-07-13T04:23:04Z

It's still at 70Mb. No Errors. It seems we found the culprit: A Mesh avatar of mine might have had a script malfunction with a texture applier. It constantly attempted to retexture my avatar to the same colour. So, now that i switched back to an older avatar without mesh, the error seems to be fixed. I will still run some tests though, if it's really that applier that is always causing it or if it's just a coincedence that this script went on a rampage (like a hang up or execution error loop). We'll see :) I'll keep you informed ;)

[sl-service-account]

Whirly Fizzle commented at 2017-07-13T04:41:47Z

Oh interesting. Can you switch back to wearing the possible repro avatar/applier & see if the errors come back?

[sl-service-account]

KainHawkins commented at 2017-07-21T16:11:23Z

I switched back to the avatar that was causing it, nothing, the Physical memory didn't change or rise in any way. It seems like changing the avatar fixed it. Makes it hard to recreate the issue.

[sl-service-account]

Mazidox Linden commented at 2017-07-21T22:35:12Z

Hi KainHawkins,

In order to effectively find the source of this problem, we'll need an outfit (or other potential cause) of this issue. If you find it happening again, please comment with as much information as you can provide about the issue, and click the Info Provided button above.