Hello Dieter Gust,

I understand that you're experiencing a "System.OutOfMemoryException" error when trying to use the DeepL MT Translation provider in your project settings. This can be quite frustrating, especially when you have a lot of translation work to do. Let's try to resolve this issue step by step:

Step 1: Ensure that you have the latest version of Trados Studio installed. You can check this by going to the Help tab and selecting 'About SDL Trados Studio'. If you don't have the latest version, you can download the latest installer for Trados Studio 2021 SR2 and run it after closing Trados Studio.

Step 2: Once you have the latest version of Trados Studio installed, open the application.

Step 3: Uninstall the DeepL Translation Provider plugin. You can do this from the Welcome view by going to the Add-Ins tab, then to the RWS AppStore, and finally to the Installed plug-ins list. Here, you can click on the bin icon or the Uninstall button to remove the plugin.

Step 4: After uninstalling the plugin, go to the AppStore tab, search for DeepL, and click on the Install button to reinstall the plugin.

Please note that it's important to ensure that your system has enough memory to run these processes. If the problem persists after following these steps, it might be a good idea to check your system's memory usage and close any unnecessary applications that might be running in the background.

I hope these steps help you resolve the issue. If you have any other questions or need further assistance, feel free to ask.

Best regards,

RWS Community AI

I have already explained that I use Trados 2024 and the DeepL plugin, both of which are the latest versions. And I have already explained that I have reinstalled the plugin several times. The ‘’System.OutOfMemoryException’ warning seems to occur when I create an action in the dialog “DeepL Translation Service Provider”.
Trying to activate the DeepL plugin by adding DeepL to the TMs immediately generates this allert, while opening the DeepL dialog in the existing activation of the DeepL API for NL De does nothing until I choose OK in the dialog, Then the alert is also triggered, and sometimes Studio quits at all.

Dieter Gust  for Katrien Vertommen.
I would like to give some additional ideas why this severe bug, not being able to use DeepL API in Trados any longer could happen: As I explained I experimented using the glossary functions.
I think that each ‘OK’ in the above dialog generates an API request to the server DeepL.
If you work ‘fast and efficient’ and change the setting of the dialogue ‘too fast’ several times, could this trigger several requests in a row that cannot be processed fast enough and therefore correctly?
Could it be that activating the dialog shown above uses a local JSON file or generally a ‘settings file’ and as a result of ‘too many’ requests in a short time, corrupted data is stored there, which leads to the message ‘System.OutOfMemoryException’ as soon as the dialog is activated?
Can I simply delete such a file?
Surely I shouldn't have to carry out a completely new Trados Studio installation?

Dieter Gust  for Katrien Vertommen.
I would like to give some additional ideas why this severe bug, not being able to use DeepL API in Trados any longer could happen: As I explained I experimented using the glossary functions.
I think that each ‘OK’ in the above dialog generates an API request to the server DeepL.
If you work ‘fast and efficient’ and change the setting of the dialogue ‘too fast’ several times, could this trigger several requests in a row that cannot be processed fast enough and therefore correctly?
Could it be that activating the dialog shown above uses a local JSON file or generally a ‘settings file’ and as a result of ‘too many’ requests in a short time, corrupted data is stored there, which leads to the message ‘System.OutOfMemoryException’ as soon as the dialog is activated?
Can I simply delete such a file?
Surely I shouldn't have to carry out a completely new Trados Studio installation?

Katrien Vertommen 

Just to save you wasting any more time on this we are currently working to make this more robust around the use of the plugin with glossaries and will release a new version in due course. 

We are not getting the problem you have, and this may be something else altogether so if you have any more details such as the full error stack it would be helpful as this might provide more information to help avoid guessing, but we are addressing some issues around the use of the API keys in association with glossaries.

Dieter Gust on behalf of Katrien Vertommen
Thanks Paul for your feedback. I executed the repair process of Trados Studio but this didn't help toget id of the "’System.OutOfMemoryException" alert.

The situation is getting stranger and stranger: Neither the repair process nor a complete reinstallation of Trados Studio or the creation of a new API key have changed anything: I keep getting the message. One of created log files I lsit here. I get so many log files during tryoing t activate DeepL support I don't know which one might be relevant. As we have a level 1 support I try to create a ticket and adding all log files in a zip file.

INFO [2024-09-02 17:38:25,876] TradosStudio.PushNotificationProvider.SignalRClient - Initializing client
ERROR [2024-09-02 17:38:26,945] Sdl.Desktop.Platform.ServerConnectionPlugin.Client.IdentityModel.UserCredentialRepository - Error reading GS servers
System.IO.DirectoryNotFoundException: Ein Teil des Pfades "C:\Users\Katrien\AppData\Roaming\Trados\Platform\Identity\SDLTradosStudio.exe\Servers.bin" konnte nicht gefunden werden.
   bei System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   bei System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   bei System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   bei System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize, Boolean checkHost)
   bei System.IO.File.InternalReadAllText(String path, Encoding encoding, Boolean checkHost)
   bei System.IO.File.ReadAllText(String path)
   bei Sdl.Desktop.Platform.Implementation.SystemIO.FileWrapper.ReadAllText(String path)
   bei Sdl.Desktop.Platform.ServerConnectionPlugin.Client.IdentityModel.UserCredentialRepository.Load()
INFO [2024-09-02 17:38:29,233] Sdl.Desktop.Platform.Implementation.Studio - Starting application service.
INFO [2024-09-02 17:38:29,536] Sdl.BestMatchServiceStudioIntegration.Common.DelegatingHandlers.ConnectivityHandler - Request with trace id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx for lc-api.sdl.com/.../sync-user-profile:
INFO [2024-09-02 17:38:30,230] Sdl.BestMatchServiceStudioIntegration.Common.DelegatingHandlers.ConnectivityHandler - Request response: OK traceId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
INFO [2024-09-02 17:38:30,330] Sdl.BestMatchServiceStudioIntegration.Common.DelegatingHandlers.ConnectivityHandler - Request with trace id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx for lc-api.sdl.com/.../accountsAndSettings:
INFO [2024-09-02 17:38:30,568] Sdl.BestMatchServiceStudioIntegration.Common.DelegatingHandlers.ConnectivityHandler - Request response: OK traceId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
INFO [2024-09-02 17:38:30,899] Sdl.BestMatchServiceStudioIntegration.Common.DelegatingHandlers.ConnectivityHandler - Request with trace id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx for lc-api.sdl.com/.../studioPackage:
INFO [2024-09-02 17:38:31,212] Sdl.BestMatchServiceStudioIntegration.Common.DelegatingHandlers.ConnectivityHandler - Request response: OK traceId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
INFO [2024-09-02 17:38:32,322] Sdl.TranslationStudio.LanguageCloud.Startup.LanguageCloudLogin - Language Cloud login successful.
INFO [2024-09-02 17:38:32,476] Sdl.TranslationStudio.ProjectManagement.AutoDeleteOnStartup - Deleting temporary files
INFO [2024-09-02 17:38:37,303] Sdl.BestMatchServiceStudioIntegration.Common.DelegatingHandlers.ConnectivityHandler - Request with trace id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx for lc-api.sdl.com/.../assigned:
INFO [2024-09-02 17:38:37,624] Sdl.BestMatchServiceStudioIntegration.Common.DelegatingHandlers.ConnectivityHandler - Request response: OK traceId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
INFO [2024-09-02 17:38:38,506] Sdl.TranslationStudio.ProjectManagement.ProjectManagementService - ProjectManagementService started: 1638 ms
INFO [2024-09-02 17:38:53,125] TradosStudio.PushNotificationProvider.SignalRClient - Configuring websocket connection
INFO [2024-09-02 17:38:53,125] TradosStudio.PushNotificationProvider.SignalRClient - TraceId for signalR connection: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
INFO [2024-09-02 17:38:53,331] TradosStudio.PushNotificationProvider.SignalRClient - Connection built has state Disconnected
INFO [2024-09-02 17:38:53,363] TradosStudio.PushNotificationProvider.SignalRClient - Connecting to push notification service
INFO [2024-09-02 17:38:53,457] Microsoft.AspNetCore.Http.Connections.Client.Internal.WebSocketsTransport - Starting transport. Transfer mode: Text. Url: 'wss://studio-push-notification.sdl.com/ProjectsHub'.
INFO [2024-09-02 17:38:53,824] Microsoft.AspNetCore.Http.Connections.Client.HttpConnection - HttpConnection Started.
INFO [2024-09-02 17:38:53,839] Microsoft.AspNetCore.SignalR.Client.HubConnection - Using HubProtocol 'json v1'.
INFO [2024-09-02 17:38:54,018] Microsoft.AspNetCore.SignalR.Client.HubConnection - HubConnection started.
INFO [2024-09-02 17:38:54,691] Sdl.AppStoreIntegration.Service.OfflineConnectivityHandler - Request with trace id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx for studio-appstore-api.azurewebsites.net/plugins Studio&studioVersion=18.0.0.1013:
INFO [2024-09-02 17:38:59,516] Sdl.TranslationStudio.Plugins.CommunityInside.Notifications.Service.OfflineConnectivityHandler - Request with trace id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx for community.rws.com/.../login:
INFO [2024-09-02 17:38:59,674] Sdl.Desktop.Platform.Implementation.ResourceLoggingInternalCommandExecuter - Start#Id=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx#Name=Verbindungsaufbau#ProcessName=SDLTradosStudio#PhysicalMemorySize=524480512#VirtualMemorySize=174735360#ThreadCount=34#HandleCount=1665#GdiHandleCount=855#UserHandleCount=452#TotalProcessorTime=00:00:21.2968750
INFO [2024-09-02 17:38:59,674] Sdl.Desktop.Platform.Implementation.ResourceLoggingInternalCommandExecuter - Finish#Id=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx#Name=Verbindungsaufbau#ProcessName=SDLTradosStudio#PhysicalMemorySize=524480512#VirtualMemorySize=174735360#ThreadCount=34#HandleCount=1665#GdiHandleCount=855#UserHandleCount=453#TotalProcessorTime=00:00:21.2968750
INFO [2024-09-02 17:38:59,977] TradosStudio.PushNotificationProvider.SignalRClient - Subscribing to project changes
INFO [2024-09-02 17:39:00,100] Sdl.TranslationStudio.Plugins.CommunityInside.Notifications.Service.OfflineConnectivityHandler - Request response: OK
INFO [2024-09-02 17:39:00,166] Sdl.AppStoreIntegration.Service.OfflineConnectivityHandler - Request response: OK
INFO [2024-09-02 17:39:00,196] Sdl.TranslationStudio.Plugins.CommunityInside.Notifications.Service.OfflineConnectivityHandler - Request with trace id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx for community.rws.com/.../notifications.json:
INFO [2024-09-02 17:39:00,485] Sdl.TranslationStudio.Plugins.CommunityInside.Notifications.Service.OfflineConnectivityHandler - Request response: OK
INFO [2024-09-02 17:39:01,256] Sdl.Desktop.Platform.Implementation.Services.Updater.UpdateClientCaller - Started TrueUpdate Process Id: 22684
INFO [2024-09-02 17:39:01,669] Sdl.AppStoreIntegration.Service.OfflineConnectivityHandler - Request with trace id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx for studio-appstore-api.azurewebsites.net/mapNames
INFO [2024-09-02 17:39:01,837] Sdl.AppStoreIntegration.Service.OfflineConnectivityHandler - Request response: OK
INFO [2024-09-02 17:39:01,907] Sdl.AppStoreIntegration.Service.OfflineConnectivityHandler - Request with trace id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx for studio-appstore-api.azurewebsites.net/.../categories:
INFO [2024-09-02 17:39:02,148] Sdl.AppStoreIntegration.Service.OfflineConnectivityHandler - Request response: OK
INFO [2024-09-02 17:39:04,491] Sdl.Desktop.Platform.Implementation.Services.Updater.UpdateClientCaller - TrueUpdate ProcessId=22684 has exited
INFO [2024-09-02 17:39:04,491] Sdl.Desktop.Platform.Implementation.Services.Updater.UpdateInfoReader - Trying to read file: C:\Users\Katrien\AppData\Local\Temp\Studio18Updates\FilteredUpdates.xml
INFO [2024-09-02 17:39:04,491] Sdl.Desktop.Platform.Implementation.Services.Updater.UpdateInfoReader - File not found
INFO [2024-09-02 17:39:14,523] Sdl.BestMatchServiceStudioIntegration.Common.DelegatingHandlers.ConnectivityHandler - Request with trace id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx for lc-api.sdl.com/.../assigned:
INFO [2024-09-02 17:39:14,801] Sdl.BestMatchServiceStudioIntegration.Common.DelegatingHandlers.ConnectivityHandler - Request response: OK traceId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
INFO [2024-09-02 17:39:18,222] Sdl.Desktop.Platform.Implementation.ResourceLoggingInternalCommandExecuter - Start#Id=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx#Name=ProjectSettingsContextAction#ProcessName=SDLTradosStudio#PhysicalMemorySize=603222016#VirtualMemorySize=242745344#ThreadCount=37#HandleCount=1809#GdiHandleCount=1025#UserHandleCount=553#TotalProcessorTime=00:00:24.7968750
FATAL [2024-09-02 17:39:41,163] Sdl.Desktop.Platform.UnhandledException - Eine Ausnahme vom Typ "System.OutOfMemoryException" wurde ausgelöst.
System.OutOfMemoryException: Eine Ausnahme vom Typ "System.OutOfMemoryException" wurde ausgelöst.
   bei System.String.SplitInternal(Char[] separator, Int32 count, StringSplitOptions options)
   bei System.String.Split(Char[] separator)
   bei Sdl.Community.DeepLMTProvider.GlobalSettings.DeserializeGlossaryIds(String[] globalSettingsSerialized)
   bei Sdl.Community.DeepLMTProvider.GlobalSettings.LoadGlossaryIds()
   bei Sdl.Community.DeepLMTProvider.GlobalSettings.GetLastUsedGlossaryId(ValueTuple`2 languagePair)
   bei Sdl.Community.DeepLMTProvider.ViewModel.DeepLWindowViewModel.GetSelectedGlossaryFromSavedSetting(List`1 glossaries, LanguagePairOptions languageSavedOptions, String sourceLangCode, String targetLangCode)
   bei Sdl.Community.DeepLMTProvider.ViewModel.DeepLWindowViewModel.<LoadLanguagePairSettings>d__63.MoveNext()
--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
   bei System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_0(Object state)
   bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   bei System.Windows.Threading.DispatcherOperation.InvokeImpl()
   bei System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
   bei MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(Object obj)
   bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   bei MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)
   bei System.Windows.Threading.DispatcherOperation.Invoke()
   bei System.Windows.Threading.Dispatcher.ProcessQueue()
   bei System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   bei MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   bei MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   bei System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
   bei MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   bei MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
   bei System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
   bei System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
   bei System.Windows.Window.ShowHelper(Object booleanBox)
   bei System.Windows.Window.Show()
   bei System.Windows.Window.ShowDialog()
   bei Sdl.Community.DeepLMTProvider.Studio.DeepLMtTranslationProviderWinFormsUI.Browse(IWin32Window owner, LanguagePair[] languagePairs, ITranslationProviderCredentialStore credentialStore)
   bei Sdl.TranslationStudio.Common.TranslationMemory.TranslationMemoriesControl.pluginContextMenuStripItem_Click(Object sender, EventArgs e)
   bei System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   bei System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   bei System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   bei System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   bei System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
   bei System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
   bei System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   bei System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   bei System.Windows.Forms.Control.WndProc(Message& m)
   bei System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   bei System.Windows.Forms.ToolStrip.WndProc(Message& m)
   bei System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
INFO [2024-09-02 17:39:41,167] Sdl.Desktop.Platform.UnhandledException - Eine Ausnahme vom Typ "System.OutOfMemoryException" wurde ausgelöst.#ProcessName=SDLTradosStudio#PhysicalMemorySize=1441980416#VirtualMemorySize=1094983680#ThreadCount=37#HandleCount=1851#GdiHandleCount=995#UserHandleCount=567#TotalProcessorTime=00:00:36.9375000
INFO [2024-09-02 17:39:53,219] Sdl.Desktop.Platform.Implementation.ResourceLoggingInternalCommandExecuter - Finish#Id=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx#Name=ProjectSettingsContextAction#ProcessName=SDLTradosStudio#PhysicalMemorySize=603222016#VirtualMemorySize=242745344#ThreadCount=37#HandleCount=1809#GdiHandleCount=1004#UserHandleCount=540#TotalProcessorTime=00:00:37.4375000
INFO [2024-09-02 17:40:00,694] Sdl.Desktop.Platform.Implementation.ResourceLoggingInternalCommandExecuter - Start#Id=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx#Name=ExitRibbonAction#ProcessName=SDLTradosStudio#PhysicalMemorySize=1444102144#VirtualMemorySize=1095618560#ThreadCount=34#HandleCount=1827#GdiHandleCount=995#UserHandleCount=537#TotalProcessorTime=00:00:37.9843750
INFO [2024-09-02 17:40:01,047] Sdl.BestMatchServiceStudioIntegration.Common.DelegatingHandlers.ConnectivityHandler - Request with trace id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx for lc-api.sdl.com/.../release
INFO [2024-09-02 17:40:01,234] Sdl.BestMatchServiceStudioIntegration.Common.DelegatingHandlers.ConnectivityHandler - Request response: OK traceId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

Katrien Vertommen 

I recovered your post from the moderation queue as it was put in there by the system because you posted a lot of code in the post as if it was text... we do see this sort of thing happening from spammers and hackers so the system automatically protects us and our users if it's suspicious.  Better to zip logs files and attach them, or do as I have done above and insert it as a code block using the menu (Insert -> Code).

The support team will probably pass any logs you sent them over to us (AppStore Team) at some point as apps are not covered by your support agreement, and we'll review.  But what you have provided us with here is enough for now.

I mentioned already that we are working on a new release anyway as there is a problem we have to address (so no need to keep trying with a version that has a problem you won't be able to fix), and this info will provide us with something else to check in case this is a problem of the plugin and not your own environment having memory management problems.

Look out for updates in the next weeks.

Thank you very much

Hi Paul,

This is not about the glossaries but about installing the DeepL plugin. Forget about the glossaries, but since we once tried to activate the glossary we cannot add the DeepL Plugin any more without Trados crashing each time. So I assume this issue is part of the Support Agreement.

Best regards,

Katrien

Katrien Vertommen 

Katrien Vertommen said:

since we once tried to activate the glossary we cannot add the DeepL Plugin any more without Trados crashing each time. So I assume this issue is part of the Support Agreement.

No it won't be.  If the plugin is completely removed do you still have this problem?  If you don't then that's all support need to do.

Yes I have uninstalled Trads Studio and the DeepL plugin and reinstalled the software.
AInd I ordered a new API key for the DeepL plugin. But this diidn't change the situation: I cannot use DeepL support any longer: When I try to activate the DeepL Translation Service Provider the error message  "System.OutOfMemoryException" is produced. And in some cases the whole Trados Studio Software crashes. That's why I created a support case also.

Katrien Vertommen 

Can you delete these files/folders?  Then try the plugin again but don't attempt to use glossaries yet?

c:\Users\[USERNAME]\AppData\Roaming\Trados AppStore\DeepL\

c:\Users\[USERNAME]\AppData\Roaming\Trados AppStore\DeepLLogs\

c:\Users\[USERNAME]\AppData\Roaming\Trados\Trados Studio\18\Plugins\Packages\DeepL Translation Provider.sdlplugin

c:\Users\[USERNAME]\AppData\Roaming\Trados\Trados Studio\18\Plugins\Unpacked\DeepL Translation Provider\

That may help you use the plugin for translation at least.

Wonderful! You gave the solution!
We did not clean up all of the folders you mentioned before and now yes, yes, yes!
DeepL API is working again, great!
No, we will not use DeepL glossaries again until a new update and the corresponding help will name it a robust feature!