Skip to content

Conversation

rajatd
Copy link
Contributor

@rajatd rajatd commented Jul 26, 2018

If we failed to reserve memory for the pre-reserved section when initializing the jit server thread context, when the jit process does the reservation, the client process has no way of knowing the start address of the pre-reserved section.

Instead, don't try to allocate memory for jitted code in pre-reserved section if we couldn't reserve when initializing server thread context

@rajatd rajatd requested a review from MikeHolman July 26, 2018 19:24
Copy link
Contributor

@MikeHolman MikeHolman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@chakrabot chakrabot merged commit 4a3ce7b into chakra-core:release/1.10 Jul 26, 2018
chakrabot pushed a commit that referenced this pull request Jul 26, 2018
…when initializing server thread context. OS#15209418

Merge pull request #5536 from rajatd:prereserved

If we failed to reserve memory for the pre-reserved section when initializing the jit server thread context, when the jit process does the reservation, the client process has no way of knowing the start address of the pre-reserved section.

Instead, don't try to allocate memory for jitted code in pre-reserved section if we couldn't reserve when initializing server thread context
chakrabot pushed a commit that referenced this pull request Jul 26, 2018
…erved section when initializing server thread context. OS#15209418

Merge pull request #5536 from rajatd:prereserved

If we failed to reserve memory for the pre-reserved section when initializing the jit server thread context, when the jit process does the reservation, the client process has no way of knowing the start address of the pre-reserved section.

Instead, don't try to allocate memory for jitted code in pre-reserved section if we couldn't reserve when initializing server thread context
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants