Hi,

I apologize for how frustrating this is.

I have opened an internal ticket for a development team to look at this and I am adding all the information that I can find.

Sometimes fixing an issue is like being a detective we just need more clues until someone has a Sherlock moment and realizes what the cause is. When we get an complaint of an issue that we are not seeing in any of our tests and users themselves are not seeing regularly it can be really difficult to get to the bottom of it.

The stack trace indicates that intellisense (the system that responds to what you type) is trying to show the suggestions window. During this operation it is trying to work out how to draw the window and contents and is measuring the height of the font it is using. Nothing particularity strange so far, but then it is throwing an error about a bad parameter which is sadly a quite generic error. 

It looks like you are using English US windows 10 Home. Do you have any particular language packs installed for windows that may have installed any fonts?

Have you changed any of the display fonts in in Studio settings?

What display language is Studio using - .i.e is the user interface of studio also in English?

What language pair were you using in the project that was having problems?

When you switched back to studio 2017 to finish the job, was that on the same PC? As it seems like you could work in 2017 if it was the same machine it may not be down to the fonts installed on the machine.

Could it be some sort of memory corruption, did you try saving and rebooting and trying again?

If you can answer these questions or give us any other information about this problem please do.

Apologies again and thanks.

Hi,

I apologize for how frustrating this is.

I have opened an internal ticket for a development team to look at this and I am adding all the information that I can find.

Sometimes fixing an issue is like being a detective we just need more clues until someone has a Sherlock moment and realizes what the cause is. When we get an complaint of an issue that we are not seeing in any of our tests and users themselves are not seeing regularly it can be really difficult to get to the bottom of it.

The stack trace indicates that intellisense (the system that responds to what you type) is trying to show the suggestions window. During this operation it is trying to work out how to draw the window and contents and is measuring the height of the font it is using. Nothing particularity strange so far, but then it is throwing an error about a bad parameter which is sadly a quite generic error. 

It looks like you are using English US windows 10 Home. Do you have any particular language packs installed for windows that may have installed any fonts?

Have you changed any of the display fonts in in Studio settings?

What display language is Studio using - .i.e is the user interface of studio also in English?

What language pair were you using in the project that was having problems?

When you switched back to studio 2017 to finish the job, was that on the same PC? As it seems like you could work in 2017 if it was the same machine it may not be down to the fonts installed on the machine.

Could it be some sort of memory corruption, did you try saving and rebooting and trying again?

If you can answer these questions or give us any other information about this problem please do.

Apologies again and thanks.

I really appreciate the follow up. I will try to answer all your questions in the hopes that this will help other linguists.

I am using the US English windows 10 Home version and I did not install any language pack.

The display language in Studio is also English.

Yes, I have changed the size of the font in Studio because sometimes, it is very small and having a font size of at least 12 makes it easier to read and work on. I will try reducing the size of the font and see what happens. Unfortunately, I have not had any Studio projects this week. And since the error does not pop up all the time, it could be a week or two until it comes up again. It's a bit like a car that is making a noise and does not make it when you bring it to your mechanic.

I translate into French, and that is the language that I was using every time the error came up.

Studio 2017 is installed on the same PC. I do not have that error with the2017 version, but had it with 2019 and 2021. I also work for SDL in Montreal, and some of the technicians in that office tried to help me last fall with the 2019 version, but nothing worked. I thanked them and said that I would be installing 2021 soon, and that should resolve the issue. But no, I got the same issue with 2021.

As for the saving and rebooting, I have done that more times than I care to remember. That is always the no. 1 solution offered with all Windows issues. Shut down and reboot. So, I did that numerous times and made sure all the updates (Windows and Studio) are installed. I also corrected/repaired Studio.

I do not think it is some sort of memory corruption because this error came up with numerous clients, not just one.

I guess the only thing that we have shed light on is possibly the font. I will definitely reduce it and see what happens. However, I have always changed the font size, colors, etc. when first setting up any new version of Studio (including 2017), so it would be odd that those changes are creating a problem in 2019 and 2021, but not in 2017.

Chantal