metaball vanishes & changes name then Blender crashed #94518

New Issue

Ward Darcey · 2021-12-30T23:33:21+01:00

Ward Darcey commented

2021-12-30 23:33:21 +01:00

{F12782443}System Information
Operating system: Windows-10-10.0.19043-SP0 64 Bits
Graphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.71

Blender Version
Broken: version: 3.1.0 Alpha, branch: master, commit date: 2021-12-29 00:25, hash: c34ea3323a
Worked: (2.8)

Short description of error
Metaball placed in a new file shows as expected until scaled down, then vanishes.
However, a metaball placed in a file with a few other objects shows only as an empty circle.

This is the file - B3_WaterDroplets.blend

Exact steps for others to reproduce the error
I set up a simple water droplets simulation on a cube using a UV sphere & geometry nodes.
This worked just as expected.
I added a metaball object with the intention of substituting it for the UV sphere in the Object Info node.
I renamed the metaball at the object data level (to "BlobOne" in this case) and the
object name changed mysteriously to "Hello".
I did NOT name any object "Hello" in that file. The "Hello" has come from the Blender code.
The object data level still is called "BlobOne".
I hope this is useful feedback to finding the problem . . . I can see the possibility that the
vanishing metaball problem has something to do with the appearance of "Hello" in the name.
At that point some of the metaball's data gets lost.
Then shortly after that Blender crashed as I resized a window, without any error message.

I was using Blender 3.1 Alpha filename "blender-3.1.0-alpha+master.c34ea3323a3a-windows.amd64-release.zip"
but the same behaviour occurs with 3.0 stable.

I hope this helps (!) - somewhere in the code you're looking for "Hello"

[Based on the default startup or an attached .blend file (as simple as possible)]

{[F12782443](https://archive.blender.org/developer/F12782443/system-info.txt)}**System Information** Operating system: Windows-10-10.0.19043-SP0 64 Bits Graphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.71 **Blender Version** Broken: version: 3.1.0 Alpha, branch: master, commit date: 2021-12-29 00:25, hash: `c34ea3323a` Worked: (2.8) **Short description of error** Metaball placed in a new file shows as expected until scaled down, then vanishes. However, a metaball placed in a file with a few other objects shows only as an empty circle. This is the file - [B3_WaterDroplets.blend](https://archive.blender.org/developer/F12782503/B3_WaterDroplets.blend) **Exact steps for others to reproduce the error** I set up a simple water droplets simulation on a cube using a UV sphere & geometry nodes. This worked just as expected. I added a metaball object with the intention of substituting it for the UV sphere in the Object Info node. I renamed the metaball at the object data level (to "BlobOne" in this case) and the object name changed mysteriously to "Hello". I did NOT name any object "Hello" in that file. The "Hello" has come from the Blender code. The object data level still is called "BlobOne". I hope this is useful feedback to finding the problem . . . I can see the possibility that the vanishing metaball problem has something to do with the appearance of "Hello" in the name. At that point some of the metaball's data gets lost. Then shortly after that Blender crashed as I resized a window, without any error message. I was using Blender 3.1 Alpha filename "blender-3.1.0-alpha+master.c34ea3323a3a-windows.amd64-release.zip" but the same behaviour occurs with 3.0 stable. I hope this helps (!) - somewhere in the code you're looking for "Hello" [Based on the default startup or an attached .blend file (as simple as possible)]

Ward Darcey commented

2021-12-30 23:33:21 +01:00

Added subscriber: @didactic

Fen commented

2021-12-31 03:26:21 +01:00

Added subscriber: @chemicalcrux

Fen commented

2021-12-31 03:26:21 +01:00

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

Fen commented

2021-12-31 03:26:21 +01:00

A debug/developer 3.1 alpha build immediately triggers AddressSanitizer when I open that file: P2690

A 3.0 release build is randomly crashing when I undo repeatedly after selecting a few objects. I cannot get this to happen reliably yet. Sometimes, Blender just hangs for a moment instead of crashing: P2691

I was not, however, able to replicate the bug you described. Can you reliably trigger this on your end?

A debug/developer 3.1 alpha build immediately triggers AddressSanitizer when I open that file: [P2690](https://archive.blender.org/developer/P2690.txt) A 3.0 release build is randomly crashing when I undo repeatedly after selecting a few objects. I cannot get this to happen reliably yet. Sometimes, Blender just hangs for a moment instead of crashing: [P2691](https://archive.blender.org/developer/P2691.txt) I was not, however, able to replicate the bug you described. Can you reliably trigger this on your end?

Ward Darcey commented

2021-12-31 09:58:30 +01:00

I can reliably predict that the metaball disappears as described.
This even occurs when starting from a new file.
I am going to try this on a few other computers with that same blender build & same file,
ie different hardware, then get back to you with the results.
I think I can test this without the Nvidia card altogether.
Just give me a few hours to test on different hardware.
It seemed like a Blender problem, but it might just be the damn Nvidia drivers.
Odd that you too are having different problems with the dame file.
Back soon, thanks for your attention.

I can reliably predict that the metaball disappears as described. This even occurs when starting from a new file. I am going to try this on a few other computers with that same blender build & same file, ie different hardware, then get back to you with the results. I think I can test this without the Nvidia card altogether. Just give me a few hours to test on different hardware. It seemed like a Blender problem, but it might just be the damn Nvidia drivers. Odd that you too are having different problems with the dame file. Back soon, thanks for your attention.

Pratik Borhade commented

2021-12-31 11:05:44 +01:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2021-12-31 11:05:44 +01:00

Hi @didactic , thanks for the report.

Then shortly after that Blender crashed as I resized a window,

You mean crash occurs after resizing application window? Can not reproduce in that case.

I can rename without any issue, it didn't show up "Hello" name for metaball.
I would suggest to test again with factory preferences: {nav Edit > Preferences > Save & Load (3 horizontal lines) > Load Factory preferences}

Also, please provide crash logs generated after the crash: https://docs.blender.org/manual/en/dev/troubleshooting/crash.html#crash-log

Hi @didactic , thanks for the report. > Then shortly after that Blender crashed as I resized a window, You mean crash occurs after resizing application window? Can not reproduce in that case. I can rename without any issue, it didn't show up "Hello" name for metaball. I would suggest to test again with factory preferences: {nav Edit > Preferences > Save & Load (3 horizontal lines) > Load Factory preferences} ![image.png](https://archive.blender.org/developer/F12717357/image.png) Also, please provide crash logs generated after the crash: https://docs.blender.org/manual/en/dev/troubleshooting/crash.html#crash-log

Ward Darcey commented

2022-01-01 00:48:01 +01:00

Process-of-elimination brings me to the conclusion that that the file is faulty.
The machine(1) I used it on has had several previous Blender versions on it (2.6 & up)
but the faulty file was started on Blender 3, definitely not started on any previous version.
But on machine(1), even a new file behaves badly - however on machine(2) with identical
hardware (ie same motherboard, processor & chipset) with no previous versions of Blender,
the problems still exist on the suspect file, but not on a new file.

So I suggest there is a settings "leak" from previous versions into Blender 3, because
reloading factory defaults as you suggested, cleaned up the behavior on a new file,
but the original file remained faulty regardless of what I did.
Also, when I copied the objects (file/append/ . . ) from the bad file into the new file,
on machine(2), they all behaved just fine.
I've tried uninstall/reinstall on machine(1), but the problem persists ONLY WITH THE SUSPECTED FILE

Ugh!

That's the best I can find out, but some crook data has got into one file only on one machine.
This is inconclusive, but now I'm alerted to this behavior, I'll look out for more & submit
another report if I find anything specific & reproducible.

Thanks for your attention.

Process-of-elimination brings me to the conclusion that that the file is faulty. The machine(1) I used it on has had several previous Blender versions on it (2.6 & up) but the faulty file was started on Blender 3, definitely not started on any previous version. But on machine(1), even a new file behaves badly - however on machine(2) with identical hardware (ie same motherboard, processor & chipset) with no previous versions of Blender, the problems still exist on the suspect file, but not on a new file. So I suggest there is a settings "leak" from previous versions into Blender 3, because reloading factory defaults as you suggested, cleaned up the behavior on a new file, but the original file remained faulty regardless of what I did. Also, when I copied the objects (file/append/ . . ) from the bad file into the new file, on machine(2), they all behaved just fine. I've tried uninstall/reinstall on machine(1), but the problem persists ONLY WITH THE SUSPECTED FILE Ugh! That's the best I can find out, but some crook data has got into one file only on one machine. This is inconclusive, but now I'm alerted to this behavior, I'll look out for more & submit another report if I find anything specific & reproducible. Thanks for your attention.

Pratik Borhade commented

2022-01-05 19:28:02 +01:00

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

Pratik Borhade closed this issue

2022-01-05 19:28:02 +01:00

Pratik Borhade commented

2022-01-05 19:28:02 +01:00

This is inconclusive, but now I'm alerted to this behavior, I'll look out for more & submit another report if I find anything specific & reproducible.

Hi, will close this ticket for now.

Feel free submit a new report. Be sure to provide system information, Blender version, the last Blender version which worked, and a .blend file with exact steps to reproduce the problem.

(A guideline for making a good bug report can be found at https://wiki.blender.org/wiki/Process/Bug_Reports)

> This is inconclusive, but now I'm alerted to this behavior, I'll look out for more & submit another report if I find anything specific & reproducible. Hi, will close this ticket for now. Feel free submit a new report. Be sure to provide system information, Blender version, the last Blender version which worked, and a .blend file with exact steps to reproduce the problem. (A guideline for making a good bug report can be found at https://wiki.blender.org/wiki/Process/Bug_Reports)

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

metaball vanishes & changes name then Blender crashed #94518