Thanks for your report and testing. I did not try to work around or fix the problem because it seems something that creates an all out crash needs fixing, even if some oddities like the boundaries maybe the cause, errors should be trapped and not crash FreeCAD.
This may be linked to "phantom paths " bug and I may be guilty of "going to the opera" before/after defining the job.
IIRC what I did here was create the sketch , pad +ve, add job, noticed that origin was not right. Went back and changed pad to "reversed", came back to same job ( ie not deleting and starting fresh job ). This presumably will no longer cause problems when Russ' PR is merged.
I know I keep moaning about lack of error checking, maybe this common practice in python, but even if something like phantom paths bug is setting the scene for this to happen it seems to me to show that some more low level error checking is needed instead of letting stuff assume everything is OK.
I'd like some thoughts on this from those writing the python code in FreeCAD.
Code: Select all
Exception (Mon Jun 24 11:31:31 2019): Access violation
OS differences likely explain different results. It seem Linux takes illegal memory accesses more seriously than Windows.
Code: Select all
PathPocketShape.ERROR: extendWire(): (ePts[0] - endPts[0]).Length
PathPocketShape.ERROR: list index out of range
PathPocketShape.ERROR: extendWire(): (ePts[0] - endPts[0]).Length
PathPocketShape.ERROR: list index out of range
Program received signal SIGSEGV, Segmentation fault.
#0 /lib64/libpthread.so.0(+0x13070) [0x7f3258199070]
#1 /usr/local/lib64/libCoin.so.80(cc_rbptree_insert+0xa) [0x7f32586a133a]
#2 0x7f325880bf52 in SoChildList::append(SoNode*) from /usr/local/lib64/libCoin.so.80+0x22
#3 0x7f3258852333 in SoGroup::addChild(SoNode*) from /usr/local/lib64/libCoin.so.80+0x43
#4 /usr/lib/python2.7/site-packages/pivy/_coin.so(+0x51440a) [0x7f32349a140a]
#5 /lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x8f3b) [0x7f325919f14b]
#6 /lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x7f9c) [0x7f325919e1ac]
#7 /lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x712) [0x7f325919f902]
#8 /lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x632c) [0x7f325919c53c]
#9 /lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x712) [0x7f325919f902]
#10 /lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x632c) [0x7f325919c53c]
#11 /lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x712) [0x7f325919f902]
#12 /lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x632c) [0x7f325919c53c]
#13 /lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x7f9c) [0x7f325919e1ac]
Opened provided file with immediate error in Report Panel:
Code: Select all
No extension found of type 'PartGui::ViewProviderAttachExtension
I get no error on opening the file. The only thing I have changed from building master a couple of days ago, is replacing PathSurface.py t3 with w3 , and I have the extended tools enabled to get the 3D pocket tool ( which is not used here ).
I think that is due to you testing a virgin FC. I had the 3D pocket enabled.