-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modify error message for failed RW mappings #102458
Conversation
Tagging subscribers to this area: @mangod9 |
@ayende, @loop-evgeny, does the modified message sound sufficient to you? |
I would mention the configuration item explicitly, or add a specific term that you can search by it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A suggestion that explicitly mention the actual probem.
@@ -905,7 +905,7 @@ void* ExecutableAllocator::MapRW(void* pRX, size_t size, CacheableMapping cacheM | |||
|
|||
if (pRW == NULL) | |||
{ | |||
g_fatalErrorHandler(COR_E_EXECUTIONENGINE, W("Failed to create RW mapping for RX memory")); | |||
g_fatalErrorHandler(COR_E_EXECUTIONENGINE, W("Failed to create RW mapping for RX memory. This can be caused by not enough memory or by exceeding the configured maximum number of memory mappings.")); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
g_fatalErrorHandler(COR_E_EXECUTIONENGINE, W("Failed to create RW mapping for RX memory. This can be caused by not enough memory or by exceeding the configured maximum number of memory mappings.")); | |
g_fatalErrorHandler(COR_E_EXECUTIONENGINE, W("Failed to create RW mapping for RX memory. This can cause by insufficient memory or hitting the limit of memory mapping on Unix (vm.map_max_count).")); |
g_fatalErrorHandler(COR_E_EXECUTIONENGINE, W("Failed to create RW mapping for RX memory. This can be caused by not enough memory or by exceeding the configured maximum number of memory mappings.")); | |
g_fatalErrorHandler(COR_E_EXECUTIONENGINE, W("Failed to create RW mapping for RX memory. This can be caused by not enough memory or by exceeding the configured maximum number of memory mappings.")); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, sounds good. I'll just change "Unix" to "Linux", as that setting is Linux specific.
I like ayende's wording! |
The executable allocator can fail to create a RW mapping for an existing RX mapping due to both being out of memory and exceeding maximum number of memory mappings. People were getting confused by the original error message. This chnage updates it to explicitly mention the cases when it can occur.
12289ff
to
b8bd95d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
The executable allocator can fail to create a RW mapping for an existing RX mapping due to both being out of memory and exceeding maximum number of memory mappings. People were getting confused by the original error message. This chnage updates it to explicitly mention the cases when it can occur.
The executable allocator can fail to create a RW mapping for an existing RX mapping due to both being out of memory and exceeding maximum number of memory mappings. People were getting confused by the original error message. This chnage updates it to explicitly mention the cases when it can occur.
The executable allocator can fail to create a RW mapping for an existing RX mapping due to both being out of memory and exceeding maximum number of memory mappings. People were getting confused by the original error message.
This change updates it to explicitly mention the cases when it can occur.