Chrome extension AJAX behviour

[Sohan Chotia]

Hello,

I have been working on a chrome extension, which is used for checking multiple thousands of websites status loading them via AJAX.

I have used all async codes and callbacks, and no library, pure native code.

But as it starts and keep running for like 5-6 hours, then after that Chrome start cancelling the AJAX requests, for no reason. We are trying to figure out what can be the possible reason for it.

- we think memory consumption can be one reason, then what can we do to free up memory.

- also we were not able to use or find anything to detect the network connection status, so we had to use on more AJAX call to our server to check n/w status, if some website had status 0.

Please guidance will be appreciated.

[Sohan Chotia]

Please help me on this. 

We tried chrome.runtime.reload() too once per hour, its still mis-behaving.

[PhistucK]

Do all of the AJAX calls fail, or only certain ones, when you reach that failing point?

Have you tried inspecting the AJAX initiating page using the Developer Tools? What do you see in the Network panel?

Chrome has a throttling mechanism when a website returns Error 500 and such, in order to eliminate DDOS cases. Though I am not sure it throttles AJAX requests, it might just throttle navigations.

☆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/4e89bd23-9251-4783-8ad9-10fa65b5ac8f%40chromium.org.

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

[Sohan Chotia]

Yes We have tried all sorts of things we can think off..

in Network Panel, it just keeps cancelling the requests, basically it happens to one single website, which we use to determine the network connection is alive or not.

so its been a pain, and its strange its cancelling it after reload too, 

we have been using ?t=timestamp too to bust cache.

--

Thanks

Sohan Chotia

[PhistucK]

What is the status code of the response of that certain website? Always 200 and the like?

You can look at chrome:net-internals for more information (too verbose, but may still help).

☆PhistucK