Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Android is slow/broken (Skipping frames)

See original GitHub issue

I have svg map with like ~100 elements and when clicking and updating only that one, app freeze and do not update element. Is there a way to optimize this?

This is the logs from my Galaxy S6 Edge

09-09 18:46:20.281 15172-15172/? I/art: Waiting for a blocking GC Alloc
09-09 18:46:20.281 15172-15172/? I/art: Starting a blocking GC Alloc
09-09 18:46:20.281 15172-15172/? I/art: Starting a blocking GC Alloc
09-09 18:46:20.291 15172-15172/? I/art: Alloc partial concurrent mark sweep GC freed 140(5KB) AllocSpace objects, 14(108MB) LOS objects, 9% free, 144MB/160MB, paused 385us total 10.488ms
09-09 18:46:20.301 15172-15172/? I/art: Waiting for a blocking GC Alloc
09-09 18:46:20.301 15172-15172/? I/art: Starting a blocking GC Alloc
09-09 18:46:20.301 15172-15172/? I/art: Starting a blocking GC Alloc
09-09 18:46:20.311 15172-15172/? I/art: Alloc partial concurrent mark sweep GC freed 149(6KB) AllocSpace objects, 16(124MB) LOS objects, 11% free, 128MB/144MB, paused 378us total 10.545ms
09-09 18:46:20.311 15172-15172/? I/art: Waiting for a blocking GC Alloc
09-09 18:46:20.321 15172-15172/? I/art: WaitForGcToComplete blocked for 10.156ms for cause Alloc
09-09 18:46:20.321 15172-15172/? I/art: Starting a blocking GC Alloc
09-09 18:46:20.331 15172-15172/? I/art: Waiting for a blocking GC Alloc
09-09 18:46:20.341 15172-15172/? I/art: WaitForGcToComplete blocked for 9.913ms for cause Alloc
09-09 18:46:20.341 15172-15172/? I/art: Starting a blocking GC Alloc
09-09 18:46:20.341 15172-15172/? I/art: Waiting for a blocking GC Alloc
09-09 18:46:20.351 15172-15172/? I/art: WaitForGcToComplete blocked for 9.940ms for cause Alloc
09-09 18:46:20.351 15172-15172/? I/art: Starting a blocking GC Alloc
09-09 18:46:20.361 15172-15172/? I/art: Waiting for a blocking GC Alloc
09-09 18:46:20.381 15172-15172/? I/art: WaitForGcToComplete blocked for 12.629ms for cause Alloc
09-09 18:46:20.381 15172-15172/? I/art: Starting a blocking GC Alloc
09-09 18:46:20.391 15172-15172/? I/art: Waiting for a blocking GC Alloc
09-09 18:46:20.401 15172-15172/? I/art: WaitForGcToComplete blocked for 8.350ms for cause Alloc
09-09 18:46:20.401 15172-15172/? I/art: Starting a blocking GC Alloc
09-09 18:46:20.601 15172-15172/? D/ViewRootImpl: ViewPostImeInputStage processPointer 1
09-09 18:46:20.601 15172-15172/? I/Choreographer: Skipped 98 frames!  The application may be doing too much work on its main thread.

didn’t test on iPhone but in simulator everything is fine.

Issue Analytics

State:
Created 7 years ago
Reactions:2
Comments:25 (3 by maintainers)

Top GitHub Comments

28reactions

davidbonnetcommented, Jul 26, 2017

The current version of react-native-svg is terribly slow on Android devices. We built an app with a single view containing an SVG with a path rendering a list of points generated from a finger stroke. On a Galaxy Tab Active and a Galaxy S4, the latency goes up to several seconds seconds and/or drops many touch locations.

On the other hand, this same app behaves smoothly on iOS devices, as old as an iPhone 5.

Are there any Android performance enhancements planned?

0reactions

msandcommented, Dec 9, 2018

If you’re still having performance issues, you should probably profile your code and find your bottlenecks and attempt to optimize those. There’s not much to be done here without specific problematic cases. Closing…