725043 - GeckoLinker or gralloc crash: libnssckbi.so: Warning: dynamic header type #6ffffffa not handled

Status: RESOLVED DUPLICATE of bug 718703

(Firefox for Android Graveyard :: General, defect)

Description

[JR Conlin [:jrconlin,:jconlin]]

Steps to reproduce:

start aurora
* Go to "Settings"
 * Sync
  * Firefox Sync 
    [Pair a Device]
      As Bob used to say: * Reboot! *

(Moto Razr running 2.3.5)

Comment 1

[JR Conlin [:jrconlin,:jconlin]]

Attachment: razr log

second try because ddms silently failed to write the log.

Comment 2

[Richard Newman [:rnewman]]

Thanks for filing, JR.

The crash here is in Fennec, even though you've launched Settings. There's nothing at all about Sync in the log.


10.577 27385 27394 E GeckoLinker: /data/app/org.mozilla.fennec_aurora-1.apk!/libnssckbi.so: Warning: dynamic header type #6ffffffa not handled
10.632 25592 25872 I gralloc : Allocated 0x31 size -1345030876
10.827 25592 25629 I ActivityManager: Displayed org.mozilla.fennec_aurora/org.mozilla.gecko.GeckoPreferences: +409ms
10.835 27385 27385 I GeckoApp: stop
23.968 25592 25610 W dalvikvm: threadid=10: thread exiting with uncaught exception (group=0x4001e560)
23.999 25592 25610 I Process : Sending signal. PID: 25592 SIG: 9


Does it crash if you just open Settings in Aurora, without clicking Sync?

Does it crash if you tap Sync (and thus get thrown over to Settings), but don't do anything?

Comment 3

[JR Conlin [:jrconlin,:jconlin]]

No, opening settings works fine. 

I have attempt to pair the device to cause the reboot.
Clicking on "Pair a Device" causes the display to freeze for about a second, and the device to immediately reboot. I am able to reproduce this and have posted a video of the sequence at http://jrconlin.com/img/reboot.avi

Comment 4

[Richard Newman [:rnewman]]

Ah, looks like Bug 718703. This landed in Aurora on Sunday, and so it should be in an 02-06 or 02-07 Aurora build.

Could you verify that you're not running an older version?

(about: in Fennec should do the trick, or just check for updates.)

Comment 5

[JR Conlin [:jrconlin,:jconlin]]

Odd, checking updates showed none available this afternoon, and the crashing version was 01-31. No idea why it wasn't pulling updates, since I check daily.

Pulling latest version now.

Comment 6

[JR Conlin [:jrconlin,:jconlin]]

Sure enough, latest version solved the problem.

Comment 7

[Richard Newman [:rnewman]]

Thanks JR!