Closed Bug 1050764 Opened 11 years ago Closed 11 years ago

crash in android::Parcel::setData(unsigned char const*, unsigned int)

Categories

(Firefox OS Graveyard :: NFC, defect)

All
Gonk (Firefox OS)
defect
Not set
critical

Tracking

(blocking-b2g:2.1+, b2g-v2.1 affected)

RESOLVED DUPLICATE of bug 1055187
blocking-b2g 2.1+
Tracking Status
b2g-v2.1 --- affected

People

(Reporter: zcampbell, Assigned: allstars.chh)

References

Details

(Keywords: crash, regression)

Crash Data

Attachments

(1 file)

This bug was filed from the Socorro interface and is report bp-2b99e955-d19c-47b7-8fa4-639082140808. ============================================================= Flame: Gaia 5709345df31c5fab5cc5c051d591d4e76ca4f706 Gecko https://hg.mozilla.org/mozilla-central/rev/afcb3af79d09 BuildID 20140807040201 Version 34.0a1 ro.build.version.incremental=110 ro.build.date=Fri Jun 27 15:57:58 CST 2014 B1TC00011230
Zac - Do you know what STR you used to hit this crash?
Flags: needinfo?(zcampbell)
Component: General → NFC
I was running test automation and happened to catch the device with the crash submission dialogue open so cancelled the test and submitted the crash. I couldn't say what caused it but I wanted to log it for posterity.
Flags: needinfo?(zcampbell)
Alison, would you please help the developers run this test on master until you/they can reproduce the failure? Thanks!
Flags: needinfo?(ashiue)
I'll look into first.
Assignee: nobody → allstars.chh
Flags: needinfo?(ashiue)
I've run several times but didn't meet the crash. Also It seems Stephen uses an older version of nfcd.
(In reply to Yoshi Huang[:allstars.chh] from comment #7) > I've run several times but didn't meet the crash. > Also It seems Stephen uses an older version of nfcd. I've confirmed that we're running the V123+fonts base/vendor build, so not sure how/why nfcd is out of date.
(In reply to Stephen Donner [:stephend] from comment #8) > (In reply to Yoshi Huang[:allstars.chh] from comment #7) > > I've run several times but didn't meet the crash. > > Also It seems Stephen uses an older version of nfcd. > > I've confirmed that we're running the V123+fonts base/vendor build, so not > sure how/why nfcd is out of date. Thomas, do you know why we might be on an older version of nfcd, despite being on the latest vendor base build of V123+fonts?
Flags: needinfo?(tzimmermann)
(In reply to Stephen Donner [:stephend] from comment #9) > (In reply to Stephen Donner [:stephend] from comment #8) > > (In reply to Yoshi Huang[:allstars.chh] from comment #7) > > > I've run several times but didn't meet the crash. > > > Also It seems Stephen uses an older version of nfcd. > > > > I've confirmed that we're running the V123+fonts base/vendor build, so not > > sure how/why nfcd is out of date. > > Thomas, do you know why we might be on an older version of nfcd, despite > being on the latest vendor base build of V123+fonts? No, no idea. The latest version should always be in the branch 'master'. Dimi, do you know about any exceptions?
Flags: needinfo?(tzimmermann) → needinfo?(dlee)
(In reply to Thomas Zimmermann [:tzimmermann] [:tdz] from comment #10) > (In reply to Stephen Donner [:stephend] from comment #9) > > (In reply to Stephen Donner [:stephend] from comment #8) > > > (In reply to Yoshi Huang[:allstars.chh] from comment #7) > > > > I've run several times but didn't meet the crash. > > > > Also It seems Stephen uses an older version of nfcd. > > > > > > I've confirmed that we're running the V123+fonts base/vendor build, so not > > > sure how/why nfcd is out of date. > > > > Thomas, do you know why we might be on an older version of nfcd, despite > > being on the latest vendor base build of V123+fonts? > > No, no idea. The latest version should always be in the branch 'master'. > Dimi, do you know about any exceptions? If you are using vendor's build as base image, then the nfcd may be older one because they don't keep updating nfcd to latest build.
Flags: needinfo?(dlee)
All of QA team is synchronised onto the same public base build.
I just hit this crash, while hunting another crash. Below are my variables and some STR's I was doing. STR: 1. Launch Video app. 2. Start playing a video 3. Tap the home button to put it into the background. 4. Hold the Home button and quickly tap Restart until the phone restart happens. Tried to reproduce this about 20 times with no luck. 1/20 Environmental Variables: Device: Flame Master BuildID: 20140821060216 Gaia: c8e93dadeaec6a2617b4db8b7d65ba14aa8db378 Gecko: c14e5feadc61 Version: 34.0a1 (Master) Firmware Version: v122
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
[Blocking Requested - why for this release]: Request for nominate to 2.1+ as this should be regression from Bug 933588.
blocking-b2g: --- → 2.1?
Blocks: 933588
Keywords: regression
triage: regression, crash
blocking-b2g: 2.1? → 2.1+
I just hit this crash while working on the test pass. Prerequisite: have 2 devices with NFC enabled. Repro Steps: 1) Update a Flame device to BuildID: 20140827040203 2) Open an item that can be shared through NFC on one of the phones 3) Move devices back to back so that "Swipe to share" appears 4) Pull devices apart so they return to normal 5) Repeat steps 3-4 at least 4 times 6) Observe one or both devices crashing Repro Rate: 11/12 Notes: It is not always the same device that will crash but one of the devices will almost always crash following these steps. Environmental Variables: Device: Flame 2.1 Master (319mb) BuildID: 20140827040203 Gaia: 6e804a42ab90f4251c7fe8c68731dc1c6abd8006 Gecko: 0753f7b93ab7 Version: 34.0a1 (2.1 Master) Firmware: V123 User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(dharris)
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(dharris)
Keywords: regression
Removing regression window wanted, did not realize the window was already found
QA Whiteboard: [QAnalyst-Triage+]
I hit this crash 2x today - once when I was actually on an active phone call. I hope this gets fixed soon.
Firmware v122 and v123 uses older nfcd, which will send fragmented data. The master branch of nfcd already fixes this.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: