Kernel
Reported by
grayneve...@gmail.com,
Oct 11 2016
|
||||
Issue description
<b>Chrome Version : <Copy from: 'about:version'></b>
OS Version:
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5:
Firefox 4.x:
IE 7/8/9:
What steps will reproduce the problem?
1.
2.
3.
What is the expected result?
What happens instead of that?
Please provide any additional information below. Attach a screenshot if
possible.
,
Oct 11 2016
Could you upload the full crash report? The report indicates that the problem took place on thread 5 but the thread is not visible on the screenshots. It looks that the app requested some time to finish an operation when it was moved to background but couldn't finish the work within the allocated time. As the result, the app was killed by iOS.
,
Oct 11 2016
,
Oct 11 2016
This may help
,
Oct 13 2016
,
Oct 13 2016
{"timestamp":"2016-10-13 09:37:06.53 +0100","bug_type":"157","os_version":"iPhone OS 10.0.2 (14A456)","incident_id":"BEE128A9-5DA4-4FE8-BA17-66F37BAB5D30"}
Date/Time: 2016-10-12 00:00:00 +0100
OS Version: iPhone OS 10.0.2 (Build 14A456)
Architecture: arm64
Report Version: 19
Event: powerstats
Start time: 2016-10-12 00:00:00 +0100
End time: 2016-10-13 00:00:00 +0100
Duration: 86400s
Steps: 85
Hardware model: iPhone6,2
Active cpus: 2
Binary Images:
1 libsystem_kernel.dylib <04E6664A-F080-30E1-AD7D-9F2249E47E18> /usr/lib/system/libsystem_kernel.dylib
2 libsqlite3.dylib <51121563-7EDC-3A0F-8D34-16FE4536881D> /usr/lib/libsqlite3.dylib
3 libsystem_platform.dylib <67358148-99ED-3284-99CE-8A0F59FF49B6> /usr/lib/system/libsystem_platform.dylib
4 libcorecrypto.dylib <69592D5D-E33D-337B-AF07-46846B8E8B71> /usr/lib/system/libcorecrypto.dylib
5 libdispatch.dylib <9DA4900C-6D95-3655-BBFC-C6B31C990E9C> /usr/lib/system/libdispatch.dylib
6 libsystem_pthread.dylib <BE17C5DE-3FF8-3A86-9591-3479341C34EC> /usr/lib/system/libsystem_pthread.dylib
7 <DFF973DD-25F3-35AC-B2DD-1C776D04C9B4>
Powerstats for: locationd
UUID: 7
Microstackshots: 85 samples
Primary state: 33 samples state 0x214
0 85 6 + 4808
1 85 5 + 69868
2 85 5 + 70540
3 85 5 + 63808
4 85 5 + 18856
5 85 5 + 62532
6 85 4 + 401856
7 85 7 + 14125768
8 85 7 + 12981908
9 85 7 + 12982208
10 85 7 + 756408
11 85 7 + 752320
12 85 7 + 807840
13 72 7 + 947236
14 72 7 + 625012
15 72 7 + 615428
16 72 5 + 59488
17 72 4 + 401856
18 72 7 + 629964
19 72 7 + 625284
20 72 7 + 778912
21 72 7 + 771648
22 72 2 + 264932
23 44 2 + 271396
24 44 2 + 338096
25 37 2 + 688932
26 25 2 + 574880
27 25 2 + 175252
28 25 2 + 37124
29 25 1 + 9520
30 19 <state 0x294>
30 4 <state 0x29c>
30 2 <state 0x298>
26 12 2 + 574408
27 10 2 + 173580
28 9 3 + 8672
29 3 <state 0x21c>
29 1 <state 0x218>
28 1 3 + 8680
27 2 2 + 172424
28 2 2 + 873372
29 2 2 + 173952
30 2 <state 0x294>
25 7 2 + 689016
26 7 2 + 332592
27 3 <state 0x21c>
27 2 <state 0x218>
23 6 2 + 337772
24 2 <state 0x21c>
24 1 <state 0x218>
23 5 2 + 269888
24 1 <state 0x21c>
23 4 2 + 305228
24 4 2 + 374280
25 3 3 + 5424
23 4 2 + 327848
24 4 2 + 152192
25 4 2 + 356548
26 4 2 + 359144
27 1 <state 0x21c>
23 3 2 + 289232
23 3 2 + 374216
23 1 2 + 332892
23 1 2 + 271420
23 1 2 + 305352
13 13 7 + 947308
14 13 7 + 625512
15 13 7 + 615428
16 13 5 + 59488
17 13 4 + 401856
18 13 7 + 629964
19 13 7 + 625784
20 13 7 + 937248
21 13 7 + 930284
22 13 2 + 264932
23 6 2 + 327848
24 6 2 + 150104
25 6 2 + 465708
26 6 2 + 468116
27 6 2 + 469388
28 6 2 + 871692
29 6 1 + 4256
30 3 <state 0x294>
30 2 <state 0x29c>
30 1 <state 0x298>
23 6 2 + 271396
24 6 2 + 338096
25 6 2 + 688932
26 6 2 + 574880
27 6 2 + 175252
28 6 2 + 629352
29 2 <state 0x21c>
29 2 <state 0x218>
23 1 2 + 271928
24 1 2 + 155640
25 1 2 + 574408
26 1 2 + 172756
27 1 1 + 10348
28 1 1 + 4232
29 1 <state 0x294>
,
Oct 13 2016
Google.app? That's GSA, not Chrome for iOS, isn't it?
,
Oct 17 2016
This indeed looks like iGSA.
,
Oct 18 2016
The com.Google.GoogleMobile is indeed Google App, which is using Chromium Network stack internally, but it is not using Chromium bug tracker, so there isn't anything that we can do on this side. You can use Settings -> Feedback menu inside of the Google.app to describe an issue or share your ideas, and optionally include system logs with more information. |
||||
►
Sign in to add a comment |
||||
Comment 1 by rdsmith@chromium.org
, Oct 11 2016