Closed
Bug 1048402
Opened 10 years ago
Closed 10 years ago
B2G crashes on |make test-perf|
Categories
(Firefox OS Graveyard :: Performance, defect, P1)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: wcosta, Assigned: wcosta)
References
Details
(Keywords: perf, qablocker, regression, Whiteboard: [c=regression p=4 s= u=])
User Story
When running |make test-perf|, B2G eventually crashes.
Attachments
(1 file)
11.09 KB,
text/plain
|
Details |
No description provided.
Assignee | ||
Updated•10 years ago
|
OS: Windows 7 → Linux
Comment 2•10 years ago
|
||
Do you know which app is being tested when this happens? Can it reproduce just by testing this app?
Also please, which git revision for gecko and gaia.
Assignee | ||
Comment 3•10 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #1)
> Wander - Can you get a crash stack for this bug?
Attachment 8466517 [details] of Bug 1046967 has a stack trace. But I suspect that this is just a side effect for the root cause. I am in the middle of a fresh build now. Once it is done I will do more tests.
Flags: needinfo?(wcosta)
Assignee | ||
Comment 4•10 years ago
|
||
(In reply to Hubert Figuiere [:hub] from comment #2)
> Do you know which app is being tested when this happens? Can it reproduce
> just by testing this app?
>
I couldn't find a pattern on that yet. Which I am sure is that it takes more than one run for b2g to crash.
> Also please, which git revision for gecko and gaia.
gecko-dev: efe972f9749251a1580fd07fd22f4db583e4e640
gaia: 5fd14b8bc428f87f9b5cf9cc49f9a4f362a970fb
Comment 5•10 years ago
|
||
[Blocking Requested - why for this release]:
Test blocker for performance testing on 2.1 & a regression.
blocking-b2g: --- → 2.1?
Keywords: qablocker
Comment 6•10 years ago
|
||
I found out when running 30 RUNS that the Overfill crash was back: https://bugzilla.mozilla.org/show_bug.cgi?id=1038136
Comment 7•10 years ago
|
||
BTW a crash during the test is identifiable by this error:
"stack": "{ name: 'Error',\n stack: 'Error: Connection reset by peer!\\n
You should have the name of the test just above the line.
Assignee | ||
Comment 8•10 years ago
|
||
(In reply to Hubert Figuiere [:hub] from comment #7)
> BTW a crash during the test is identifiable by this error:
>
> "stack": "{ name: 'Error',\n stack: 'Error: Connection reset by
> peer!\\n
>
> You should have the name of the test just above the line.
It crashed on video app, I am running a few more times to confirm if it always on video test.
Assignee | ||
Comment 9•10 years ago
|
||
This is the piece of logcat ouput when b2g crashes.
Assignee | ||
Comment 10•10 years ago
|
||
(In reply to Hubert Figuiere [:hub] from comment #2)
> Do you know which app is being tested when this happens? Can it reproduce
> just by testing this app?
>
APP=video RUNS=30 make test-perf does reproduce the crash.
Assignee | ||
Comment 11•10 years ago
|
||
The issue only rises only in debug builds and test-perf is intendend for release builds only.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Updated•10 years ago
|
blocking-b2g: 2.1? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•