-
Notifications
You must be signed in to change notification settings - Fork 769
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
Docs should include guidance on using Pylance on low power devices #5881
Comments
Thanks. If you need more details then please let me know |
Can you include a log as described here? https://github.com/microsoft/pylance-release/blob/main/TROUBLESHOOTING.md#filing-an-issue My suspicion is that we're running out of memory. There are some things we outline here that you can do to alleviate that problem: |
another data that could be helpful is providing this info (https://github.com/microsoft/pylance-release/wiki/Collecting-data-for-an-investigation.#collecting-cpuprofiles) basically do
and provide the profile data to us. |
I suspect out of memory too, the device only has 1GB RAM of which the container only really gets about 400-500MB. For reference this is running on a Dual ARM Cortex-A9 MPCore (600MHz). I shall attempt some profiling but will need to ensure no sensitive info is in the logs, so please bear with me. It might also be tricky to get a representative profile of the full issue since that would cause a full crash. Will do my best! |
@luabud we might want to add basically, only enables these features and turn off everything else.
turn off
basically, we provide only cheap features that help typing but nothing else. it will be a little bit better than plain text. |
// No user files
"python.analysis.exclude": ["**"],
// Expensvie to turn on
"python.analysis.indexing": false,
"python.analysis.fixAll": [],
"python.analysis.diagnosticMode": "openFilesOnly",
"python.analysis.enablePytestSupport": false,
"python.analysis.inlayHints.callArgumentNames": "off",
"python.analysis.inlayHints.functionReturnTypes": false,
"python.analysis.inlayHints.pytestParameters": false,
"python.analysis.inlayHints.variableTypes": false,
"python.analysis.supportRestructuredText": false,
"python.analysis.typeCheckingMode": "off",
"python.analysis.useLibraryCodeForTypes": false,
// vscode settings that affect pylance feature but
// expensive to turn on
"editor.semanticHighlighting.enabled": false,
"editor.occurrencesHighlight": "off",
// okay to turn on if they want to
"python.analysis.completeFunctionParens": false,
"python.analysis.autoFormatStrings": false,
"python.analysis.autoImportCompletions": false,
"python.analysis.gotoDefinitionInStringLiteral": false, here are settings user would want to make with this settings, editor related features such as Users can enable specific settings to activate features they want, however, because many features share the same underlying engines, enabling one feature might result in resource consumption similar to that of enabling multiple features. |
From Marketplace review:
The text was updated successfully, but these errors were encountered: