Unfortunately, it is not the last known one for bevel. I'm currently working on T53459, which is taking a lot of effort to fix (end is in sight, though).
For this bug, as mentioned earlier, the problem is that I don't understand the theory of subdivision with constraints on boundary normals well enough to make the general case ensure curvature continuity.
Just wanted to report the same bug and noticed it's the last known one for bevel, congrats @Howard Trickey (howardt) for making it so robust :)
Thanks for this clarification.
Sun, Jan 14
Thu, Jan 11
No problem @Campbell Barton (campbellbarton) . My fix had some weird side effects when I tested it deeper after submitting the patch, so not surprised it was rejected. Glad I could help better define the root cause though.
Thanks @Dan Marra (dmarra) for finding the cause of the error, though I closed the diff since I think it doesn't properly resolve the issue.
Modifying the normal by the plane may give bad results in some cases.
This is actually a problem that occurs when the vertex normal is the same as the normal between both points of the edge; aka the edge is pointing towards the object origin.
Wed, Jan 10
My last comment wasn;t entirely true. It seems that in the first case of (0,0,0), setting the pivot point to "active element" corrects the behavior. However, for the second reproduction step regarding multiples of 2, no pivot point selection seems to remedy the problem.
After playing with this a bit, I noticed that if you move the vertex that is positioned at local (0,0,0) to another position, and then move it back to local (0,0,0), the orientation of the manipulator is correct.
Tue, Jan 9
Sun, Jan 7
Here is proposal for bevel options for corners:
Bevel affect inner corners too:
Sat, Jan 6
Looked into it, this happens to rotation too. This can be set as TODO and archived. - https://wiki.blender.org/index.php/Dev:Source/Development/Todo/Tools#Transform
Fri, Jan 5
Also think this is kind of expected to accumulate?
@Campbell Barton (campbellbarton) : you think this can be closed? Or Should I take some time investigating more?
Thu, Jan 4
Wed, Dec 20
I think it is a known limitation. It may be considered as a visual disturbance. It looks related to position of selection in the window and amount of movements.
But user should focus on the mesh and not really take attention to the position of mouse pointer.
I am happy to change the code for Bevel and Inset to allow spacebar for confirm. Just wanted to check with someone else (Campbell?) that this is indeed a UI pattern that Blender is intended to have.
@Howard Trickey (howardt), is it something you can have a look into? :)
Tue, Dec 19
One more thing I noticed, is that transform operator has its own modal hotkey map. Because of that a lot of things can be set by the user, it looks like 'Release confirms' is some old option that is not needed in case of transform operator at all since that can be changed by a user in another way.
on 2.79.1 bb30ce0
Try a later version from build bot. Bugs have recently been squashed on these.
Nov 15 2017
Confirmed on linux for 2.79 and master 556b13f
Nov 13 2017
Nov 12 2017
Yes my bad
It looks like a duplicate report of T53145
Nov 3 2017
I had to hit tab a lot (spam it more than 10 times) after joining and got a crash indeed on win7 using latest master.
This has already been reported here: T53145
Nov 2 2017
Oct 31 2017
It looks like array modifier is not using name but index of vertex group.