1020515 - Flame devices are using 60% CPU and not producing logcat on latest master

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: General, defect)

Description

[Kartikaya Gupta (email:[e-mail])]

Have a bunch of people here running Flame builds built from m-c code over the last day (at some point after June 2) and the devices seem to be very laggy. "top" shows much CPU hogging, and after a while logcat seems to not work any more. I haven't reproduced this myself so I don't have much detail but at least two people have run into this.

Comment 1

[Mike Habicher [:mikeh] (high bugzilla latency)]

We've seen this in the bootcamp workshop, running m-c pulled about an hour ago.

When we do manage to connect to logcat (usually by trying to early in the boot process) the output is spammed with RIL "connect failed with error 2" and related messages.

Comment 2

[Kartikaya Gupta (email:[e-mail])]

The logcat spam is bug 1010993, but that shouldn't cause the logcat to die like it does here.

Comment 3

[Jason Smith [:jsmith]]

kats - what base image are you using for Flame?

Comment 4

[Kartikaya Gupta (email:[e-mail])]

mconley, do you know? (i have an older build on my device so i wasn't seeing the problem myself)

Comment 5

[Mike Conley (:mconley) (:⚙️)]

Not sure how to answer that question - total b2g noob here.

What I _do_ know, is that mikeh updated the firmware on the device, and that seemed to solve the problem using the same Gecko.

Comment 6

[Mike Habicher [:mikeh] (high bugzilla latency)]

I updated mconley's Flame to v10G-2, and happiness was attained.

Comment 7

[Mason Chang [Inactive] [:mchang]]

Attachment: Build.prop for bug

Just in case anyone needs it.