There seems to be a connection with the setting "Fuzzy Matches - Include Recycle Bin".

Good morning Susanne Muris ,

we've been facing a crashing issue, too.

In our case, Passolo sporadically crashes during the update of string lists. At some days it keeps crashing in 19 of 20 updating processes, on other days it crashes 0 or 1 of 20 times.
As we are using licenses with a license server, it's very annoying because, after a crash this license is locked for about five minutes. And it can't be released without releasing all other licenses on that server, too. Until now it seems not to be possible, to release only one license on a server. Therefore, I've already created a feature request, here: Possibility to release a session of only one user in license server manager. Feel free, to vote for it.

"Unfortunately", in our case, Passolo doesn't crash everytime during the update process, which makes it very difficult, to analyse. And until now, the support from RWS is not able to reproduce the issue on there systems. Even with our project files.

I don't know, if our issue is related to yours, especially, because we're not working on a project with the Java add-in but with the "Microsoft .Net Parser". But who knows?! Therefore, I'm writing here. Maybe, we can collect further results of our investigation, here, until it's proven that our cases are not related to eachother.

In our case, the crashing issue seems to be related to the parser setting "Diagnostic Report". Disabling this option prevented crashes. But at the moment, even with this option re-enabled, I'm not able to reproduce the issue.

What you could try, is a clean boot of windows (support.microsoft.com/.../how-to-perform-a-clean-boot-in-windows-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).

Kind regards and have a nice day.
Nils

Hi Susanne - wild guess but if you are seeing this while translating in Passolo, I had this at one point and could ultimately address it by resetting the window layout (View - Reset Window Layout). It was very tricky to reproduce, so we could not really address it as a bug in the product yet. You can perhaps check this? I have not seen such frequent crashes since (when doing translation or review work in string lists). Thanks, Daniel

Hello Nils,

thank you for your reply.

In my case, the crashes happened during translation, the string list updates worked fine. However, I recognize the license problem and will definitely look at the feature request. 

Kind regards,

Susanne

Hi Daniel,

yes, the crashes happened during translation; they were typically associated with pre-translation via the translation assistant.

However, I was about to resize the bottom pane when the software crashed the first time, so your advice sounds entirely plausible.

Next week I will see whether that solved the problem.

Thank you very much!

Unfortunately, the crashes still occur, and I still believe there is a connection with pre-translation via the translation assistant. 

These are my settings:

- "Use translation assistant" is enabled.

- On CTRL+Down, the next untranslated string is located.

- Then, a fuzzy search is to be performed and matches better than 99% should be used for pre-translation. At this stage, the crash occurs.

A simple pre-translation using F8 works fine.

Thanks Susanne - and resetting Passolo window layout did not help? Personally, I did not see any crashes anymore after doing that. Thanks, Daniel

Hi Daniel,

I'm afraid not. After resetting the window layout, the crashes still occurred.

Kind regards

Susanne

Sorry to hear that Susanne Muris . I am wondering if perhaps Adrian Maniu  or Achim Herrmann can reach out and see if he can help you figure this out. It might still be worth trying to resize the Passolo window slightly, for instance.

Hello,

Could you check the resources used for translations and maybe try to disable them one by one? To identify which one is causing issues?

Could you check if Studio/MultiTerm are updated to latest versions if you use them?

Could you post an error message from Event Viewer with the crash - the log might have additional details about the issue.