Nightly extension seems to hang when loading metadata

[bnjbvr]

Hi! I'm on Windows 10, using VSCode 1.55.2, with Rust-analyzer nightly (according to the RA version command). As a sidenote, I didn't think I explicitly chose nightly when installing the addon from the available vscode extensions, is that the default?
Anyhow I'm trying to build a large Rust binary, and it seems the rust-analyzer binary keeps getting stuck loading metadata of random dependencies, and not even large ones (e.g. libm, . It seems most dependencies' metadata is loaded right away, but at some point it gets stuck on one randomly. In this case, there's no noticeable CPU activity or disk activity.

On the other hand, full builds in a bash CLI window works perfectly fine, so that seems to be an issue in rust-analyzer.

Please let me know if I can help debug this with logs!

[bjorn3]

It being reported as nightly was a bug that has been fixed two days ago: #8239.

[BlackHoleFox]

I am seeing this bug on the Nightly version of the extension, so perhaps there is more to it. It basically chooses at random which crate it wants to freeze up on.

As of sending this, its been spinning here for 7 minutes, holding a Cargo.lock file lock for the entire time D:

Version: 0.3.560-nightly
OS: Windows 10

Heres my client startup logs if they help at all:

INFO [4/17/2021, 12:51:34 AM]: Extension version: 0.3.560-nightly
INFO [4/17/2021, 12:51:34 AM]: Using configuration {
  cargoRunner: null,
  runnableEnv: null,
  inlayHints: {
    enable: true,
    chainingHints: true,
    maxLength: 25,
    parameterHints: true,
    typeHints: true
  },
  updates: { channel: 'nightly', askBeforeDownload: true },
  server: { path: null, extraEnv: null },
  trace: { server: 'off', extension: false },
  debug: {
    engine: 'auto',
    sourceFileMap: {
      '/rustc/<id>': '${env:USERPROFILE}/.rustup/toolchains/<toolchain-id>/lib/rustlib/src/rust'
    },
    openDebugPane: false,
    engineSettings: {}
  },
  assist: {
    importMergeBehavior: 'full',
    importPrefix: 'plain',
    importGroup: true
  },
  callInfo: { full: true },
  cargo: {
    autoreload: true,
    allFeatures: true,
    features: [],
    runBuildScripts: true,
    useRustcWrapperForBuildScripts: true,
    noDefaultFeatures: false,
    target: null,
    noSysroot: false,
    loadOutDirsFromCheck: true
  },
  checkOnSave: {
    enable: true,
    allFeatures: null,
    allTargets: true,
    command: 'clippy',
    noDefaultFeatures: null,
    target: null,
    extraArgs: [],
    features: null,
    overrideCommand: null
  },
  completion: {
    addCallArgumentSnippets: true,
    addCallParenthesis: true,
    postfix: { enable: false },
    autoimport: { enable: true }
  },
  diagnostics: {
    enable: true,
    enableExperimental: true,
    disabled: [ 'incorrect-ident-case' ],
    warningsAsHint: [],
    warningsAsInfo: []
  },
  files: { watcher: 'client', excludeDirs: [] },
  hoverActions: {
    debug: true,
    enable: true,
    gotoTypeDef: true,
    implementations: true,
    run: true,
    linksInHover: true
  },
  lens: {
    debug: true,
    enable: true,
    implementations: true,
    run: true,
    methodReferences: false,
    references: false
  },
  linkedProjects: [],
  lruCapacity: 256,
  notifications: { cargoTomlNotFound: true }, // Dunno why it says this, Im in a valid project.
  procMacro: { enable: true, server: null },
  runnables: { overrideCargo: null, cargoExtraArgs: [] },
  rustcSource: null,
  rustfmt: { extraArgs: [], overrideCommand: null }
}
INFO [4/17/2021, 12:51:34 AM]: PersistentState: {
  lastCheck: 1618629240813,
  releaseId: 41574990,
  serverVersion: '0.3.560-nightly'
}
INFO [4/17/2021, 12:51:34 AM]: Using server binary at c:\Users\User\AppData\Roaming\Code - Insiders\User\globalStorage\matklad.rust-analyzer\rust-analyzer-x86_64-pc-windows-msvc.exe

[jonas-schievink]

We will probably need a code base that reproduces this problem in order to fix it

[ChayimFriedman2]

To me it occured in the codebase of rust-analyzer itself (checked only yesterday, so I'm not sure if it's still there).

[BlackHoleFox]

I'm able to consistently reproduce the issue in a GearBot repository.

[jonas-schievink]

Hmm, I can't reproduce it on Linux with the GearBot repo, and the rust-analyzer repo also works fine for me

[lnicola]

@ChayimFriedman2 are you also using Windows?

[ChayimFriedman2]

Yes.

[BinChengZhao]

I am in the same situation:.

OS: win10
rustc: stable-x86_64-pc-windows-msvc

Always blocking at 'Loading: metadata *'

[joshmossas]

I'm experience the same issue with Windows 10, VSCode, and rust-analyzer v0.2.563. I just spins for forever and it seems to get stuck on a different crate each time.

This is a brand new project. I just ran cargo new my-project and then added bevy v0.5 as a dependency.

I've gotten around this by doing the following:

• disable rust-analyzer extension
• run cargo build
• reenable rust-analyzer and now it loads up fine

However when I add a new dependency I have to repeat the process.

EDIT:
It seems in some cases I need to do

• disable rust-analyzer
• runcargo build
• run cargo check
• reenable rust-analyzer

[lnicola]

Looks like this is Windows only and is related to our RUSTC_WRAPPER shenanigans. Our wrapper process closes, but its parent cargo hangs for some reason:

[stanciuadrian]

Mine is stuck here too:

with the environment:

If I run cargo check --workspace --message-format=json --manifest-path Cargo.toml --all-targets, the process ends successfully.