Skip to content

Wrong reference count for nested functions #2646

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
kborowinski opened this issue Apr 20, 2020 · 5 comments
Closed

Wrong reference count for nested functions #2646

kborowinski opened this issue Apr 20, 2020 · 5 comments
Assignees
Labels
Area-Symbols & References Issue-Bug A bug to squash. Resolution-Fixed Will close automatically.

Comments

@kborowinski
Copy link

kborowinski commented Apr 20, 2020

System Details

System Details Output

### VSCode version: 1.45.0-insider ec0d19789f89d4c25895f4a0cf364276cfb0c6ed x64

### VSCode extensions:
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]


### PSES version: 2.2.0.0

### PowerShell version:

Name                           Value
----                           -----
PSVersion                      5.1.18362.752
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.18362.752
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Issue Description

Wrong reference count (double the actual number) for nested functions:

nesting_1

nesting_2

nesting_3

Expected Behaviour

The code lens should show the correct reference count

Attached Logs

Follow the instructions in the troubleshooting docs
about capturing and sending logs.

logs.zip

@ghost ghost added the Needs: Triage Maintainer attention needed! label Apr 20, 2020
@SydneyhSmith
Copy link
Collaborator

Thanks @kborowinski does this look like a duplicate of #1465 to you?

@SydneyhSmith SydneyhSmith added Needs-Repro-Info and removed Needs: Triage Maintainer attention needed! labels Apr 21, 2020
@kborowinski
Copy link
Author

@SydneyhSmith They may look similar but I don't think that this issue is a duplicate.

@ghost ghost added the Needs: Maintainer Attention Maintainer attention needed! label Apr 21, 2020
@andyleejordan
Copy link
Member

Hey @kborowinski can you confirm if this is fixed in the latest preview?

@andyleejordan andyleejordan self-assigned this Feb 7, 2023
@andyleejordan andyleejordan added the Needs: Fix Verification Please verify the fix for us! label Feb 7, 2023
@kborowinski
Copy link
Author

@andschwa Yep, it works as expected! Thanks!

@andyleejordan andyleejordan added Resolution-Fixed Will close automatically. and removed Needs: Fix Verification Please verify the fix for us! labels Feb 7, 2023
@ghost ghost closed this as completed Feb 8, 2023
@ghost
Copy link

ghost commented Feb 8, 2023

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

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

No branches or pull requests

3 participants