New issue
Advanced search Search tips

Issue 776594 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

localStorage request for https://clients5.google.com/ results in a kill in site-per-process trial

Project Member Reported by lukasza@chromium.org, Oct 19 2017

Issue description

[Renderer kill 123] content::mojom::StoragePartitionServiceStubDispatch::Accept in site-per-process trial can be partially explained by  issue 776160  (Renderer kill when trying to use localStorage from file://localhost/ in --site-per-process).

Nevertheless, there are around 10 kills in the site-per-process trial where killed_process_origin_lock is a real website.  There are 2 reports with:
- killed_process_origin_lock = https://google.com.tw/
- requested_origin: https://clients5.google.com/ 
- requested_site_url: https://google.com/ 
There are a few more reports with the same requested_origin, but with no killed_process_origin_lock crash key.

The 2 reports can be found at:

1) https://crash.corp.google.com/browse?q=custom_data.ChromeCrashProto.channel%3D%27canary%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27%5BRenderer%20kill%20123%5D%20content%3A%3Amojom%3A%3AStoragePartitionServiceStubDispatch%3A%3AAccept%27%20AND%20EXISTS%20(SELECT%201%20FROM%20UNNEST(custom_data.ChromeCrashProto.experiments.ids)%20custom_data_ChromeCrashProto_experiments_ids%20WHERE%20custom_data_ChromeCrashProto_experiments_ids%3D%2747edb3-e5224fcd%27)%20AND%20ReportID%3D%27a400c421e9aa9bd3%27&sql_dialect=googlesql&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D&stbtiq=&reportid=&index=0#2

and at

2) https://crash.corp.google.com/browse?q=custom_data.ChromeCrashProto.channel%3D%27canary%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27%5BRenderer%20kill%20123%5D%20content%3A%3Amojom%3A%3AStoragePartitionServiceStubDispatch%3A%3AAccept%27%20AND%20EXISTS%20(SELECT%201%20FROM%20UNNEST(custom_data.ChromeCrashProto.experiments.ids)%20custom_data_ChromeCrashProto_experiments_ids%20WHERE%20custom_data_ChromeCrashProto_experiments_ids%3D%2747edb3-e5224fcd%27)%20AND%20ReportID%3D%27d396949be452fee3%27&sql_dialect=googlesql&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D&stbtiq=&reportid=&index=0
 
Cc: -alex...@chromium.org lukasza@chromium.org
Owner: alex...@chromium.org
Status: Fixed (was: Untriaged)
These kills were likely explained by issues 780661 and 773140, so I'm tentatively marking this as fixed.  Let's verify this in the next --site-per-process trial and re-open if this reoccurs.

Sign in to add a comment