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
fix(ios): remove busy loop and change waitForMemoryPanicCleared to noop since it's always on main thread #10893
Conversation
…op since it's always on main thread Was previously used in kroll thread entry points to wait for main thread to handle memory warnings. Now it will just result in an infinite sleep loop because JS runs on main thread. Fixes TIMOB-27080
Instead of making it a noop, can't we just remove the method completely? I don't think it's party of any public API so it shouldn't be an issue to remove it now. |
Tests:
|
Still dead-locking / crashing, but now with many more logs:
Triggered manually via EDIT: Discard my comment, I patched an outdated fork of the SDK with this pull. After rebasing from master + applying our 2-3 blocker pulls that we require immediately, this pull works as well! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved! As discussed in Teams we'll keep the function and extern var for now to avoid possible breaking changes.
Still see the issue with the SDK build fetched from Jenkins for this PR. It consistently crashes when scrolling through the trips (had around 15 trips created and it crashes after scrolling through 8-10 trips). Following logs were shown in console during one of the crash Env: |
* Update SystemButton.yml Added system icons image. https://jira.appcelerator.org/browse/TIDOC-2851 * Create system_icons.png
Also add core-js@2 to our devDependencies so that we dont get burnt if core-js@3 starts being in the top level of the project node_modules
Any update on the merge here? This is a critical pull request for many production apps. I hope postponing it to 8.2.0 was a mistake. |
@hansemannn It's an artifact of our branching off 8_1_X. We expect this fix to be in 8.0.2, master and 8_1_X. |
Couldn't check the master build on the lambus app as there are some errors reported in the app upon launch when using the recent builds. |
merged manually |
JIRA: https://jira.appcelerator.org/browse/TIMOB-27080
Description:
Was previously used in kroll thread entry points to wait for main thread to handle memory warnings.
Now it will just result in an infinite sleep loop because JS runs on main thread.
All credit goes to @janvennemann for finding this, once he pointed it out to me I was able to do a local SDK build with it as a no-op and confirm the fix on @hansemannn 's Lambus app.