microsoft / AL

Home of the Dynamics 365 Business Central AL Language extension for Visual Studio Code. Used to track issues regarding the latest version of the AL compiler and developer tools available in the Visual Studio Code Marketplace or as part of the AL Developer Preview builds for Dynamics 365 Business Central.
MIT License
718 stars 242 forks source link

Out Of Memory (OOM) Error Opening AL Project Folder #7765

Open wm-camelot opened 3 weeks ago

wm-camelot commented 3 weeks ago

Please include the following with each issue:

1. Describe the bug When opening an AL project folder I receive the following error: image

Using Help: Start Extension Bisect I was able to narrow down the issue to the AL Language Extension for Microsoft Dynamics 365 Business Central: image

In an attempt to clear any cache files causing issues I deleted all files in the following folders:

Inside of C:\Users\%USERPROFILE%\AppData\Roaming\Code\Crashpad\reports I found a series of DMPs. I attached two different files that were generated during the crashes so that you may review. 05a1701c-56fc-4e52-b120-b5bef21dd499.dmp 3b91a8f1-354f-4a3c-a007-2a3f110879b8.dmp

2. To Reproduce Steps to reproduce the behavior:

  1. Open Visual Studio Code
  2. Press Ctrl+K, Ctrl+O to open the target folder
  3. Wait ~3 seconds
  4. OOM Error is produced

3. Expected behavior I would expect that I am able to open and load my AL project, allowing me to benefit from IntelliSense, code completion, and other features of the AL extension.

4. Actual behavior Instead, within ~3 seconds of opening the AL project Visual Studio Code freezes and provides the following error: image

5. Versions:

Final Checklist

Please remember to do the following:

thloke commented 2 weeks ago

To help us investigate this, can you answer the following?

  1. Does this reproduce on a specific project/workspace, or all projects?
  2. If it is a specific project, is it particularly large? What is the estimate of the number of application objects in the project?
  3. Do you have a minimal repro project that you can share?
  4. What settings have you enabled for the extension in your settings.json?
  5. Can you share the verbose telemetry logs? To do that, do the following:
  1. In your VSCode settings.json, set "al.editorServicesLogLevel": "Verbose"
  2. Reproduce the scenario
  3. Under the path C:\Users\<username>\.vscode\extensions\ms-dynamics-smb.al-<version>\bin\win32, collect the editorservice.log and debuggerservices.log files.
wm-camelot commented 2 weeks ago

Answers to questions below:

  1. This is currently only an issue for one project
  2. Project is fairly large with 679 total objects, total project size (including .app dependencies) is 68.2 MB. However, I can successfully open the Base App project (version 23.0.12034.12841) from the DVD without any issues. The Base App is 8363 total objects, total project size (including .app dependencies) is 367 MB). I can open other custom projects and Microsoft projects with various sizes and total objects without issue.
  3. I don't think I have a way to share the project with you, however I did just copy the project to a different location on my C drive and the project loaded successfully when opened via VSCode. Would you have a suggestion based upon that scenario?
  4. The following settings are enabled for the extension:
    • image
    • image
  5. Attached the EditorServices.log but a debuggerservices.log was not generated upon reproducing the error (see below)