
Same for VSCode

I've left the error logging on the bottom.
It seems to crash when i do "use std::thread;"
It may crash with other modules, but i noticed with this one.
Steps to replicate
I'm following the steps from https://github.com/rust-lang/rust-enhanced#rls
Then created a binary package with the example from https://doc.rust-lang.org/std/collections/struct.BTreeMap.html#examples
Error
The error i get back is fatal runtime error: allocator memory exhausted:
I'm not sure if there's any better way of debugging this
I think this is related to https://github.com/rust-lang-nursery/rls/issues/632
I have the same error. It has been introduced since 2017-12-06.
Logs from working version: https://pastebin.com/2QhNV2r5
Logs from broken version: https://pastebin.com/c1gHTzUk
I can stop the broken version crashing by commenting out every use, mod and extern crate statement in my code. But as soon as I uncomment the first one use std::path::Path, it dies.
As a temporary workaround, I've downgraded to the 2017-12-07 nightly toolchain. I used the following command:
rustup install nightly-2017-12-07
and set the following in my vscode config:
"rust-client.channel": "nightly-2017-12-07"
Same here when adding use std::io::Read or use std::io::File in VSCode using either rls-vscode or vscode-rust in RLS mode.
it seems that https://github.com/rust-lang-nursery/rls/commit/2333a2872d636ae31fbf032665fbdff722cb467d fixed the allocator memory exhausted error, could you see if it's fixed? (using RLS that contains the commit, when released, or using the compiled version from master)
Will give it a try in a few days after the holidays.
Experiencing the same error with Emacs using lsp-rust
Here is my stderr log:
https://gist.github.com/skeleten/791d8298e56994d7dabf87b32f08ff34
Using current nightly (rls-preview 0.124.0-nightly, 299a6a9 2017-12-25) the allocator error is gone. However, it is failing with following error (when using lsp-rust)
thread 'request-worker-0' panicked at 'called
Result::unwrap()on anErrvalue: Missing', /checkout/src/libcore/result.rs:916:5
The error I had been experiencing is gone with the current nightly.
Most helpful comment
I have the same error. It has been introduced since 2017-12-06.
Logs from working version: https://pastebin.com/2QhNV2r5
Logs from broken version: https://pastebin.com/c1gHTzUk
I can stop the broken version crashing by commenting out every use, mod and extern crate statement in my code. But as soon as I uncomment the first one
use std::path::Path, it dies.As a temporary workaround, I've downgraded to the 2017-12-07 nightly toolchain. I used the following command:
rustup install nightly-2017-12-07and set the following in my vscode config:
"rust-client.channel": "nightly-2017-12-07"