Closed Bug 1079313 Opened 11 years ago Closed 11 years ago

Opening the call log crashes the dialer app

Categories

(Firefox OS Graveyard :: Gaia::Dialer, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: past, Unassigned)

References

Details

Flame on v184 with shallow flashed gecko & gaia on top. Opening the dialer app works fine and logs these in logcat: E/QCALOG ( 306): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] D/wpa_supplicant( 1820): RX ctrl_iface - hexdump(len=11): 53 49 47 4e 41 4c 5f 50 4f 4c 4c D/wpa_supplicant( 1820): wlan0: Control interface command 'SIGNAL_POLL' D/wpa_supplicant( 1820): nl80211: survey data missing! W/AudioFlinger( 204): Thread AudioOut_2 cannot connect to the power manager service E/AudioFlinger( 204): no wake lock to update! E/QCALOG ( 306): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] E/QCALOG ( 306): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] However, once I click on the call log icon the app crashes and I see this in the log: I/Gecko ( 208): I/Gecko ( 208): ###!!! [Parent][DispatchAsyncMessage] Error: (msgtype=0x120005,name=PBackground::Msg_PBlobConstructor) Value error: message was deserialized, but contained an illegal value I/Gecko ( 208): I/Gecko ( 208): IPDL protocol error: could not look up PBlob I/Gecko ( 208): IPDL protocol error: Error deserializing 'PBlobParent' I/Gecko ( 208): I/Gecko ( 208): ###!!! [Parent][DispatchAsyncMessage] Error: (msgtype=0x60004,name=PBackgroundIDBDatabase::Msg_PBackgroundIDBDatabaseFileConstructor) Value error: message was deserialized, but contained an illegal value I/Gecko ( 208): I/Gecko ( 208): I/Gecko ( 208): ###!!! [Parent][MessageChannel] Error: Channel error: cannot send/recv I/Gecko ( 208): W/GeckoConsole( 208): [JavaScript Error: "IndexedDB UnknownErr: ActorsParent.cpp:7692"] W/GeckoConsole( 208): [JavaScript Error: "IndexedDB UnknownErr: ActorsParent.cpp:6065"] W/AudioFlinger( 204): Thread AudioOut_2 cannot connect to the power manager service E/AudioFlinger( 204): no wake lock to update! E/QCALOG ( 306): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] D/wpa_supplicant( 1820): RX ctrl_iface - hexdump(len=11): 53 49 47 4e 41 4c 5f 50 4f 4c 4c D/wpa_supplicant( 1820): wlan0: Control interface command 'SIGNAL_POLL' D/wpa_supplicant( 1820): nl80211: survey data missing! I/Gecko ( 4169): ###################################### forms.js loaded I/Gecko ( 4169): ############################### browserElementPanning.js loaded I/Gecko ( 4169): ######################## BrowserElementChildPreload.js loaded E/QCALOG ( 306): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] E/QCALOG ( 306): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] It's likely that this hasn't worked ever since I got my flame and flashed v184 on it a couple of days ago, but I don't know for sure.
I don't see the issue on today's 2.1 under the v184 base image. Gaia-Rev 7f738edf66b9298bceef8a4981d05d04fd04e540 Gecko-Rev https://hg.mozilla.org/releases/mozilla-aurora/rev/b9d04c58580a Build-ID 20141007000203 Version 34.0a2 Device-Name flame-kk FW-Release 4.4.2 FW-Incremental 34 FW-Date Tue Sep 30 14:06:36 CST 2014 Bootloader L1TC00011840 I also don't see it on the latest master build.: Gaia-Rev 83de447d9ae9a59459d7a445f9348a254c661850 Gecko-Rev https://hg.mozilla.org/mozilla-central/rev/9ee9e193fc48 Build-ID 20141007040205 Version 35.0a1 Device-Name flame-kk FW-Release 4.4.2 FW-Incremental 34 FW-Date Tue Sep 30 14:06:36 CST 2014 Bootloader L1TC00011840 Which gecko and gaia are you running?
Flags: needinfo?(past)
gecko$ git show commit 745dcf1bff1d2b2306dd241c5a3513731e8c23b1 Merge: 03d235f 6626c53 Author: Wes Kocher <wkocher@mozilla.com> Date: Mon Oct 6 19:29:41 2014 -0700 Merge fx-team to m-c a=merge CLOSED TREE gecko$ cd ../gaia gaia$ git show commit 7d54bbbea42343fc30649fd275c08ae247eec1b3 Merge: 9306e43 f78672c Author: Anthony Ricaud <anthony@ricaud.me> Date: Tue Oct 7 12:43:06 2014 +0200 Merge pull request #24477 from Rik/keypad-vibrate-1069286 Bug 1069286 - No tactile feedback when dialling a number r=drs, r=gweng
Flags: needinfo?(past)
Similar error than bug 1078438. I guess those highly depends on the data.
Since I'm flashing my own builds it wouldn't be too hard for me to instrument them to log more information that exposes the unexpected data format, if one were to tell me what such instrumentation would look like.
Can you please test again now that bug 1079546 has landed?
I have been using full flash lately, which didn't like it when I used to restore my profile backup, so I've lost that data. It's been a while since I've got a crash in the call log screen, but I don't know whether that's because I don't have a lot of (bad?) entries in it or whether it's fixed.
Let's resolve for now. Please reopen if you see this again.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.