HarryvL wrote: ↑Fri Aug 10, 2018 11:47 am
Thanks @Jee-Bee. This may be related. The thread suddenly stopped on this topic.
Have you tried renaming the .cfg files in %appdata%/freecad?
Sometimes this just fixes things magically. The point of renaming the files is that FreeCAD creates new ones on restart, and if this fixes the problem, we can examine the old files and try to find the problem.
Do you get the same behavior with the pre-built binaries on the release page? (Thy use the same Libpack)
I am trying to reproduce without success,
What is your start wb?
What example FEM example file are you opening?
What workbench do you first switch to?
Hi @sgrogan, I am just back on line and ready to try a few things. But here a few easy answers:
FreeCAD opens up on >START. If I click on any link under "Example Projects" I get the crash. So with ALL EXAMPLES I get this behavior.
As an example, the first link in the list refers to c:/Users/hvlan/Documents/FC_Daily/Build/data/Mod/Start/StartPage/LoadSchenkel.py
HarryvL wrote: ↑Fri Aug 10, 2018 7:47 pm
WAIT ... that's with the release version. let me try again with the debug version
crash_3.png (505.28 KiB) Viewed 951 times
Again no crash file.
ALSO: I tried to open the example files with the debug version and again I gets a crash for all. Removing the user and system files doesn't help this time.
wmayer wrote: ↑Fri Aug 10, 2018 7:08 am
When you are in debug mode can you have a look at the Output panel of Visual Studio. You should get a list of all loaded dlls and I wonder if there might be loaded two different versions of a library.
E.g. netgen links against OCCT and it can happen that FreeCAD is linked against a different OCCT version. This would result in undefined behaviour when FreeCAD loads the FEM module which then pulls the binary incompatible OCCT version.
Werner, the only duplication I can spot is comctl32.dll and they indeed refer to different module versions and directories. Could this be the culprit?
