Closed Bug 779853 Opened 12 years ago Closed 12 years ago

panda boards seem to have a 4 minute siesta while creating a new profile

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jmaher, Unassigned)

References

Details

(Whiteboard: u=panda c=ateam p=2)

While trying to get mochitests running on the panda board (android 4.0.4 + fennec 17), I found that after the initial launch, fennec would sit there with nothing in adb logcat until 4 minutes have gone by then:
08-02 11:30:31.468 E/GeckoLibLoad( 1941): Loaded libs in 864ms total, 335ms user, 132ms system, 2 faults
08-02 11:34:02.515 I/Process ( 1554): Sending signal. PID: 1554 SIG: 9
08-02 11:34:02.523 I/GeckoProfile( 1941): profile dir changed from /data/data/org.mozilla.fennec_jmaher/files/mozilla/3n2i4asf.default to /mnt/sdcard/tests/profile

This appears to be happening when there is no profile already (i.e. sql files and cache files).  If I have an existing installation and delete the profile directory, I run into the same problem.

This will really suck for ts startup times, as well as all our automation since we always run with a fresh install and a fresh profile.

On a subsequent launch of fennec, it takes 8 seconds to launch and get the page loaded which is very normal.
Blocks: 769428
They must be Iberian Pandas.
if I kill com.android.phone, this siesta is no more.  I see this in the logcat:
08-02 11:34:02.539 W/ActivityManager( 1414): Scheduling restart of crashed service com.android.phone/.BluetoothHeadsetService in 1250ms

Does fennec share a resource or reference phone or bluetooth networking?
I don't believe so. I also looked at the BluetoothHeadsetService code in the android repo and I didn't see anything obvious that might cause this interaction.
Whiteboard: u=panda c=ateam p=2
ok, adjusting the resolution in bootargs resolved this.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.