-
-
Notifications
You must be signed in to change notification settings - Fork 429
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
Crash with server 2012 r2 #28
Comments
Try to disable "Show memory clean result" and repeat tests. |
Ok, thanks
I try
De : Henry++ [mailto:notifications@github.com]
Envoyé : mardi 29 août 2017 14:23
À : henrypp/memreduct <memreduct@noreply.github.com>
Cc : GOERING Yves <yves.goering@mipe.fr>; Author <author@noreply.github.com>
Objet : Re: [henrypp/memreduct] Crash with server 2012 r2 (#28)
Try to disable "Show memory clean result" and repeat tests.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#28 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/Ad_ATyEMzwp9A2yUXu9B02neBfmBna-3ks5sdAKZgaJpZM4PF1B6>.
|
So what? |
So good
Thanks
Cordialement
Envoyé de mon téléphone.
Yves Goering
…________________________________
From: Henry++ <notifications@github.com>
Sent: Monday, September 4, 2017 5:26:35 PM
To: henrypp/memreduct
Cc: GOERING Yves; Author
Subject: Re: [henrypp/memreduct] Crash with server 2012 r2 (#28)
Ok, thanks
I try
So what?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#28 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/Ad_AT6fN3HaVhjxsB_QQ_QiDzKNSi7Ivks5sfBargaJpZM4PF1B6>.
|
3.2.2 fixed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The software is nice, but crash on windows 2012r2 operating system after cleaning.
we have a 128 Gb RAM server and if the memory is used arround or more than 30%, your software do the job and crash . if the memory is low, no any problem
The text was updated successfully, but these errors were encountered: