Suppress info strings before 'uci' #3147
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
On Windows, Stockfish wouldn't launch in some GUI because we output some info strings (about the use of large pages) before sending the 'uci' command. It seems more robust to suppress these info strings, and instead to add a proper section section in the Readme about large pages use. For easier reference, here is the section on this subject of the Readme. The use of large pages requires "Lock Pages in Memory" privilege. See the links under this paragraph to learn how to enable this privilege, and the RAMMap utility to double-check that large pages are used. We suggest that you reboot your computer after you have enabled large pages, because long Windows sessions suffer from memory fragmentation which may prevent Stockfish from getting large pages -- a fresh session is better in this regard. Large pages: https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/enable-the-lock-pages-in-memory-option-windows RAMMap : https://docs.microsoft.com/en-us/sysinternals/downloads/rammap --- Fixes official-stockfish/Stockfish#3052 (comment) Closes official-stockfish/Stockfish#3147 No functional change
snicolet
force-pushed
the
info_string
branch
from
3fcdf6f
to
2ea4cbe
Compare
Dantist
pushed a commit
to Dantist/Stockfish
that referenced
this pull request
Dec 22, 2020
On Windows, Stockfish wouldn't launch in some GUI because we output some info strings (about the use of large pages) before sending the 'uci' command. It seems more robust to suppress these info strings, and instead to add a proper section section in the Readme about large pages use. fixes official-stockfish#3052 closes official-stockfish#3147 No functional change
BM123499
pushed a commit
to BM123499/Stockfish
that referenced
this pull request
Feb 22, 2021
On Windows, Stockfish wouldn't launch in some GUI because we output some info strings (about the use of large pages) before sending the 'uci' command. It seems more robust to suppress these info strings, and instead to add a proper section section in the Readme about large pages use. fixes official-stockfish#3052 closes official-stockfish#3147 No functional change
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On Windows, Stockfish wouldn't launch in some GUI because we output some
info strings (about the use of large pages) before sending the 'uci'
command. It seems more robust to suppress these info strings, and instead
to add a proper section section in the Readme about large pages use. For
easier reference, here is the section on this subject of the Readme.
The use of large pages requires "Lock Pages in Memory" privilege. See
the links under this paragraph to learn how to enable this privilege,
and the RAMMap utility to double-check that large pages are used. We
suggest that you reboot your computer after you have enabled large pages,
because long Windows sessions suffer from memory fragmentation which may
prevent Stockfish from getting large pages -- a fresh session is better in
this regard.
Large pages: https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/enable-the-lock-pages-in-memory-option-windows
RAMMap : https://docs.microsoft.com/en-us/sysinternals/downloads/rammap
Fixes #3052 (comment)
Closes #3147
No functional change