Skip to content
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

can't dump RAM #44

Open
cofarmer opened this issue Aug 1, 2022 · 3 comments
Open

can't dump RAM #44

cofarmer opened this issue Aug 1, 2022 · 3 comments

Comments

@cofarmer
Copy link

cofarmer commented Aug 1, 2022

image
With DbgView.exe,the value of number_of_runs == 50, so dump ram failed here.

@vivianezw
Copy link
Collaborator

#10

Dynamic Memory in Hyper-V is enabled? This leads to fragmentation of thousands of memory ranges.

@cofarmer
Copy link
Author

Run in VMware 16+

@vivianezw
Copy link
Collaborator

You have more than the usual number of runs. You should look into the vmware settings for something causing the behavior, it would have to be something with memory management.

The sanity check limits the number of runs to a current maximum of 20 runs. Typically it would be something around 10. Technically we could afford more, just not 1000 like it happens with HV after a while with dynamic memory on. I suspect a similar mechanism is happening on Vmware.
It would be interesting to know how many runs you got in this case (more than 20, for sure :D).

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

No branches or pull requests

2 participants