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

FlutterEventTracer is leaked per shell run. #30808

Closed
chinmaygarde opened this issue Apr 9, 2019 · 4 comments
Closed

FlutterEventTracer is leaked per shell run. #30808

chinmaygarde opened this issue Apr 9, 2019 · 4 comments
Labels
engine flutter/engine repository. See also e: labels. P2 Important issues not at the top of the work list

Comments

@chinmaygarde
Copy link
Member

In |InitSkiaEventTracer|.

@chinmaygarde chinmaygarde added the engine flutter/engine repository. See also e: labels. label Apr 9, 2019
@pedromassangocode
Copy link

Can you please provide more information about this issue?
I'm not able to verify if this is still valid or not. Thanks

@chinmaygarde
Copy link
Member Author

Yes, the handle given to the _flutter.enableSkiaTracing callback is a small leak and must be cleaned up when the shell instance is torn down.

@chinmaygarde chinmaygarde added the P2 Important issues not at the top of the work list label Dec 2, 2020
@jason-simmons
Copy link
Member

This callback was removed in flutter/engine@0fc1bea

@github-actions
Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 31, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
engine flutter/engine repository. See also e: labels. P2 Important issues not at the top of the work list
Projects
None yet
Development

No branches or pull requests

3 participants