Mon, Jan 16
In the end I had the time to check my second rig.
CPU: intel Core2Duo e8400
OS: openSuSe 13.2 64bit
Ram: 8GB DDR2
GFX: Radeon HD7770 1GB
Fri, Jan 13
I cannot reproduce the crash either here (linux64, latest master), neither in release build nor in debug + asan build. There’s a lot of visual artifacts at some scale levels though…
Thu, Jan 12
I have an i7-4770k 32gigs of RAM.
Wed, Jan 11
Are you scale once or several times ? Sometimes in blender-2.78-d5cf90f works longer, can scaling several times. Like this:
Later check on my second machine.
Tue, Jan 10
ubuntu 16.04 64 bits blender master hash d5cf90f NVIDIA titan black
Sat, Jan 7
Can confirm the behavior. Really looks like a bug indeed. It only happens when the bevel modifier is activated, so I'll let @Howard Trickey (howardt) decide.
Thu, Jan 5
Dec 21 2016
Dec 9 2016
Works like a charm in the nightly build. Thank you very much! :-)
Dec 6 2016
Nov 29 2016
I can confirm this. Will work on fixing it now.
I confirm that this happened in the version of blender cited (commit 3e460b6), but at the latest revision of 2.78 (bd5ae46c) the crash does not happen. I am closing this one. Feel free to reopen if the crash still happens for you. There is another bevel crash bug task that I am going to look at now, so I am not discounting that there may be a bug to fix here. Going to look at that other task now.
Nov 27 2016
Nov 26 2016
I'd love this because I work a lot with the Mirror modifier and run not rarely into the problem that I want to merge some portions along the Mirror axis but not all of them.
Nov 22 2016
Looked into this problem, which is caused by a concave quad,
where the edge between its 1st and 3rd vertex is outside the face when projected onto its own normal.
Nov 15 2016
Nov 12 2016
Nov 11 2016
Please do not mix issues, if you have another problem create a new report.
Nov 9 2016
See for example T43393, T35590 for some tickets reporting the same problem, this has been considered a known limitation so far and not a bug. Note the issue is specifically with the Connected method (I can't tell if you have that enabled in 2.49).
Nov 8 2016
Nov 4 2016
Like it was said, this is currently a limitation of the BMesh Boolean solver (library) and not the add-on itself.
I already show you youtube what I create bug report. I am not good english. I show you really clear on youtube.
Please follow our submission template and guidelines and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.
Videos and/or links to external sites etc. are not acceptable as bug report (they can be provided as additional information only).
Nov 3 2016
Nov 2 2016
Nov 1 2016
Hello to all the team.
Oct 28 2016
Oct 24 2016
Thank you for your answers.
Can not reproduce the issue. Things to try:
I tried several times. That crash when these three conditions are met:
Cannot confirm in Windows 7 64bits. Steps to recreate aren't very clear
Oct 23 2016
Thanks, can confirm there seems to be a problem here indeed.
Oct 17 2016
@Howard Trickey (howardt) I've been looking at the bevel code, and found that just before the crash, the BMILoop l has a null BMIEdge, so l->v, l->f are fine, but l->e is NULL.
Oct 16 2016
Right, just wanted to clarify since the description says "fix sefgault" but it will still crash, just in a slightly more informative way.
@Brecht Van Lommel (brecht) I'll still figuring out the issue, this was just one I noticed.
I suspect this might be similar or the same as the problem in T49467, which I haven't had time to fix yet. I should have time to look at this soon - not next week, but the week after.