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

Memory leak on Path with vector effect non-scaling-stroke #1436

Closed
Foggyhazel opened this issue Aug 12, 2020 · 2 comments
Closed

Memory leak on Path with vector effect non-scaling-stroke #1436

Foggyhazel opened this issue Aug 12, 2020 · 2 comments
Labels

Comments

@Foggyhazel
Copy link

Foggyhazel commented Aug 12, 2020

Bug

I'm making scatter plot with Path component set to render each dot with "M x y v0"

<Path d={d} strokeWidth={2} stroke="black" strokeLinecap="round" vectorEffect="nonScalingStroke"  />

When I transform this with parent G component, the memory usage in expo performance monitor keep rising.
There isn't an issue if the vector effect property is removed.

Environment info

React native info output:

System:
    OS: Linux 5.4 Ubuntu 20.04.1 LTS (Focal Fossa)
    CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
    Memory: 994.30 MB / 7.66 GB
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 12.16.3 - /tmp/yarn--1597218790434-0.5635823842019212/node
    Yarn: 1.22.4 - /tmp/yarn--1597218790434-0.5635823842019212/yarn
    npm: 6.14.4 - ~/.nvm/versions/node/v12.16.3/bin/npm
    Watchman: Not Found
  SDKs:
    Android SDK: Not Found
  IDEs:
    Android Studio: Not Found
  Languages:
    Java: Not Found
    Python: Not Found
  npmPackages:
    @react-native-community/cli: Not Found
    react: ~16.11.0 => 16.11.0 
    react-native: https://github.com/expo/react-native/archive/sdk-38.0.2.tar.gz => 0.62.2 
  npmGlobalPackages:
    *react-native*: Not Found

Library version: 12.1.0

Steps To Reproduce

  1. git clone https://github.com/Foggyhazel/test-path.git
  2. cd test-path
  3. yarn
  4. yarn start
  5. open the app in expo client (ios)
  6. press the Forward and Backward buttons repeatedly
  7. Observe ram usage in perf monitor
@stale
Copy link

stale bot commented Oct 15, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. You may also mark this issue as a "discussion" and I will leave this open.

@stale stale bot added the stale label Oct 15, 2020
@bohdanprog
Copy link
Member

Hello @Foggyhazel,
I attempted to replicate the issue without success.
If the problem persists, please feel free to open a new issue.
Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants