WAT, com.amazon.webapps.performancetester killed by low memory killer on HD 8 Plus, not on HD 10

Question

question

ghumiston asked · Feb 17 at 03:07 PM

WAT, com.amazon.webapps.performancetester killed by low memory killer on HD 8 Plus, not on HD 10

I'm currently trying to smoke-test a web application through the Amazon Web App Tester (https://www.amazon.com/Amazon-Digital-Services-Inc-Tester/dp/B00DZ3I1W8) before submitting for review and after testing the application on the HD 8 Plus, the application is killed and I'm returned to the Web app Tester. Testing the same portion of the application with an HD 10 never results in a crash.

Upon checking the HD 8 Plus crash logs, I see the following:

hasForegroundActivities: true
Process: com.amazon.webapps.performancetester
Version: 314
Total memory of com.amazon.webapps.performancetester: 2148 MB (ResidentSize (includes GPU): 2199996 KB, IonAllocations: 0 KB, GpuMemory: 0 KB)
TraceHashCode: LMK_com.amazon.webapps.performancetester_2200
Build: Amazon/onyx/onyx:7.0/PS7317/1810N:user/amz-p,release-keys
OsBuildNumber: PS7317_user_1810
OsOtaNumber: 0019227153028

======low memory killer=====
Free memory other_free: 2981, other_file:17843 pages
Candidate 564 (system_server), adj -900, rss 12481, to kill
Candidate 1860 (com.android.se), adj -800, rss 1789, to kill
Candidate 1830 (com.dolby.daxservice), adj -800, rss 2086, to kill
Candidate 1843 (com.amazon.tcomm), adj -800, rss 2334, to kill
Candidate 1818 (amazon.speech.sim), adj -800, rss 1677, to kill
Candidate 1448 (com.amazon.imp), adj -800, rss 4882, to kill
Candidate 1347 (com.android.systemui), adj -800, rss 9679, to kill
Candidate 20799 (com.amazon.webview.chromium:sandboxed_process0), adj 0, rss 23558, to kill
Killing 'com.amazon.webview.chromium:sandboxed_process0' (20799), uid 99022, adj 0
   to free 94232kB because system is under low memory pressure oom_adj 0
previous crash:
Killing 'com.amazon.webapps.performancetester' (20692), uid 10173, adj 0
   to free 2199996kB because system is under medium memory pressure oom_adj 0

Reviewing the crash log shows that the 'com.amazon.webapps.performancetester' process was killed to free up memory. Upon testing my web app through the Silk browser on the HD 8 Plus, I was unable to recreate this crash using the same portion of the web application.

I also noticed that the WAT version on the HD 8 Plus is 3.14 while the HD 10 is 3.0.200129.0_3021110. Although I'm still unsure of whether this matters or note, it was something I noticed that could explain why HD 8 plus is crashing while the HD 10 isn't.

Given that Silk is not giving me low memory issues on the HD 8 plus, I was wondering

if WAT version, or Chrome Webview, were potentially contributing to the low memory issue
If there is a specific place in the Kindle logs that would/could point to what is causing low memory to occur
why the performancetester is consuming too much memory on a 3 gb RAM device (HD 8 Plus) and not on a 2 gb RAM device (HD 10)

fire tablet debugging testing memory

1

10 |2000 characters needed characters left characters exceeded

Attachments: Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

Answer 1 · 2021-02-17T19:46:11Z

Jacek answered · Feb 17 at 07:46 PM

There is one more moving part - WAT generates Cordova built apk. So, comparing Silk to WAT doesn't really make sense (no apk needed for Silk).

If you search this forum (or potentially Appstore forum), when HD 8 2020 was introduced last Oct or so, more or less all web-apps were being rejected for crashing on that device. As those apps were running the same code on HD 10 2019 and HD 8 2020 (what you also see), the assumption was that the apk produced by Amazon was bad. (Amazon is still using Cordova v3 or so.)

Since those crashes were intermittent, Amazon submission team started re-approving those web-apps (in my opinion, without any more testing - if it starts, that's fine, if it doesn't, too bad - type of approach).

If you submit your app right now, it can either pass or fail, and if it fails and you complain about it, it may be approved (but will fail in the field). That submission team doesn't understand that the apk is built by Amazon, and instead of asking the Cordova team to investigate, an easier way for them is to push back on you submission.

The devs consensus was that the Cordova wrapping is not done right, but I don't think that has been addressed or even acknowledge by Amazon.

Potentially, you are getting closer to pinpoint the issue, but it may be that there is no more Cordova team, so the problem will just get worst when new devices will kick in this year.

The best you can do is to submit your app as is now, and hope for the best with that. At the same time keep pushing this thread, as you may be on something with that Cordova build.

Thank you, Jacek

1 · Show 10 · Share

10 |2000 characters needed characters left characters exceeded

Attachments: Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

ghumiston · Feb 17 at 09:52 PM

Thank you for mentioning Cordova is an additional piece as I overlooked that entirely! I used Silk as a sanity check against my web application potentially causing the memory leak vs. WAT itself but this makes a bit more sense.

I'll go ahead and search for the HD 8 2020 to see if what was reported is similar to what I'm seeing but I unfortunately (or fortunately?) don't feel comfortable submitting a web app blindly so I'll avoid going that route.

Just for clarification on my end (and please excuse my ignorance): when you say "Cordova team", is that a team internal to Amazon?

1 · Share ·

Jacek ghumiston · Feb 18 at 01:51 AM

No worries, we are all here to learn from each other, and the info you provided is really good!

One more thing about your WAT testing. Although, WAT runs Cordova to build an apk, that is not the same apk as one built for production. Also, low memory issue may be due to the apk and WAT running at the same time.

Yeah, Silk looks like a sanity check, but knowing the chromium version (when you test in a browser) is the key.

The next thing is that both HD 8 2020 and HD 10 2019 are running FOS 7. And here is the bummer, as those are not really the same versions/builds; therefore the problem you see (works on one, but not the other). Apparently, the FOS on HD 8 2020 is less forgiving to how Cordova v3 builds an apk (comparing to HD 10 2019).

As far as Cordova, yes I had in mind the Amazon Cordova wrapping team. My take is that all those engineers left, and Amazon neither has the budget nor the expertise to address those issues. It looks like Amazon decided to support Prime Videos, Netflix, Hulu, and the other big guys, and abandon little guys like you and me (we are those pushing for web-apps, not the big guys).

0 · Share ·

Jacek Jacek · Feb 18 at 04:13 AM

As far as publishing your app, there are few more challenges in front of you. I do understand that you don't want to publish for HD 8 2018, but don't get your hopes up that this problem will be fixed any time soon (if at all). It looks like it this problem was first reported around the last September or October, and there is not even an acknowledgement from Amazon that they are considering looking into it, or seeing it as an issue (but we didn't have the info you provided). There are few other rather significant issues that are also not yet/anymore addressed.

With that in mind, submit for those devices that you feel are working for you (e.g., HD 10 2019), while you will continue working on those that give you trouble. Once you get your app approved for one device, it will be rather easy to add more devices, as the very first submission may also be a challenge.

Thank you, Jacek

(it didn't let me post it in one chunk)

0 · Share ·

Show more comments

WAT, com.amazon.webapps.performancetester killed by low memory killer on HD 8 Plus, not on HD 10

question details

Related Questions