Closed Bug 1042248 Opened 11 years ago Closed 11 years ago

[Search] entering text in the search bar causes "{{name}}" crash

Categories

(Core :: DOM: Core & HTML, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1041646
Tracking Status
b2g-v2.1 --- affected

People

(Reporter: njpark, Unassigned)

Details

(Whiteboard: [systemsfe])

STR: - Flash device, and on the top search bar, type 'toyota'. - Select enable if location prompt comes up - press home button to exit after the results are shown Expected: - Exits to homescreen normally Actual: crash is reported Note: this does not happen again after reboot Crash log: https://crash-stats.mozilla.com/report/index/e0b47b68-6d59-4c44-9cd8-8b4f42140722 Version Info: Gaia e423c3be8d19c9a8a5ae2571f499c36dc6b0df89 Gecko https://hg.mozilla.org/mozilla-central/rev/6f702709fab6 BuildID 20140722040212 Version 34.0a1 ro.build.version.incremental=eng.tclxa.20131223.163538 ro.build.date=Mon Dec 23 16:36:04 CST 2013
[Blocking Requested - why for this release]:
blocking-b2g: --- → 2.1?
(In reply to No-Jun Park [:njpark] from comment #1) > [Blocking Requested - why for this release]: The device crashes in the middle of the search process
Component: Gaia::Everything.me → Gaia::Search
QA Whiteboard: [VH-FL-blocking-][VH-FC-blocking-]
Whiteboard: [systemsfe]
This may be related to bug 1041510; will need to retest once a fix is there.
Summary: [Everything.me] entering text in the search bar causes "{{name}}" crash → [Search] entering text in the search bar causes "{{name}}" crash
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #3) > This may be related to bug 1041510; will need to retest once a fix is there. From what I can tell - The crash stack I'm seeing here looks like a DOM or JS crash, since there's DOM/JS code references present in the crash stack. However, I don't see any layout-based crash symbols at the top of the stack. Going to bounce this into DOM first to have someone from that team look at this crash. I'm also adding qawanted for branch checks.
Component: Gaia::Search → DOM
Keywords: qawanted
Product: Firefox OS → Core
Status: NEW → RESOLVED
blocking-b2g: 2.1? → ---
Closed: 11 years ago
Keywords: qawanted
Resolution: --- → DUPLICATE
Is it possible to get this crash in a debugger and look at the top frame? Breakpad is not dealing well with the inlining going on there, clearly, so it's not clear where we're actually crashing.
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.