Closed Bug 988580 Opened 10 years ago Closed 10 years ago

Apps crash on Tarako when device resource demand is high

Categories

(Firefox OS Graveyard :: Performance, defect, P4)

x86_64
Windows 7
defect

Tracking

(blocking-b2g:-)

RESOLVED FIXED
2.0 S6 (18july)
blocking-b2g -

People

(Reporter: relaas, Assigned: Harald)

References

()

Details

(Keywords: perf, Whiteboard: [c= p= s=2014.07.18.t u=tarako] )

Example App 1: Aviary APP ID 477652

Steps to reproduce; Launch and use app. Experienced when cropping and applying filters.

Example App 2: Candy Crush APP ID 475777

Launch app. Candies don't move. Overall unresponsive.
Thomas, can you please specify what you mean by crash?  Do you have a crash id from the crash reporter?  Or was it OOM killed?

ie : 
please provide a logcat, and a listing from 
adb shell ls -l /data/b2g/mozilla/Crash\ Reports/submitted/ 

Also if you can provide a 
adb shell dmesg > dmesg.log

That would be wonderful.
Flags: needinfo?(telin)
Hi Naoki. I am in the process of updating the dependency tree for these 'Tarako trending issue' bugs. These were not filed to solve specific app issues but rather to identify issues that exist across multiple apps that have been tested on the Tarako device.

The cc'd audience are meant to discuss potential causes in these bugs and file separate and specific fixes with the relevant teams; platform, marketplace, developer, etc.

If you would like additional detail into the current Tarako testing process please see the URL attached to this bug.
Blocks: 989003
No longer blocks: 987944
Flags: needinfo?(telin)
Hi Thomas, understanding that these are not meant to solve specific app issues; having said if it truly is a crash, then that might be something we really need to investigate, esp if it happens in our gecko layer.

If it is an OOM issue then the information provided could help in regards to figuring out how to fine tune the gecko/gaia layer levels better for the phone.

The testing could also benefit engineering if we get more information.
batch update: 1.3T? so we can get more eyes into these marketplace related bugs
blocking-b2g: --- → 1.3T?
Thomas, this can be used as a meta bug, if you can file bug against specific app with crash logs, that will help the team better.
blocking-b2g: 1.3T? → -
Keywords: perf
Whiteboard: [c= p= s= u=tarako]
Priority: -- → P2
Setting these to P4 priority since they're not meant to be acted on but discussed. Our performance team is actively troubleshooting and fixing critical Tarako performance issues affecting core applications. You can see what we're working on via our scrum views at: https://scrumbu.gs/p/fxos-perf/
Status: NEW → ASSIGNED
Priority: P2 → P4
This is improved a lot and shouldn't be an issue anymore on latest builds with apps that Marketplace vetted to run on Tarako.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Whiteboard: [c= p= s= u=tarako] → [c= p= s=2014.07.18.t u=tarako]
Target Milestone: --- → 2.0 S6 (18july)
You need to log in before you can comment on or make changes to this bug.