Slava Egorov

> I've posted the full message in a first topic. I am interested in the message code (e.g. `deprecated_member_use`) which is part of the whole warning printed by the analyzer...

I am wondering if it is some other tool (e.g. custom_lint?) or something else (e.g. using outdated analyzer with newer core libs?) which displays these.

There is an indication that we can somehow get into a state where we report incorrect warnings, see https://github.com/dart-lang/sdk/issues/62013#issuecomment-3555304271 @scheglov do you have any hypothesis around how this can happen?...

If you upgrade Flutter SDK while analysis server is running then you will end up in a situation where on-disk SDK is updated, but DAS process is using old version....

@JonasJW what is your current experience with analysis performance? Are you still experiencing this weird behavior?

@larssn not much we can do about that `qemu` which is taking most your memory, but with respect to analyzer: can you look at the analyzer diagnostic page (e.g. `Dart:...

@larssn thanks! unfortunately the report does not contain the most useful information about analyzer memory usage, due to a regression which accidentally snuck in when we changed how LSP is...

> Is this fixed now, or does something need updating in the LSP server? I will take a look at it next. I have a work-around but I want to...

@larssn hmm, strange. Lets try again: I have added more logging so we can at least see what is going wrong: ```console $ dart pub global activate -sgit https://github.com/mraleph/dart_lsp_collect_global_report Package...

Thanks! Top memory consumers seem to be: | className | bytesCurrent | |---|---| | _OneByteString | 582472320 | | Declaration | 429231360 | | _Uint8List | 308044912 | | _List...