**System Information**
Operating system: Windows-10-10.0.19042-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1660/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.84
**Blender Version**
Broken: version: 3.1.0 and upwards. including 3.2.0 Alpha, branch: master, commit date: 2022-03-31 17:14, hash: `rB42853bacc973`
Worked: (newest version of Blender that worked as expected)
**Short description of error**
//String to Curves// node causes crash when the output from the //Curve Instances // socket is filled with N-gons (via //Fill Curve// node) and linked to a //Merge by Distance// node.
{F12964804}
Some things I've observed via trial and error:
- It doesn't matter if the Geometry Nodes in question is on a curve object or a mesh object
- Crash doesn't occur when the //Triangles //mode of the //Fill Curve// is used instead of// N-gons//
- Crash doesn't occur if you use a //Realize Instances// node right after //String to Curves//
- Crash doesn't occur if you use a //Resample Curve// node right after //String to Curves//
- Crash doesn't occur if you add a Geometry Nodes to a normal Text object (Shift A > Text) and use the same //Fill Curve—N-gons **>** Merge by Distance// setup (as seen in the screenshot)
- Crash doesn't occur if you attempt to use the same setup with curve instances created via other methods (for instance, curve primitives instanced on points—as seen in the screenshot)
**EDIT:** Upon further investigation I found an even weirder but consistent behaviour:
- It seems like only some letters cause the crash to occur. These letters are "A, X, x, Y, H, K". Case sensitive. The only lowercase letter to cause crash is "x". No other letters were problematic for me, even Turkish characters like Ö,Ç, or Ğ, or numbers. One common feature is perhaps them having geometries where lines intersect sharply, but then again, "P" or lowercase "k" doesn't cause a crash so I don't know.
- These letters cause a crash only when they're used by themselves. So, if you simply type "H" in the //String //box, it crashes, but if you type "HX"—no crash, even though they're both letters from the list above.
- Using a// Resample Curve// right after //String to Curves// seems to prevent all crashes, but using// Realize Instances //only prevents multi-letter crashes. So, if you type just "K" into the box, it doesn't crash if there's a //Resample Curve// node attached, but it does crash if there's a //Realize Instances// node instead. But if you type multiple letters, say "LX", it doesn't crash even if you're using //Realize Instances// (but it crashes if neither is present).
**Exact steps for others to reproduce the error**
# Put a //Geometry Nodes// modifier on any type of object that supports it.
# Add a //String to Curves// node, write something in the //String// box including at least one of the letters "A, X, x, Y, H, K" and link the output into a //Fill Curve// node with the //N-gon// mode selected
# Feed the //Fill Curve// node into a //Merge by Distance// node, which in turn is linked into the //Group Output—Geometry// socket.
# Crash occurs as soon as you link or attempt to play with the value on the //Merge by Distance// node.
or
# Download the attached blend file and mute the //Resample Curve //node of the GN setup seen in the bottom part of the screenshot above.
Thanks!
{F12964807}