My application is working fine in all browsers Chrome , Firefox , (except ie 11).
We have a loader that is common for Ajax calling. It get stucks or hangs at some controllers randomly.
IE 11 is displaying a message on the footer "localhost is not responding due to a long running script" .Also note the application is working fine .Assuming this is some thing specific to IE 11 .
Any idea would be appreciable .
Thanks,
Avi Verma.
Related
I've recently ported my chrome extension to safari using the safari web extension converter: https://developer.apple.com/documentation/safariservices/safari_web_extensions/converting_a_web_extension_for_safari.
However, I'm finding that my setInterval calls only executed a set number of times in the background page. When I open the background page for my web extension, I've tried running a simple interval to see the result:
Safari Web Extension Background Page with interval stuck after running set number of times
When I try the same thing for my chrome web extension, the interval runs indefinitely:
Chrome Web Extension Background Page with interval running continuously
If I try to run the interval after opening the dev console for any random web page in Safari, the interval works fine:
Safari content page with interval running continuously
Similarly, a recursive setTimeout function fails in the background page for the web extension:
Recursive setTimeout function in my background page
Result of recursive set timeout function in my background page (stops afterwards)
I'm not sure why timers might be failing in background page for Safari. My extension works perfectly fine in chrome/brave/firefox. Thanks!
When the extension is not active safari browser stops the background process of that specific extension.
Alternative approach: You can create a timeout in the content script and message background from the content script periodically to check your requirement.
I saw the same issue. setInterval() was throttled after 6 iterations, no matter the interval. Calls were made, but sporadically, like once a minute at first and even further apart later.
I fixed this by switching to alarms API instead of setInterval(). Seems to work fine.
Safari 16.3, macOS 12.6 Monterey.
I'm working on a monitoring tool for my website to log data. The actual logging is made on server. My goal is to calculate stats based on how long the user stays on the website.
Main question: I used chrome headless command --remote-debugging-port=80. I got logs for up to 10 minutes. Works perfectly. But how long will it work if left working? Is there a default timeout? If yes, how can I change it? If I want to run it exactly 30 minutes after page finished loading?
I'm trying to do the same on firefox (tried using PhantomJS but it wasn't loading the page correctly even though useragent was set to firefox) but firefox just throws an bank page when I'm trying to start a headless mode. I used "firefox -headless" and tried capturing an screenshot. It was just exiting my currently open firefox tabs without capturing any image. Any idea?
Using firefox quantum 59.0. I don't want to use selenium.
Also PhantomJS solution would be great. Currently I just want to collect logs. So, it only have to run all javascript (an jquery) code on the page which then sends the data using ajax. I tried page.onLoadFinished and then a wait function to make it stay on the page for the exact time after page loading.
Since no one answered, I will try to answer my own question after even more research and logical thinking.
Main question: Seems that there is no timeout but if need can be used --timeout X. Even though it's not perfect because it runs independently if the page if fully loaded or not.
As for the firefox, it's buggy. -new-instance (make headless run while you are already on firefox) is not working and -no-remote didn't help. Firefox is only working if running only one instance. So, if it's the PC you are working on and you want to run tests too, firefox is not for you. Headless runs only when no other instances of firefox are running, while chrome runs fine.
PhantomJS didn't work even though tried multiple solutions.
Best solution? Use chrome. Need portable? Use chromium and use headless. Or write your soft to use cefsharp which is based on chromium. Your browser with all libs will be around 120-200MB. Pretty big for portable but do it's work. Same as portable chrome or chromium. CefSharp have a privilege of integrating whatever you like into the browser since it's a... browser.
Running on Windows 7 Enterprise, 64-Bit OS, with Chrome Version 65.0.3325.181 (Official Build) (64-bit) and ChromeDriver version 2.37.
The same code runs flawlessly in Firefox. I am using webdriver to fill out a page (say page 1) that will generate an XML link. When I click the link from page 1 it will open the XML page in a new window. My code switches to the window and calls "getCurrentUrl()". Once it hits this snippet of code, it hangs for several minutes and returns:
[1523382059.135][SEVERE]: Timed out receiving message from renderer:
300.000 [1523382059.138][SEVERE]: Timed out receiving message from renderer: -0.002.
However, if I manually refresh the page, it will return the URL and finish executing.I have tried telling selenium to send control + F5, as well as the refresh methods and even telling it to get(getCurrentUrl() ).
Could this be an issue with proxys or maybe an issue with pulling the page, since it is just raw XML?
Thanks for the time and help.
I have recently had issues with Selenium and the chrome driver myself. Even though its not ideal have you tried using a implicit or explicit wait? Thread.sleep() has worked for me in the past when all else failed.
When running several tests synchronously using Selenium with IE, after about 10 minutes the browser starts to freeze. The browser will not render pages properly or respond at all. I can only diagnose that when these symptoms occur, the Memory reaches about 1.7G and hovers around there. I use Capybara so after every test, on average about every 30 seconds, it will reset the session. This issue does not occur when I use Firefox or Chrome.
Does anyone have any thoughts? I could try figuring out why it stops at 1.6G, but I imagine I'd hit the same issue once hit what ever new cap is set. I could also restart the process every few tests, but that would slow the test run down dramatically.
Configuration:
OS: Windows 7 64-bit
Selenium grid: v2.46.0
IEDriver: 32-bit
v2.46.0.0 (Tried using 64 bit but sending keys went very slow)
Browser: IE11
Thanks in advance for thoughts you might have.
We ran into the same problem and noticed that every character typed using sendKeys() consumes around 2 MB (!) in IE. We now restart the driver every 10 tests, which works for us.
Note: you could try replacing webElement.sendKeys with a Windows API call like SendInput and see if the problem in IE still remains.
I wrote an application using the HTML5 Cache Manifest and I'm having a problem using it in IE 10.
I used Fiddler to witness the manifest file being downloaded and all resources fetched on the initial load of the application. If I disable my network adapter to force the machine offline, the application continues to work as expected as long as I don't close the browser window.
However, when I close the browser window, then attempt to re-open the page from a favorite, IE 10 tells me "You're not connected to a network". Obviously I know that, I'm trying to use the app offline. These exact steps work in Chrome.
Is this behavior by design? Is there a workaround? I can't test with IE 11 right now...is this different in IE 11?
Hearing of some issues of the appcache clearing if your company utilizes gpo settings and has "empty temporary internet files folder when browser is closed" enabled.
Did you find the answer to this? I have the same problem. I did get a bit further though. I found that if you go to the IE10 File menu option and tick Work Offline then try and access your cached app it loads the page but I still have an issue as it does not appear to be using the javascript file that should also be cached. All works ok on Google Chrome but our clients are restricted to IE so Chrome is not an option.