Using QM on Windows, while adding the signal name for an event in the property editor, after hitting enter the application crashed. When I tried to reopen the model, the file attempted to open (I could see a white background while the application was loading) but immediately the process got terminated (I saw this in the Task Manager). I opened the .qm file using VSCode to check the XML structure and the structure got corrupted.
I created a new model and then started adding the functionality again. When I hit the save button, the application crashed and the .qm file got corrupted again. I also noticed that when this problem was occurring the file did not detect changes to the model (the asterisk at the title bar was not being displayed). I also tried to recover the file from the .bak file.
At the event viewer in Windows, I saw that the error was suggesting access violation (unfortunately I did not export the data). Then I used the WinDbg tool to monitor the qm.exe execution and it shows that it is an access violation attempting to save the file (the access violation was generated when I hit the save button).
I would really appreciate it if you could investigate and determine in which conditions this might happen.
Thank you!
Anonymous
Thank you for reporting. Which QM version are you using?
--MMS
Attached is the version I am using.
Could you perhaps try it on your end and see if the latest QM 7.0.1 also has this problem? I cannot reproduce it in the QM 7.0.1...
--MMS
The inconvenient we have is that the new version does not support sub-machines. This support is for a commercial license, and I do not think that we are going to migrate because of that. It would be helpful to understand under which conditions this might happen.
If this is a commercial license still under an active support term, please submit the support request to support@state-machine.com
--MMS
Last edit: Quantum Leaps 2025-03-27
Ok thank you!