Hello,
I have just installed MFiX 25.2 for Windows. I have tried to run a couple of different cases but the same error always shows up, even if I build the solver in the current folder:
Error: Solver crash!
The MFiX solver has terminated unexpectedly
Error information:
access violation in (null)
at (null):0
MFiX 25.1.2 works as usually.
What could be the reason?
Thanks!
Hi @edcanop
There seems to be a problem with 25.2 on Windows. Unfortunately, this release did not get sufficient testing on the Windows platform. I’m not 100% sure what the problem is but we’ll be issuing an update as soon as the problem is fixed.
Sorry for the trouble and thanks for your patience.
– Charles
Dear Jeff and Charles,
Thank you very much for your fast answers. Sure, I will wait for any update!
Cheers,
Eduardo
The problem is related to a Windows debugging library called d3.dll which is supposed to catch errors and report the file and line where the error occurred. For some reason it is misbehaving. Since this feature is completely optional, you can work around the problem by opening a Conda prompt, and doing the following:
(base) C:\> conda activate mfix-25.2
(mfix-25.2) C:\> cd %CONDA_PREFIX%\Scripts
(mfix-25.2) C:\...\envs\mfix-25.2\Scripts> rename d3.dll d3.dll.bak
After doing this, MFiX jobs should run without error, although the debugging of runtime crashes is disabled. This workaround should be sufficient until we have a fix for the underlying problem, at which time we will issue an updated version (25.2.1)
Thanks again for reporting this issue. Let us know if you have any further difficulties with MFiX 25.2.
– Charles
Dear Charles,
I also noticed this problem. In addition, the new version mfix-25.2 GUI seems to have some issues with the utf8 codings
@gq05021 Can you please provide more information about the UTF8 problems you are seeing?
Sorry for misleading. I solved this problem. It is not due to mfix itself, instead it is due to my system configuration
No problem, thanks for clearing that up.