-
-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changing a named reference constraint crashes FreeCAD #387
Comments
I can't reproduce it. How do you change the length using mouse? By dragging the line? Also, did it freeze or crash? If it crashes, please start the AppImage using command line in a terminal, and post the call stack dump when it crashes? If it freezes, please find out the running FreeCADLink process ID. You can use the task manager on your system. And then kill the process by typing the following command in a terminal, and post the dump here. kill -SIGSEGV <ProcessID>
|
======================================== Report: FreeCAD#4183 realthunder/FreeCAD_assembly3#387 Problem: renameConstraint() previously implemented exclusively in SketchObjectPyImp.cpp, will change the Constraints property without updating the solver. A prospective drag operation would rely on a deleted pointer constraint which leads to the crash. Solution: make renameConstraint function update the solver so that Bonus: move the core of the function to SketchObject.cpp so that input data validity check on constraint change is inhibited.
======================================== Report: FreeCAD#4183 realthunder/FreeCAD_assembly3#387 Problem: renameConstraint() previously implemented exclusively in SketchObjectPyImp.cpp, will change the Constraints property without updating the solver. A prospective drag operation would rely on a deleted pointer constraint which leads to the crash. Solution: make renameConstraint function update the solver so that Bonus: move the core of the function to SketchObject.cpp so that input data validity check on constraint change is inhibited.
======================================== Report: FreeCAD#4183 realthunder/FreeCAD_assembly3#387 Problem: renameConstraint() previously implemented exclusively in SketchObjectPyImp.cpp, will change the Constraints property without updating the solver. A prospective drag operation would rely on a deleted pointer constraint which leads to the crash. Solution: make renameConstraint function update the solver so that Bonus: move the core of the function to SketchObject.cpp so that input data validity check on constraint change is inhibited.
======================================== Report: FreeCAD#4183 realthunder/FreeCAD_assembly3#387 Problem: renameConstraint() previously implemented exclusively in SketchObjectPyImp.cpp, will change the Constraints property without updating the solver. A prospective drag operation would rely on a deleted pointer constraint which leads to the crash. Solution: - mark the solver status as needing an update - leverage new through sketchobject r/w interface to ensure solver is synchronised before the temporary move operation starts Bonus: move the core of the function to SketchObject.cpp so that input data validity check on constraint change is inhibited.
======================================== Report: FreeCAD#4183 realthunder/FreeCAD_assembly3#387 Problem: renameConstraint() previously implemented exclusively in SketchObjectPyImp.cpp, will change the Constraints property without updating the solver. A prospective drag operation would rely on a deleted pointer constraint which leads to the crash. Solution: - mark the solver status as needing an update - leverage new through sketchobject r/w interface to ensure solver is synchronised before the temporary move operation starts Bonus: move the core of the function to SketchObject.cpp so that input data validity check on constraint change is inhibited.
======================================== Report: FreeCAD#4183 realthunder/FreeCAD_assembly3#387 Problem: renameConstraint() previously implemented exclusively in SketchObjectPyImp.cpp, will change the Constraints property without updating the solver. A prospective drag operation would rely on a deleted pointer constraint which leads to the crash. Solution: - mark the solver status as needing an update - leverage new through sketchobject r/w interface to ensure solver is synchronised before the temporary move operation starts Bonus: move the core of the function to SketchObject.cpp so that input data validity check on constraint change is inhibited.
======================================== Report: FreeCAD#4183 realthunder/FreeCAD_assembly3#387 Problem: renameConstraint() previously implemented exclusively in SketchObjectPyImp.cpp, will change the Constraints property without updating the solver. A prospective drag operation would rely on a deleted pointer constraint which leads to the crash. Solution: - mark the solver status as needing an update - leverage new through sketchobject r/w interface to ensure solver is synchronised before the temporary move operation starts Bonus: move the core of the function to SketchObject.cpp so that input data validity check on constraint change is inhibited.
======================================== Report: FreeCAD#4183 realthunder/FreeCAD_assembly3#387 Problem: renameConstraint() previously implemented exclusively in SketchObjectPyImp.cpp, will change the Constraints property without updating the solver. A prospective drag operation would rely on a deleted pointer constraint which leads to the crash. Solution: - mark the solver status as needing an update - leverage new through sketchobject r/w interface to ensure solver is synchronised before the temporary move operation starts Bonus: move the core of the function to SketchObject.cpp so that input data validity check on constraint change is inhibited.
======================================== Report: #4183 realthunder/FreeCAD_assembly3#387 Problem: renameConstraint() previously implemented exclusively in SketchObjectPyImp.cpp, will change the Constraints property without updating the solver. A prospective drag operation would rely on a deleted pointer constraint which leads to the crash. Solution: - mark the solver status as needing an update - leverage new through sketchobject r/w interface to ensure solver is synchronised before the temporary move operation starts Bonus: move the core of the function to SketchObject.cpp so that input data validity check on constraint change is inhibited.
Tested on: OS: Windows 10 Version 2009 No issue found. |
Closing ticket |
I can constantly recreate this issue following this procedure.
If the constraint is unnamed there is no problem
Tried to recreate this in the "official" 0.19 AppImage and doesn't crashes
I run the following version:
The text was updated successfully, but these errors were encountered: