Description: On the "What's in a crash report" page the header is truncated Device: Buri v1.2 Aurora COM RIL BuildID: 20131021004006 Gaia: 1fd315337d8ae891c3024e4c682c4c50797ea40e Gecko: d585fe28cd55 Version: 26.0a2 Firmware Version: US_20130930 RIL Information: 01.02.00.019.082 Repro frequency: 100% See attached: (screenshot
Steps to repro: 1) Crash the app such as "Browser" with the command: adb shell kill -11 https://wiki.mozilla.org/B2G/QA/Gaia_Test_Plan/Crash 2) Tap the "what's in a crash report" link Actual result: The header is truncated Expected result: The header is not truncated
Created attachment 819967 [details] 2013-10-21-14-18-46.png
Attachment #819895 - Attachment is obsolete: true
Comment on attachment 819895 [details] 2013-10-21-14-47-58.png Marking as non obsolete, the other attachment is probably for bug 929173
Attachment #819895 - Attachment is obsolete: false
Attachment #819967 - Attachment is obsolete: true
(In reply to sarsenyev from comment #2) > Steps to repro: > 1) Crash the app such as "Browser" with the command: adb shell kill -11 > https://wiki.mozilla.org/B2G/QA/Gaia_Test_Plan/Crash > 2) Tap the "what's in a crash report" link > > Actual result: > The header is truncated > > Expected result: > The header is not truncated I tried to shorten the strings but no idea how to test this. If I crash the browser I just get an error page, no links. http://hg.mozilla.org/releases/gaia-l10n/v1_2/it/rev/6ff03d53012e
Francesco, This screen I'm getting when crashing the system app, not the browser page, To see the crash, open any app like "Clock" and when entering crashing commend, choose /system...
Sorry but I still don't get it. I run adb shell ps and check the existing processes, then I open "Clock", run ps again but I can't find anything related to it in the processes. If I kill /system/b2g/b2g I just restart the entire phone.
You should kill app not root: app_508 508 141 78300 28592 ffffffff 400f9604 S /system/b2g/plugin-contain But I checked it for you the strings are no longer truncated on the latest build
Therefore marking as resolved fixed
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.