Skip to content
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

Very bad debugger performance #6520

Closed
NKarolak opened this issue Mar 9, 2021 · 7 comments
Closed

Very bad debugger performance #6520

NKarolak opened this issue Mar 9, 2021 · 7 comments
Assignees
Labels
bug Product bug debugger Issues related to the debugger

Comments

@NKarolak
Copy link

NKarolak commented Mar 9, 2021

Describe the bug
Likely depending on the object that the debugger is currently in, the startup, loading of variables or moving to the next step takes a very long time (10 seconds), making it unable to use.

According to #5882 (comment), I've created a DebuggerServices.log with a verbose log level.
I will pass it personally to @kalberes, because it contains fragments of our IP.

Versions:

  • AL Language: 6.6.425415
  • VS Code: 1.54.1
@atoader atoader added bug Product bug debugger Issues related to the debugger labels Mar 9, 2021
@NKarolak
Copy link
Author

NKarolak commented Mar 9, 2021

@DTKB Did you encounter this as well?

@dzzzb
Copy link

dzzzb commented Mar 9, 2021

Yeah, I have noticed some quite long delays. The BC client freezes up, and VS Code starts to flash in the taskbar that it has something for me - both in fairly normal times - but then I have to sit and wait while VS Code realises that it needs to focus a particular file/line and show the debugging info for it. I didn't yet investigate to ascertain whether it's universal or affected by any particular features of projects.

@NKarolak
Copy link
Author

NKarolak commented Mar 9, 2021

In my case, it seems to be related that the initial variable loading takes lots of time. The debugger itself opens quickly, but when you try to open any of the variables sections (e.g. Locals), you only see some progress indicator ... Wait 10 seconds until it's loaded, then you continue with the debugger, but that variable problem repeats in the next step. Really weird.

@kalberes
Copy link
Contributor

kalberes commented Mar 9, 2021

Looks like in case of Natalie, RecRef.GetTable has severe perf issues resolving AL variables from the associated(codegened) .net variables.
I will investigate it as far as I have some time.

@NKarolak
Copy link
Author

My issue is currently on hold due to another extension (see automatic comment above). I will update or close this case as soon as possible.

@martonsagi
Copy link

Hey, this issue was caused by a custom Reference provider in AL Studio extension, the provider ran excessively in debug mode. I have fixed the issue with the help of @NKarolak

@kalberes
Copy link
Contributor

kalberes commented Mar 12, 2021

@NKarolak , @martonsagi
Thanks for the info.
Maybe we need to update our template that when something is reproduced then it should only be with MS based AL extensions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Product bug debugger Issues related to the debugger
Projects
None yet
Development

No branches or pull requests

5 participants