Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Hardware issue] (AMD) CPU baking crash #86

Closed
TripleDots opened this issue Feb 20, 2018 · 3 comments
Closed

[Hardware issue] (AMD) CPU baking crash #86

TripleDots opened this issue Feb 20, 2018 · 3 comments
Labels

Comments

@TripleDots
Copy link

TripleDots commented Feb 20, 2018

So I went in to try the CPU solver as the RX480 seems to be bugged (see: #78 ).
But for whatever reason, baking rarely goes beyond the 16th and 17th frame on all of my renders when the resolution is specifically above 200 with the CPU. EDIT: the higher the resolution, the faster it crashes.)
It happens almost every

time with white water enabled and it crashes less without white water. But still around that 17 frame mark.
There is no error message or crash log created when this happens.

There is no overheating happening.
Limiting cores doesn't do anything either.
RAM is not even near full use.
Disks are empty as well.

AMD Bulldozer 8350 x8 BLACK EDITION (stock)
24gb DDR3 ram 1600mhz
RX480 (stock)
Windows 10

*This also occurs on my AMD Phenom II x4 840 and x6 which makes me believe that it's another AMD focused issue. So if there are more folks that can test this:

Turn white water on (white water, bubbles and spray)
Set RES to 200
Turn off: GPU Scalar Field and GPU Particle Advection
Turn on: Enable Adaptive Time Stepping for obstacles

Blend file:
https://we.tl/tw8ksLYPiO

flip_fluid_stats.pdf

@rlguy
Copy link
Owner

rlguy commented Feb 20, 2018

I tested this and I also get the error. I'm running on Intel CPU and NVidia GPU, so this bug is not limited to AMD hardware. From the Blender system console:

tripledots_scene_error

The error means that the simulator is trying to access memory that is out of bounds. This shouldn't be too difficult to debug. I'm taking a further look into this now and I'll keep you updated in this thread.

@rlguy rlguy added the bug label Feb 20, 2018
@rlguy
Copy link
Owner

rlguy commented Feb 20, 2018

Thanks for finding and reporting this! This bug occurs when the GPU Scalar Field option is turned off. Your scene provided the perfect setup for triggering this error.

This bug has been fixed and and will be included in the next version (0.1.2b).

Workaround

Until the next version, keep the GPU Scalar Field option turned on. As far as I know, this GPU feature does not affect AMD users. If this option does cause problems, please let me know.

@rlguy rlguy closed this as completed Feb 20, 2018
@TripleDots
Copy link
Author

Thank you! The current work around works.
It does seem that the white water particles are still a bit more playful (but still very close to CPU only.) But that is from one tiny test.
I will fully test this tomorrow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants