App freezes after a while with OOM on low-power Android smartphone
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- android, javascript
- Domain
- mobile, performance
Research direction
The report describes an out-of-memory freeze on a Nokia 2 running Android 8.1 with Chrome 80, but does not identify a file, failing test, or specific source of the memory growth. Start by reproducing the scan on that device and tracing memory use in the QR scanning path, including the software fallback and ShapeDetection API. Done means the app no longer freezes from memory pressure while retaining a working fallback; the issue gives no test or benchmark to confirm this.
Written by the indexing model from the issue text.
Description
Using the Nokia 2 on Android 8.1 with Chrome 80, the app freezes after a while with
'This page uses soo much memory, so Chrome removed some content'.
This combination of hardware, platform and browser version has been verified to support ShapeDetection API.
Note that Google distributed this phone model to developers at some point with the indication it would be a prototypical example of low-power smartphone often found in developing countries.
So for QR snapper to be useful to the next billion users, the app and/or Google Chrome needs some serious performance work.
Note that merely switching exclusively to the browser's ShapeDetection API will not work in general, since on too many devices this may not work (needs cooperation with Google Play Services, has been observed to fail in the field even with up-to-date Services). Hence an unaccelerated software fallback like what is used in QR snapper is still needed, greatly reducing the benefit of ShapeDetection API .
Please fix this.
- Dominant language
- JavaScript
- Stars
- 375
- Forks
- 479
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PaulKinlan/qrcode
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
PaulKinlan/qrcode#67 ·
-
bug on ios 12.2 only selfie caméraPossibly taken @Yuren0312 claimed this 1 day ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 15/100
PaulKinlan/qrcode#58 · 3 comments · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
PaulKinlan/qrcode#51 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
PaulKinlan/qrcode#50 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
PaulKinlan/qrcode#48 · 1 comment ·
All issues in PaulKinlan/qrcode
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
feature request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
openlayers/openlayers#17736 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
521xueweihan/HelloGitHub#4326 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Mintplex-Labs/anything-llm#7133 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day