Skin modifier crash with null skin radii (C++ assert)
Closed, ResolvedPublic


System Information
Nvidia GTX 460

Blender Version
Broken: 2.7 RC1

Short description of error
Setting the skin radius to a smaller value with numinput crashes blender

Exact steps for others to reproduce the error
Based on

  1. Open attached file and press Ctrl+A .5
  2. Blender crashes


Ellwood Zwovic (gandalf3) updated the task description. (Show Details)
Ellwood Zwovic (gandalf3) raised the priority of this task from to Needs Triage.
Ellwood Zwovic (gandalf3) set Type to Bug.

Actually, issue is caused by skin radius being set to zero (the only dot in numinput will evaluate to 0…).

Grmlll… looks like this tool should not crash on Zero radius…

Not my area at all, have no clue how this stuff works… :/

Bastien Montagne (mont29) renamed this task from Crash when using numinput to adjust skin modifier to Skin modifier crash with null skin radii (C++ assert).Mar 11 2014, 12:12 AM
Bastien Montagne (mont29) lowered the priority of this task from High to Normal.

@Nicholas Bishop (nicholasbishop): Maybe you could have a look at this issue? I'm getting nan values in the skin modifier data. Culprit seems to be this function (maybe dangling pointers exist in Frame.merge before):;a7ed1db51fa32a80b943816d354b45b413d98fa3$1471

There was another issue in relation to skin modifier in this report: T39341
The actual regression was fixed, but if you have a look at this reduced test file

, you can see that enter/exit editmode constantly changes the vertex/face count. I'm pretty sure these two things are both related to skin modifier applied on a edge-only mesh.

@Campbell Barton (campbellbarton), remember you've added some clamping to skin modifier, guess we need some more here?

@Nicholas Bishop (nicholasbishop), any hope you'll have a look in observable future?

Apologies, but I've created a new bug report about this, as I didn't find this in the search earlier.
It's T44566, and I've also attached a .blend there.
I can't edit it anymore, or I'd make it a subtask!
And as I didn't mention it in my report (can't edit), I'm on Windows 7, 64bit, with an Nvidia GTX 670 (driver: 347.52)