Why Does Changing My C# Project's Build Platform Fix 'Attempted to Read or Write Protected Memory'?

Troubled by "Attempted to Read or Write Protected Memory"?

Problem Description:

You're experiencing a perplexing error: "Attempted to read or write protected memory. This is often an indication that other memory is corrupt." This error plagues your multi-threaded C# server application, halting its execution anywhere from 12 to 48 hours into operation.

Understanding the Error:

This error suggests that an invalid memory location is being accessed or an attempt to manipulate protected memory is occurring. This is often the result of a corrupted area of memory elsewhere in the system.

Specific Cause in This Case:

While the error can have numerous causes, a peculiar solution has been discovered for this particular case:

Solution:

A change in the Platform for Build from x86 to Any CPU and back to x86 has resolved the issue.

Conclusion:

While the underlying cause of this error can vary, this specific solution provides a potential fix. By adjusting the Platform for Build, you may successfully eliminate the "Attempted to read or write protected memory" error in your .NET application.

The above is the detailed content of Why Does Changing My C# Project's Build Platform Fix 'Attempted to Read or Write Protected Memory'?. For more information, please follow other related articles on the PHP Chinese website!