Isotropix Forums

Hi!

I noticed bad bug that would have been impossible for me to track down unless I had only just changed the name of the referenced project outside Clarisse.

It is clear that Clarisse crashes if the project references to a non-existing file.
This did NOT happen in RC2 so this is new bug. This is fatal bug because as Clarisse in built on referencing, it is very easy to have some referenced file missing. Clarisse definitely should not crash on that (if that happens on startup project, it will be infinite loop of restart-crash-restart-crash...). RC2 gave the proper error message but did not crash.

If I manually edit the reference path to non-existing file, the error message flashes on screen but disappears. If I use Reload after that, the error message is displayed correctly as in RC2.

Antti

Hi,

Thanks for the report.

Unfortunately, we have not reproduced your issue. Could you provide us your project file ?

Regards,

Hi!
It was quite complicated to make this demo but I managed to do it finally
I tried to use the Export project archive but it made all references local so that was no good for this. Then I stripped the project to contain only items necessary for this demo. Then I edited the project file manually to make the reference without path so both projects can be in same directory.

To see the problem:
-open refbug.project
-you see it opens normally
-now close Clarisse and rename the rebugref.project to something else
-open the refbug.project
-you see the error message but Clarisse does not crash
-edit the reference path manually to reference to non-existing file
-the error message window flashes but disappears immediately so it is impossible to read what it says
-don't save the changed project
-now set refbug.project as Clarisse startup project
-restart Clarisse
-it will be infinite crash/restart loop until you rename the refbugref.project back to that name outside of Clarisse

I hope this helps to figure out what is going on

Antti

Hi,

Unfortunately, we have not reproduced the issue. Could you try if the problem is still in the 3.5 ?

Regards,

I would yes but my license stopped working
I only rebooted the computer after CCleaner and upgrading F-Secure, nothing else changed but now my license claims to be for different hardware Those cannot and must not change the license validity so I have no idea what happened
I wrote to sales but no reply yet (I just sent the message recently).

Antti

This is clearly off topic:

Probably your F-Secure installed a virtual network card for a VPN or something like that. The license was probably tied to this virtual network card that changed when you upgraded. To avoid this kind of issues identify what is your physical/hardware network card and make sure it's the first one listed by the OS.

To list all your network card use ipconfig /all in the cmd prompt
To reorder your network card you can follow this tutorial for example https://www.howtogeek.com/howto/27994/h ... n-windows/

Hi!
Yes this was totally offtopic but THANK YOU VERY MUCH, I think this is the explanation!
I will continue this with support as I have no way to get back to that configuration so I will need new license anyway.

Thank you!

Antti