Error: System is out of GPU and shared host memory #90440

New Issue

Alston Jones · 2021-08-04T22:08:51+02:00

Alston Jones commented

2021-08-04 22:08:51 +02:00

System Information
Operating system: Windows 10
Graphics card: RTX 3070

Blender Version
Broken: (2.93.2)
Worked: (2.93.2, 3.0, K-Cycles 2.93, 3.0)

Short description of error
I have a scene using the addons Physical Starlight and Atmosphere (1.4 beta version), Graswald and a couple of botaniq trees. I have been having this issue for a while and I have tested it in various versions. I go to render a frame in cycles and it gets stuck on "Updating Lights, Computing distribution" and then gives me the error message in the title. It seems that the clouds from the Physical Starlight addon might be causing the problem but I'm surprised that my gpu can't handle this. I have an intel i7,7000 4.2 ghz and 64 gb of ram. I watched my GPU utlization and it never came above 2%. My preferen{F10265908}ces have CPU turned off for rendering but it seems to be taxing my CPU 100% when it renders. I've also sent an error report to the folks at Physical Starlight and they have a ticket open.
Exact steps for others to reproduce the error
Open file, Render>Render Image
Based on the default startup or an attached .blend file (as simple as possible).

**System Information** Operating system: Windows 10 Graphics card: RTX 3070 **Blender Version** Broken: (2.93.2) Worked: (2.93.2, 3.0, K-Cycles 2.93, 3.0) **Short description of error** I have a scene using the addons Physical Starlight and Atmosphere (1.4 beta version), Graswald and a couple of botaniq trees. I have been having this issue for a while and I have tested it in various versions. I go to render a frame in cycles and it gets stuck on "Updating Lights, Computing distribution" and then gives me the error message in the title. It seems that the clouds from the Physical Starlight addon might be causing the problem but I'm surprised that my gpu can't handle this. I have an intel i7,7000 4.2 ghz and 64 gb of ram. I watched my GPU utlization and it never came above 2%. My preferen{[F10265908](https://archive.blender.org/developer/F10265908/snailwarrior18.blend)}ces have CPU turned off for rendering but it seems to be taxing my CPU 100% when it renders. I've also sent an error report to the folks at Physical Starlight and they have a ticket open. **Exact steps for others to reproduce the error** Open file, Render>Render Image Based on the default startup or an attached .blend file (as simple as possible).

Alston Jones commented

2021-08-04 22:08:51 +02:00

Added subscriber: @Alston

Richard Antalik commented

2021-08-05 00:44:41 +02:00

Added subscriber: @iss

Richard Antalik commented

2021-08-05 00:44:41 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Richard Antalik commented

2021-08-05 00:44:41 +02:00

I watched my GPU utlization and it never came above 2%.

Is this GPU core or memory utilization? Please check GPU memory utilization specifically.

Please upload as simple as possible .blend file so we can reproduce the issue.

>I watched my GPU utlization and it never came above 2%. Is this GPU core or memory utilization? Please check GPU memory utilization specifically. Please upload as simple as possible .blend file so we can reproduce the issue.

Alaska commented

2021-08-05 02:17:11 +02:00

Added subscriber: @Alaska

Alaska commented

2021-08-05 02:17:11 +02:00

Error: System is out of GPU and shared host memory

As the error message implies, you are out of memory. When trying to render this scene on my computer, also with 64GB of RAM, it fills it all up plus an extra 30GB of SWAP (Pagefile) before I decided to close Blender. That means your scene takes up 90GB or more when trying to render, this easily exceeds the 8GB of VRAM + 64GB of RAM and probably the pagefile you have, and that's why you get that error.

As for what's causing it, I did some testing and this is what I observed:
The cause for this issue is the materials used by objects. Specifically the StarlightAtmosphere node group from the Physical Starlight and Atmosphere add-on. The node group is rather complex, and as such it takes up a bit of RAM. However, this isn't the issue, the amount of RAM is probably measured in tens of megabytes at the most. The issue is that you've re-used the node group a lot. You've given the node group to every material in the scene meaning that it now has to be stored for every material, which means more RAM is taken up. But once again, this probably isn't the issue, it's probably only going to take up hundreds of megabytes at the most. The issue is that you gave this node group to the "Grasswald" objects, the ones scattered using a particle system onto your landscape. The node group takes information about object position and distance from the camera and such that needs to be re-computed every time the Grasswald objects are scattered. Which is 472,024 times. And these calculations have to be stored in RAM. So although the node group only takes up a couple megabytes at most, it has to be duplicated 472,024 times, which means it takes up lots of RAM and results in the issue you're experiencing.

Removing the StarlightAtmosphere node group from the Grasswald objects resolves the issue with running out of memory. As such, I do not believe this is a bug and this report can probably be closed? I will wait for a developer to decide on this.

In theory Cycles or parts of Blender could be optimized to reduce the RAM usage, but I believe that falls under the catagory of "accidental features request" which we usually respond to with this message:

Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors.

For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

>Error: System is out of GPU and shared host memory As the error message implies, you are out of memory. When trying to render this scene on my computer, also with 64GB of RAM, it fills it all up plus an extra 30GB of SWAP (Pagefile) before I decided to close Blender. That means your scene takes up 90GB or more when trying to render, this easily exceeds the 8GB of VRAM + 64GB of RAM and probably the pagefile you have, and that's why you get that error. As for what's causing it, I did some testing and this is what I observed: The cause for this issue is the materials used by objects. Specifically the `StarlightAtmosphere` node group from the `Physical Starlight and Atmosphere` add-on. The node group is rather complex, and as such it takes up a bit of RAM. However, this isn't the issue, the amount of RAM is probably measured in tens of megabytes at the most. The issue is that you've re-used the node group a lot. You've given the node group to every material in the scene meaning that it now has to be stored for every material, which means more RAM is taken up. But once again, this probably isn't the issue, it's probably only going to take up hundreds of megabytes at the most. The issue is that you gave this node group to the "Grasswald" objects, the ones scattered using a particle system onto your landscape. The node group takes information about object position and distance from the camera and such that needs to be re-computed every time the Grasswald objects are scattered. Which is 472,024 times. And these calculations have to be stored in RAM. So although the node group only takes up a couple megabytes at most, it has to be duplicated 472,024 times, which means it takes up lots of RAM and results in the issue you're experiencing. Removing the `StarlightAtmosphere` node group from the Grasswald objects resolves the issue with running out of memory. As such, I do not believe this is a bug and this report can probably be closed? I will wait for a developer to decide on this. In theory Cycles or parts of Blender could be optimized to reduce the RAM usage, but I believe that falls under the catagory of "accidental features request" which we usually respond to with this message: > Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors. > > For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests > > For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Richard Antalik commented

2021-08-05 03:18:40 +02:00

Changed status from 'Needs User Info' to: 'Archived'

Richard Antalik closed this issue

2021-08-05 03:18:40 +02:00

Richard Antalik commented

2021-08-05 03:18:40 +02:00

Sorry, missed that file is included here. I can confirm that this file uses huge amount of memory, so I will close this report. @Alaska provided good analysis here.

Alston Jones commented

2021-08-05 04:13:20 +02:00

Thank you @Alaska for your clear analysis. I can see how this would end up creating a unique problem that's not exactly a bug. However, I also really appreciate you going through the process of figuring this out so I can try to clean it up.

In #90440#1201991, @Alaska wrote:

Error: System is out of GPU and shared host memory

As the error message implies, you are out of memory. When trying yo render these scene on my computer, also with 64GB of RAM, it fills it all up plus an extra 30GB of SWAP (Pagefile) before I decided to close Blender. That means your scene takes up 90GB or more when trying to render, this easily exceeds the 8GB of VRAM + 64GB of RAM and probably the pagefile you have, and that's why you get that error.

As for what's causing it, I did some testing and this is what I observed:
The cause for this issue is the materials used by objects. Specifically the StarlightAtmosphere node group from the Physical Starlight and Atmosphere add-on. The node group is rather complex, and as such it takes up a bit of RAM. However, this isn't the issue, the amount of RAM is probably measured in tens of megabytes at the most. The issue is that you've re-used the node group a lot. You've given the node group to every material in the scene meaning that it now has to be stored for every material, which means more RAM is taken up. But once again, this probably isn't the issue, it's probably only going to take up hundreds of megabytes at the most. The issue is that you gave this node group to the "Grasswald" objects, the ones scattered using a particle system onto your landscape. The node group takes information about object position and distance from the camera and such that needs to be re-computed every time the Grasswald objects are scattered. Which is 472,024 times. And these calculations have to be stored in RAM. So although the node group only takes up a couple megabytes at most, it has to be duplicated 472,024 times, which means it takes up lots of RAM and results in the issue you're experiencing.

Removing the StarlightAtmosphere node group from the Grasswald objects resolves the issue with running out of memory. As such, I do not believe this is a bug and this report can probably be closed? I will wait for a developer to decide on this.

In theory Cycles or parts of Blender could be optimized to reduce the RAM usage, but I believe that falls under the catagory of "accidental features request" which we usually respond to with this message:

Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors.

For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Thank you @Alaska for your clear analysis. I can see how this would end up creating a unique problem that's not exactly a bug. However, I also really appreciate you going through the process of figuring this out so I can try to clean it up. > In #90440#1201991, @Alaska wrote: >>Error: System is out of GPU and shared host memory > As the error message implies, you are out of memory. When trying yo render these scene on my computer, also with 64GB of RAM, it fills it all up plus an extra 30GB of SWAP (Pagefile) before I decided to close Blender. That means your scene takes up 90GB or more when trying to render, this easily exceeds the 8GB of VRAM + 64GB of RAM and probably the pagefile you have, and that's why you get that error. > > As for what's causing it, I did some testing and this is what I observed: > The cause for this issue is the materials used by objects. Specifically the `StarlightAtmosphere` node group from the `Physical Starlight and Atmosphere` add-on. The node group is rather complex, and as such it takes up a bit of RAM. However, this isn't the issue, the amount of RAM is probably measured in tens of megabytes at the most. The issue is that you've re-used the node group a lot. You've given the node group to every material in the scene meaning that it now has to be stored for every material, which means more RAM is taken up. But once again, this probably isn't the issue, it's probably only going to take up hundreds of megabytes at the most. The issue is that you gave this node group to the "Grasswald" objects, the ones scattered using a particle system onto your landscape. The node group takes information about object position and distance from the camera and such that needs to be re-computed every time the Grasswald objects are scattered. Which is 472,024 times. And these calculations have to be stored in RAM. So although the node group only takes up a couple megabytes at most, it has to be duplicated 472,024 times, which means it takes up lots of RAM and results in the issue you're experiencing. > > Removing the `StarlightAtmosphere` node group from the Grasswald objects resolves the issue with running out of memory. As such, I do not believe this is a bug and this report can probably be closed? I will wait for a developer to decide on this. > > In theory Cycles or parts of Blender could be optimized to reduce the RAM usage, but I believe that falls under the catagory of "accidental features request" which we usually respond to with this message: > >> Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors. >> >> For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests >> >> For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Alston Jones commented

2021-08-05 04:34:01 +02:00

This comment was removed by @Alston

*This comment was removed by @Alston*

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Error: System is out of GPU and shared host memory #90440