SIGSEGV Segmentation violation (invalid memory reference) - libhermes

[noumantahir]

Apparently starting from our version release 3.0.28, I am seeing a lot of segmentation violation issues that would possibly a reason for the weird crash reported by Melinda....

possible direction to fix out of memory issue....
facebook/hermes#439 (comment)
facebook/hermes#439

Fix for this issue might be quite a challenge, we will have identify what change started using excessive heap and causing app to crash in production.

Bugsnag reference
https://app.bugsnag.com/ecency/ecency-mobile/errors/610852062040450007c48ea8?filters[event.since]=all&filters[error.status]=open

[noumantahir]

Personal Assessment:

In my testing current production android app on my mid level Redmi Note 10 device, I was not able to crash app after using is aggressively for roughly 10 minutes that include... my testing included opening as many posts, feed paginations, screen as much as possible notifications, wallet, profile, drafts, writing posts.

The issue I did face however was extremely extremely unexpected,

• After some minutes of usage, the api calls started taking too much time for loading any data both hive and ecency, though once I let certain api take some time to load, subsequent api calls started working as normal..
• After letting app sit idle with screen on for some more minutes, next api calls also started taking a lot of time to load data, this time it took like forever to load simple feed screen but subsequent network calls started working as normal and snappy as a fresh launch