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

Result of getRetainingPath should not be about the getRetainingPath invocation. #52517

Closed
polina-c opened this issue May 25, 2023 · 2 comments
Closed
Labels
area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. vm-service The VM Service Protocol, both the specification and its implementation

Comments

@polina-c
Copy link
Contributor

polina-c commented May 25, 2023

Open leak_tracker at a14a2ec06a1b7e8f591fd9adbfd4295b903e4288 in VSCode.
Navigate to test/dart_debug/leak_tracking/end_to_ent_test.dart
Click 'debug' for the test 'Retaining path for not GCed object is reported.'

See in debug console the retaining path is about the vm call, not path in the test library, that user wants to discover:

dart.core/_Type
package:vm_service/src/vm_service.dart/VmService:_outstandingRequests@72266273
dart.collection/_Map:[InstanceRef id: objects/1045, kind: String, identityHashCode: 0, classRef: [ClassRef id: classes/93, name: _OneByteString, library: [LibraryRef id: libraries/@0150898, name: dart.core, uri: dart:core]]]
package:vm_service/src/vm_service.dart/_OutstandingRequest:_completer@72266273
dart.async/_AsyncCompleter:future
dart.async/_Future:_resultOrListeners@4048458
dart.async/_FutureListener:errorCallback
dart.core/_Closure:_context@0150898
@Context:1
dart.core/_Closure:_context@0150898
@Context:0
dart.async/_SuspendState:function_data_
dart.async/_Future:_resultOrListeners@4048458
dart.async/_FutureListener:errorCallback
dart.core/_Closure:_context@0150898
@Context:1
dart.core/_Closure:_context@0150898
@Context:0
dart.async/_SuspendState:function_data_
dart.async/_Future:_resultOrListeners@4048458
dart.async/_FutureListener:errorCallback
dart.core/_Closure:_context@0150898
@Context:1
dart.core/_Closure:_context@0150898
@Context:0
dart.async/_SuspendState:function_data_
dart.async/_Future:_resultOrListeners@4048458
dart.async/_FutureListener:errorCallback
dart.core/_Closure:_context@0150898
@Context:1
dart.core/_Closure:_context@0150898
@Context:2
dart.async/_Future:_resultOrListeners@4048458
dart.async/_FutureListener:errorCallback
dart.core/_Closure:_context@0150898
@Context:1
dart.core/_Closure:_context@0150898
@Context:0
dart.async/_SuspendState:function_data_
dart.async/_Future:_resultOrListeners@4048458
dart.async/_FutureListener:errorCallback
dart.core/_Closure:_context@0150898
@Context:1
dart.core/_Closure:_context@0150898
@Context:0
dart.async/_SuspendState:function_data_
dart.async/_Future:_resultOrListeners@4048458
dart.async/_FutureListener:errorCallback
dart.core/_Closure:_context@0150898
@Context:1
dart.core/_Closure:_context@0150898
@Context:0
dart.async/_SuspendState:function_data_
dart.async/_Future:_resultOrListeners@4048458
dart.async/_FutureListener:errorCallback
dart.core/_Closure:_context@0150898
@Context:1
dart.core/_Closure:_context@0150898
@Context:0
dart.async/_SuspendState:function_data_
dart.async/_Future:_resultOrListeners@4048458
dart.async/_FutureListener:errorCallback
dart.core/_Closure:_context@0150898
@Context:1
dart.core/_Closure:_context@0150898
@Context:0
dart.async/_SuspendState:function_data_
dart.async/_Future:_resultOrListeners@4048458
dart.async/_FutureListener:errorCallback
dart.core/_Closure:_context@0150898
@Context:1
dart.core/_Closure:_context@0150898
@Context:0
dart.async/_SuspendState
dart.core/_Closure:_context@0150898
@Context:0
file:///Users/polinach/_/leak_tracker/test/dart_test_infra/data/dart_classes.dart/LeakTrackedClass
@polina-c polina-c added area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. vm-service The VM Service Protocol, both the specification and its implementation labels May 25, 2023
@a-siva
Copy link
Contributor

a-siva commented May 25, 2023

//cc @rmacnak-google

@polina-c
Copy link
Contributor Author

It turned out to be result of two contexts living in the same function. After I moved leaking object from the test to a dedicated class, the issue disappeared.
Closing it for now, as we do not know what to do about it. If we will face the issue in other context, I will reopen the bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. vm-service The VM Service Protocol, both the specification and its implementation
Projects
None yet
Development

No branches or pull requests

2 participants