Google Omnibox Searches getting crashed to Aw! Snap when Chrome Extension is Installed (Happening Intermittently to only few Users)

[Sachin Jain]

I have developed a Chrome Extension, Requestly which allows you manipulate HTTP Requests. 

3-4 Users have faced an issue where Searching in Omnibox is Crashing the Google Search Results Page and leading to Aw!! Snap while rest of the pages work fine.

Please have a look at this Gif for more understanding.

Issue seems to be resolved by couple of ways:

1. Export Rules, Delete Rules, Restart Browser, Import Rules
2. Simply Restart Browser
3. Clearing Cache

This issue is reproducible on Ubuntu 14, Windows 8.1 Chrome 42. I have Ubuntu 12.10 Chrome 42 and I never saw this issue.

Here is the background.js code on Github. I am just wondering the cause of issue. I have used the following in my code

1. chrome.storage.sync
2. chrome.webRequest.onBeforeRequest (Blocking Option)
3. chrome.webRequest.onBeforeSendHeaders (Blocking Option)

I have observed another Chrome Extension, Scritsafe is facing the same issue. Details mentioned in this thread but the users are still not able to completely get rid of this bug.

One of the kind and helpful user gave me this information by enable logging while launching Chrome but I am not sure if these logs are helpful. These are the logs:

[13753:13788:0515/203052:WARNING:spdy_session.cc(2373)] Received HEADERS for invalid stream 7
[13753:13788:0515/203052:WARNING:spdy_session.cc(2373)] Received HEADERS for invalid stream 11
[133,3746404608:17:30:52.858104] Native Client module will be loaded at base address 0x0000702d00000000
[13753:13788:0515/203058:WARNING:spdy_session.cc(2373)] Received HEADERS for invalid stream 17
[13753:13788:0515/203210:WARNING:spdy_session.cc(2373)] Received HEADERS for invalid stream 55
[13791:13791:0515/173212:WARNING:ipc_message_attachment_set.cc(37)] MessageAttachmentSet destroyed with unconsumed descriptors: 0/1

Main problem is I am not able to manifest this on my machine. If I am able to manifest this, I would certainly try some random things and figure this out.

Here is the Github Repo for Requestly: https://github.com/blunderboy/requestly/

I have done enough Google Research. Now How should I approach to fix this issue ?

PS: Anyone who would like to answer this question on Stackoverflow, here is a clone of this question.

-Sachin

[Simon Knott]

Hi,

We were having a very similar issue using a blocking web request for manipulating response headers - searches in the omnibox or on Google were consistently causing "Aw snap" crashes, but only when a user either:

• had another extension installed which also had a blocking web request 
• had a slow machine

We managed to resolve it by restricting the requests which were covered - initially we were blocking all web requests, but when we filtered it down to main and frame page requests the crashes went away.  My guess is that on XHR requests, if the request blocked for too long (caused either by multiple extensions blocking ir, or by a slower CPU), then the page was crashing.

I've been meaning to raise a bug report, but I just don't have the time to create a sandboxed extension which consistently crashes, so I haven't done it yet.

Cheers,

Simon

[Sachin Jain]

Hi Simon,

Thanks for the information but If you look at the following GIF[0] It shows that there are no rules in the extension, even then the Google Search Results Page crash.

Moreover, whenever it starts happening it keeps happening consistently to that particular User.

BTW I think you are right. I should not block all requests but instead filter down my requests to main, frame, js etc whichever we need.

I take that as very nice suggestion. But how does clearing cache and restarting browser fix the issue for Users. Its quite strange.

I gotta need to reproduce this issue. Can you tell me which extension are you talking about ?

I would install that and try to reproduce the issue. 

[0]: https://camo.githubusercontent.com/e3d935a44694804d705e5035af1103d6231e4dab/687474703a2f2f692e696d6775722e636f6d2f344e7a587650622e676966 

[Simon Knott]

Hi,

We were getting the crashes by the simple action of attached the web request blocking listener - almost all users had no issues until about 2.5 weeks ago (I'd had two people report it before then).  Then something updated in Chrome and a lot of users were suddenly getting crashes on google.com and whenever the omnibar did a search.

The only way I found of forcing it to crash every time was to install the Reddit Enhancement Suite along with our extension (https://chrome.google.com/webstore/detail/reddit-enhancement-suite/kbmfpngjjgdllneeigpgjifpgocmfgmb) - with that installed, it crashed every single time.

I'd give you a link to our extension, but it doesn't do anything unless you have a paid account.

Cheers,

Simon

[Simon Knott]

Sorry, I should have said that we had exactly the same user reports - clearing the cache down, restarting the browser, etc, stopped the crashes for a period of time and then they started again.

As I mentioned, installing the Reddit Chrome extension at the same time forced it to happen every time in our case, no matter what you did.  Fingers crossed it works for you as well, to allow you to reproduce it.

Cheers,

Simon

[Sachin Jain]

Thank you Scott for this information.

Unfortunately, I could not reproduce this even after installing Reddit Enhancement Suite.

Well, Anyways it was definitely useful information. I would post it back to this forum if I find something useful.

-Sachin

[PhistucK]

You should file an issue at crbug.com (if you have not found a similar one already) with all of this information.

☆PhistucK

--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To post to this group, send email to chromium-...@chromium.org.
Visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/7dbddd68-f427-43ca-b53a-f7cfae130b1e%40chromium.org.

For more options, visit https://groups.google.com/a/chromium.org/d/optout.

[Sachin Jain]

Hi PhiStuck,

Thanks for the advice. I have logged an issue on Chromium Project with the above information.

Here is the URL: https://code.google.com/p/chromium/issues/detail?id=489116&thanks=489116&ts=1431919006

Thanks

-Sachin

☆PhistucK

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extensions+unsub...@chromium.org.

To post to this group, send email to chromium-...@chromium.org.
Visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/.