User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1985.143 Safari/537.36 Steps to reproduce: Geolocation actually works just if turned "on" in Settings app. After turned "on", opening any app (also system app, Camera, HERE Maps, etc.) or website that runs Geolocation, after about 2 seconds Firefox OS crashes instantly. Bug noticed on Geeksphone Peak, on latest Firefox OS 1.4 images since before about a week. Actual results: Firefox OS crash. Expected results: No crash.

Can confirm this on Flame running nightly. Unfortunately, phone lagged and rebooted just a few seconds after unlocking it (right after I've noticed geolocation icon). I had to pull our my sim cards so I didn't have to enter pin and could shutdown geolocation before it started. After update my sim cards are undetected, which I have once noticed on fxos 1.4. I tried to reflash nightly, no luck.

Sorry, scratch that, sim is fine. Geolocation problem persists.

Would it be possible for you to get the crash id for us please? https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks#command_line_to_get_the_crash_ids

Unfortunately, I didn't have the crash report anymore. However, it was easy to reproduce the crash even with the latest nightly update. Steps I've taken: 1) Fired up geolocation. 2) Checked, whether Privacy Panel is still set up to show fake location (it is, Copenhagen). 3) Allowed browser to use geolocation. 4) Opened Facebook, pressed "Check in" (basic geolocation) 5) Phone became unresponsive and rebooted 5s after. The crash report was not saved. There is a record under Crash Reports/pending http://pastebin.com/raw.php?i=3wqkKfbV I have downloaded the dump file as well in case you will need it.

Same here with flame 2.2. It must be something with user data or settings, because it does not happen with a fresh flash of base image v188. in logcat, I have : E/QCALOG ( 313): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent] E/HWComposer( 4482): Non-uniform vsync interval: 1417692760 I/GeckoDump( 4482): XXX FIXME : Got a mozContentEvent: permission-allow E/HWComposer( 4482): Non-uniform vsync interval: 17286146 E/QCALOG ( 313): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent] E/QCALOG ( 313): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent] E/HWComposer( 4482): Non-uniform vsync interval: 617100469 I/ServiceManager( 192): service 'android.security.keystore' died I/ServiceManager( 192): service 'media.resource_manager' died I/ServiceManager( 192): service 'SurfaceFlinger' died I/ServiceManager( 192): service 'permission' died I/ServiceManager( 192): service 'display.qservice' died D/nfcd ( 209): 576 of bytes to be sent... data=0x0 ret=0 I/Gecko ( 5148): [Child 5148] WARNING: pipe error (12): Connection reset by peer: file ../../../gecko/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 456 I/Gecko ( 5148): I/Gecko ( 5148): ###!!! [Child][MessageChannel::SendAndWait] Error: Channel error: cannot send/recv I/Gecko ( 5148): I/ServiceManager( 192): service 'media.audio_flinger' died I/ServiceManager( 192): service 'media.player' died I/ServiceManager( 192): service 'media.camera' died I/ServiceManager( 192): service 'media.audio_policy' died W/linker ( 5218): libsrsprocessing.so has text relocations. This is wasting memory and is a security risk. Please fix. D/SRS_Spools_V2( 5218): DSEC_DMO_Token ERR: Unable to open key file. - /system/etc/srs/srsmodels.lic D/SRS_Spools_V2( 5218): DSEC_RET_Token ERR: Unable to open key file. - /system/etc/srs/srsmodels.lic W/SRS_QDSP_Adapter( 5218): Not creating SRS DSP thread. I/mediaserver( 5218): ServiceManager: 0xb8771008 I/AudioFlinger( 5218): Using default 3000 mSec as standby time. E/MediaPlayerFactory( 5218): calling dlopen on FACTORY_LIB E/MediaPlayerFactory( 5218): calling dlsym on pFactoryLib for FACTORY_CREATE_FN E/MediaPlayerFactory( 5218): registering DASH Player factory... I/CameraService( 5218): CameraService started (pid=5218) D/mm-camera-intf( 5218): index = 0 flag = 3 mount_angle = 270 facing = 0 D/mm-camera-intf( 5218): index = 1 flag = 103 mount_angle = 270 facing = 1 I/CameraService( 5218): Loaded "QCamera Module" camera module I/AudioPolicyManagerBase( 5218): loadAudioPolicyConfig() loaded /system/etc/audio_policy.conf D/audio_hw_primary( 5218): adev_open: enter E/audio_route( 5218): Control 'RX2 MIX2 INP2' doesn't exist - skipping E/audio_route( 5218): Control 'RX1 MIX2 INP2' doesn't exist - skipping E/audio_route( 5218): Control 'MI2S_DL_HL Switch' doesn't exist - skipping E/audio_route( 5218): Control 'MI2S_DL_HL Switch' doesn't exist - skipping D/msm8974_platform( 5218): platform_init: Opened sound card:0 D/ACDB-LOADER( 5218): ACDB -> Load file: /etc/acdbdata/QRD/QRD_Bluetooth_cal.acdb D/ACDB-LOADER( 5218): ACDB -> Load file: /etc/acdbdata/QRD/QRD_General_cal.acdb D/ACDB-LOADER( 5218): ACDB -> Load file: /etc/acdbdata/QRD/QRD_Global_cal.acdb D/ACDB-LOADER( 5218): ACDB -> Load file: /etc/acdbdata/QRD/QRD_Handset_cal.acdb D/ACDB-LOADER( 5218): ACDB -> Load file: /etc/acdbdata/QRD/QRD_Hdmi_cal.acdb D/ACDB-LOADER( 5218): ACDB -> Load file: /etc/acdbdata/QRD/QRD_Headset_cal.acdb D/ACDB-LOADER( 5218): ACDB -> Load file: /etc/acdbdata/QRD/QRD_Speaker_cal.acdb D/ACDB-LOADER( 5218): ACDB -> ACDB_CMD_INITIALIZE_V2 D/ACDB-LOADER( 5218): ACDB -> ACPH INIT All the "service died" stuff happen at the same time the UI becomes unresponsive.

Crash reports submitted : bp-10cf40d6-8664-44dc-aa47-806d12150218.txt bp-1d6c013d-4327-4478-87d2-427f42150218.txt bp-2dde707f-c182-42c6-8377-fd1ef2150218.txt bp-3308ed20-acbc-4d3f-9e82-37d702150218.txt bp-9f09af95-651e-4d81-8479-2cdbc2150218.txt bp-cc0de4ec-00e2-45c1-9087-e84af2150218.txt bp-f2f9e373-8fee-41ca-9afd-1fc792150218.txt all at the same time.

Removing the [Peak] as it happens on flame as well.

Well, after today's update (2.2 nightly), I don't reproduce it any more... :-/

Autra, thanks for the crash ids! I will have to sort through them.

Naoki, actually, the update I have was from 2.2 to 3.0 (I was on nightly channel). So I still reproduce in 2.2. Don't hesitate to NI me if you need more information.

Thanks. I'm looking at the crashes: https://crash-stats.mozilla.com/report/index/10cf40d6-8664-44dc-aa47-806d12150218 https://crash-stats.mozilla.com/report/index/2dde707f-c182-42c6-8377-fd1ef2150218 https://crash-stats.mozilla.com/report/index/3308ed20-acbc-4d3f-9e82-37d702150218 https://crash-stats.mozilla.com/report/index/cc0de4ec-00e2-45c1-9087-e84af2150218 were all resolved in bug 1114667. The fix landed 2 days ago in 2.2 : https://bugzilla.mozilla.org/show_bug.cgi?id=1114667#c27 which means that I think if you go on today's 2.2 build, you shouldn't crash. Having said that, I need to take a look into : https://crash-stats.mozilla.com/report/index/1d6c013d-4327-4478-87d2-427f42150218 https://crash-stats.mozilla.com/report/index/9f09af95-651e-4d81-8479-2cdbc2150218 https://crash-stats.mozilla.com/report/index/f2f9e373-8fee-41ca-9afd-1fc792150218

Looking at : https://crash-stats.mozilla.com/report/index/1d6c013d-4327-4478-87d2-427f42150218 https://crash-stats.mozilla.com/report/index/9f09af95-651e-4d81-8479-2cdbc2150218 https://crash-stats.mozilla.com/report/index/f2f9e373-8fee-41ca-9afd-1fc792150218 I think the crashes are all the same. I am also guessing that they are related to the first crash some how... as these crashes have an uptime of 2. Ie some residual stuff in cache that needed to be cleared from the previous crash. I think this may be a dup of bug 1114667. Can you try with today's 2.2 to see if you crash? I have a feeling you might not crash.

Hi Naoki, Sorry for answering late, I was a bit busy with RTL :-) So yeah, today's nightly does not crash \o/ Geolocation is working perfectly, as far as I can tell.

No worries. Thanks for the reply. I will close this bug off as a dup then. Thanks again!