Sameh Elsharkawy 

I don't think the memory referred is a TM.  It's a bit hard to see any solid reason for this, but it could be due to a plugin used to modify something while in the Editor view (not necessarily a Studio plugin eiither... could be anything that is being used to modify text  during UI interaction.  Could be graphics driver problems... so worth making sure you're up to date.  Could even be old or 3rd party dlls if you're working with an old project template for example.

So a few things to check there.  Worth restoring Studio to its vanilla state and see if the problem still occurs?  I know you may not like that idea, but it's the first thing the support team will do if we involve them, so worth you ruling this out yourself first.

Thanks Paul, but the message clearly indicated a corrupt TM!! I will try to replicate this and see if the error comes again, but I doubt it has to do with any of the above suggestions, yet I will keep them in mind. 

Sincerely,

Sameh

Now it happened again Paul while copying a tag to paste in the target! 

<SDLErrorDetails time="4/11/2025 11:53:03 PM">
  <ErrorMessage>Attempted to read or write protected memory. This is often an indication that other memory is corrupt.</ErrorMessage>
  <Exception>
    <Type>System.AccessViolationException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <HelpLink />
    <Source>Sdl.DesktopEditor.Control</Source>
    <HResult>-2147467261</HResult>
    <StackTrace><![CDATA[   at Tree.DocumentControl.vl_WindowProc(DocumentControl* , HWND__* , UInt32 , UInt32 , Int32 )
   at FrameworkDocumentControl.vl_WindowProc(FrameworkDocumentControl* , HWND__* h_wnd, UInt32 n_msg, UInt32 w_p, Int32 l_p)
   at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at System.Windows.Forms.NativeWindow.DefWndProc(Message& m)
   at System.Windows.Forms.Control.DefWndProc(Message& m)
   at System.Windows.Forms.Control.WmMouseMove(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>Trados Studio</ProductName>
    <ProductVersion>Studio18</ProductVersion>
    <EntryAssemblyFileVersion>18.0.2.3255</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 10 Pro</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1033</OperatingSystemLanguage>
    <CodePage>1256</CodePage>
    <LoggedOnUser>ADMINSAM\Ahmed</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>ADMINSAM</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>50276084 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

Now I can 100% confirm that this issue is happening when copying tags from source to target. It happened so many times now. The question now is why this is happening?  Any help would be appreciated. 

 Sameh Elsharkawy 

Sameh Elsharkawy said:

the message clearly indicated a corrupt TM

I don't believe it does.  The exception is a System.AccessViolationException, which is a low-level memory error, typically raised when unmanaged code (code that is executed directly by the operating system, outside of the control of the .NET Common Language Runtime (CLR). In contrast, managed code is executed under the supervision of the CLR, which provides features like memory management, garbage collection, type safety, and exception handling.) tries to access protected or invalid memory.  The message “Attempted to read or write protected memory. This is often an indication that other memory is corrupt.” points to a UI or rendering issue, rather than a problem reading or writing to a TM file.

Sameh Elsharkawy 

Sameh Elsharkawy said:

Now I can 100% confirm that this issue is happening when copying tags from source to target.

For you I'm sure it does.  I cannot reproduce this at all.

Sameh Elsharkawy said:

I will try to replicate this and see if the error comes again, but I doubt it has to do with any of the above suggestions, yet I will keep them in mind. 

Please confirm you can reproduce this after working through the suggestions you don't think will help.  If you have a vanilla Studio and the problem still occurs then we definitely have to fix something in Studio.  If it doesn't then add back the things you removed (I know you have a lot of things installed to supplement working with Trados) one at a time until you find out which thing is triggering this behaviour.