Skip to content

EditorServices.log logfile takes extremely large amount of disk size [macOS] #679

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

Closed
peterblazejewicz opened this issue Apr 13, 2017 · 13 comments
Labels
Area-Logging Issue-Bug A bug to squash. Resolution-Fixed Will close automatically.

Comments

@peterblazejewicz
Copy link

  • Operating system name and version:
    macOS 10.12.4 (16E195)
  • VS Code version:
    Version 1.12.0-insider (1.12.0-insider) a5e9d3b5e8e7e9a89dd6624a70aab031f189a6fa
  • PowerShell extension version:
    0.11.0
  • Output from $PSVersionTable:
$PSVersionTable                                                                                                         

Name                           Value                                                                                                                         
----                           -----                                                                                                                         
PSVersion                      6.0.0-alpha                                                                                                                   
PSEdition                      Core                                                                                                                          
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}                                                                                                       
BuildVersion                   3.0.0.0                                                                                                                       
GitCommitId                    v6.0.0-alpha.10                                                                                                               
CLRVersion                                                                                                                                                   
WSManStackVersion              3.0                                                                                                                           
PSRemotingProtocolVersion      2.3                                                                                                                           
SerializationVersion           1.1.0.1 

Issue Description

I am experiencing a problem with extremely huge output size of extension log.
Path: /Users/piotrblazejewicz/.vscode-insiders/extensions/ms-vscode.powershell-0.11.0/logs/1492023659-6b4269a7-46c9-4e07-8b88-f619373de0aa1492023335791
Size: 19 202 038 517 bytes (19,2 GB on disk)

I've reviewed released for 0.12.* and didn't spot info about possible fix.

Thanks!

@daviwil
Copy link
Contributor

daviwil commented Apr 13, 2017

Wow! How long has this session been running? Do you have Verbose logging turned on?

@daviwil daviwil added this to the April 2017 milestone Apr 13, 2017
@daviwil daviwil added Area-Logging Issue-Bug A bug to squash. labels Apr 13, 2017
@peterblazejewicz
Copy link
Author

I don't know. I'm using PowerShell on OS X from time-to-time (rather sporadic use to be honest). I do use VSCode all the time on OS X though. Won't be able to provide more info from this log as installing new version of extension clears that directory (I've just learned this after upgrading now to 0.12.*)

@daviwil daviwil modified the milestones: April 2017, May 2017 May 8, 2017
@daviwil daviwil modified the milestones: May 2017, June 2017 Jun 1, 2017
@daviwil daviwil modified the milestones: June 2017, July 2017 Jul 11, 2017
@daviwil daviwil modified the milestones: July 2017, Future Oct 26, 2017
@TylerLeonhardt TylerLeonhardt modified the milestone: Future May 24, 2018
@PrzemyslawKlys
Copy link
Contributor

@peterblazejewicz is this still the case with newest version? Can you check and close or update?

@ghost ghost added the Needs: Maintainer Attention Maintainer attention needed! label Apr 15, 2020
@peterblazejewicz
Copy link
Author

@PrzemyslawKlys let me check this out (still using VSCode Insider bits and regular one on Mac OS)

@TylerLeonhardt TylerLeonhardt removed the Needs: Maintainer Attention Maintainer attention needed! label Apr 15, 2020
@SydneyhSmith SydneyhSmith removed this from the Future milestone Jan 26, 2021
@yurim108
Copy link

yurim108 commented Sep 24, 2021

Same problem on Windows 10, VS Code Version 1.60.2.
EditorServices.log size is 30 Gb and still growing...
Is there any setting to limit the size? Can file be just deleted?

The file contained logs for the last 18 days (only 18 days and 30 Gb!).
I have deleted the file at around 10:40 to free some space, since my C:\ had 0 free bytes left.
Now is 12:35 and the file is already 205 Mb big inspite of 2 changed settings,
which I have found in VS Code and changed from "Normal" to "Error" to reduce amount of data being logged.
I have also restarted VS Code after changing those settings.
grafik

Some examples of the file content:

 al/setActiveWorkspace
09/24/2021 10:44:05 [/4] Processing al/setActiveWorkspace took 0 seconds
09/24/2021 10:44:05 [1/13] Parsing Page 50113 "Order Bundle".
09/24/2021 10:44:06 [1/13] Parsing Page 50113 "Order Bundle".
09/24/2021 10:44:07 [/9] Parsing Codeunit 50122 "CCO Blanket Sales Order Subf.".
09/24/2021 10:44:07 [/9] Parsing Codeunit 50110 "CCO Blkt. Sales Order to Order".
09/24/2021 10:44:07 [/9] Parsing Codeunit 50104 "CCO CalcProdOrderShortage".
09/24/2021 10:44:07 [/9] Parsing Codeunit 50109 "CCO Cancel Issued Reminder".
09/24/2021 10:44:07 [/9] Parsing Codeunit 50134 "CCO Contact Subscriber".
 textDocument/documentSymbol
09/24/2021 10:44:25 [2/33] Binding property 'Extensible = true;' declared on 'Enum "CCO Customer VAT Reg. No. State"'.
09/24/2021 10:44:25 [3/23] Binding property 'Extensible = true;' declared on 'Enum "CCO Communication Chanel"'.
09/24/2021 10:44:25 [6/20] Binding the members for Codeunit "CCO Blkt. Sales Order to Order".
09/24/2021 10:44:26 [58/36] Binding Statement: SetRange(Number, 1, LotNoInformationTmp.Count);.
09/24/2021 10:44:26 [56/35] Binding Statement: if TempItem.FindSet() then begin

            NextEntryNo := 1; // BOTTLING:PMW15.00:204:4

            repeat

                ItemLedgerEntry.Reset();

                ItemLedgerEntry.SetCurrentKey("Item No.", Open, "Variant Code", Positive, "Location Code",
                                              "Posting Date", "Expiration Date", "Lot No.", "Serial No.");
                ItemLedgerEntry.SetRange(Open, true);
                ItemLedgerEntry.SetRange(Positive, true);
                ItemLedgerEntry.SetFilter("Item No.", TempItem."No.");
                ItemLedgerEntry.SetFilter("Location Code", LocationFilter);
                ItemLedgerEntry.SetFilter("CCS PM Lot No. Trading Unit", LotFilter);

It seems that a lot of source code is being logged, however I have not worked on those objects today at all, but the objects are part of the project, where I have changed one page only.

Update: now is 16:45 and the file is 754 Mb big, after normal working on only 2 AL files in 2 different AL projects.

grafik

@ghost ghost added the Needs: Maintainer Attention Maintainer attention needed! label Sep 24, 2021
@andyleejordan
Copy link
Member

@yurim108 that is not the PowerShell extension. You're looking at logs for the extension AL Language (note the extension path, you're in the folder ms-dynamics-smb.al-<version>).

Since this bug as been waiting on reproduction for a year, and your issue is with another extension, I'm marking as resolved. Thanks!

@andyleejordan andyleejordan added Resolution-Fixed Will close automatically. and removed Needs: Maintainer Attention Maintainer attention needed! labels Sep 28, 2021
@ghost ghost closed this as completed Sep 28, 2021
@ghost
Copy link

ghost commented Sep 28, 2021

This issue has been marked as fixed. It has been automatically closed for housekeeping purposes.

@Grueslayer
Copy link

My log file is about 13 GB big 02.11.2021 12:26 13.606.411.956 EditorServices.log and still growing, first entry is from my first usage on 08/12/2020 11:45:05 [/1] Editor Services Host v5.0.4.50830 starting (pid 27964).

There should be a solution with max filesize or entry date to keep the logs in a normal range (I will not look into the log for a problem 1,5 year ago)

@ghost ghost added the Needs: Maintainer Attention Maintainer attention needed! label Nov 4, 2021
@ghost
Copy link

ghost commented Nov 4, 2021

Thank you for your comment, but please note that this issue has been closed for over a week. For better visibility, consider opening a new issue with a link to this instead.

@PrzemyslawKlys
Copy link
Contributor

@Grueslayer in which folder you have that file?

@Grueslayer
Copy link

Sorry.... I think this isn't caused by this extension, too. I'll have a deeper look into it.

@andyleejordan
Copy link
Member

I was going to say, I think it's coincidental that the file name is EditorServices.log (which we do use), since the header in the file is not something I believe we write:

Editor Services Host v5.0.4.50830 starting

Our editor services are at version 3.0 🙃

@PrzemyslawKlys
Copy link
Contributor

Also your extension when it gets updated deletes all logs. So the log can only get that big if no updates were done for either preview or production version for a very long time which is not possible with your current release times.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Logging Issue-Bug A bug to squash. Resolution-Fixed Will close automatically.
Projects
None yet
Development

No branches or pull requests

8 participants