Renderer hangs from url_pattern_index / subresource_filter |
||||
Issue descriptionWhen ad tagging is enabled, we see some cases of renderer hangs. Use this query [1] to see them all. These hangs seem to be caused by Facebook error URLs that are huge > 1MB, issued during v8 microtasks. [1]: https://crash.corp.google.com/browse?q=product.name%3D%27Chrome%27%20AND%20expanded_custom_data.ChromeCrashProto.ptype%3D%27renderer%27%20AND%20EXISTS%20(SELECT%201%20FROM%20UNNEST(thread)%20CROSS%20JOIN%20UNNEST(StackTrace.StackFrame)%20WHERE%20SourceFileName%20LIKE%20%27%25url_pattern_index%25%27)%20AND%20crash.reason%3D%27Simulated%20Exception%27
,
Mar 12 2018
Issue 771547 has been merged into this issue.
,
Mar 14 2018
Users experienced this crash on the following builds: Win Dev 66.0.3359.26 - 0.10 CPM, 8 reports, 8 clients (signature [Renderer hang] base::internal::find) If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
Mar 16 2018
Users experienced this crash on the following builds: Win Canary 67.0.3371.0 - 0.17 CPM, 3 reports, 3 clients (signature [Renderer hang] base::internal::find) If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
Oct 1
Only two crashes on beta with the trace in the original description. I think this has dropped to reasonable levels. |
||||
►
Sign in to add a comment |
||||
Comment 1 by csharrison@chromium.org
, Mar 12 2018