My website is made through java and Google web toolkit
When i click on button chrome sometimes becomes unresponsive and i have to kill the page ultimately.
It never happens on firefox and IE.
Is it some cache problem or plugin problem or something else.
I would firstly start looking at your server logs to verify that this is a client based problem rather than bad parameters.
Then verify that HTML/JS is correctly formed and has no errors.
Lastly I suggest to you to use Chrome Developer Tool (Right click) and to choose the profiling tab to collect JS CPU Profiling.
Related
I am having below error while using google colab on google chrome. It started coming up suddenly
Error
Could not load the JavaScript files needed to display output.
This is probably because your Google Account login access has expired or because third-party cookies are not allowed by your browser.
Please reload this page.
I followed instructions from here using this page as some settings have changed. I have added [*.]googleusercontent.com in the section Sites that can always use cookies using the below instructions
On your computer, open Chrome.
At the top right, click More More and
then Settings.
Click Privacy and security and then Cookies and other
site data.
Next to "Sites that can always use cookies," "Always
clear cookies when windows are closed," or "Sites that never use
cookies," click Add.
Apart from that I have tried below steps:
The google chrome>>incognito mode and firefox browser runs fine.
I have already restarted my machine and cleared my cookies.
My javascripts seem to be enable as they are on the setting Sites can use Javascript
My google account is fully functional and not facing any issues with gmail or any other site
How could I resolve this issue?
Do you have too many cells open on your Colab that aren’t needed? Start a new notebook with just the cells you need or get rid of them.
Solution1: Disconnect your collab runtime and Restart your browser.
Solution2: Clearing cookies of last 24hours (and restarting the system) fixed the issue.
If anyone find any better approach, let me know.
There is an issue opened already https://github.com/googlecolab/colabtools/issues/757
I've been trying to research for existing web browsers that do not have an address bar or additional controls on the UI. Ideally a web browser that has just the window frame. The reason is that I am writing a web application, which ideally I do not want the user to have the ability to navigate to other websites or have the ability to navigate backwards/forwards etc. Obviously I can write additional code that can prevent people from navigating other side/ backwards, etc, but ideally would like a clean Window for the user to work from.
So far i've explored the option of building a web browser UI using JavaFX. However the web application is built using Angular and the JavaFX web browser window flickers from time to time during a screen transition.
If there is anyone that can provide a recommendation of such a browser that would be greatly appreciated. Thanks.
Just curious if you have already looked into Kiosk modes for browsers as that is built in and meant to display a single website. If chromium has that then could could use that.
Chromium kiosk mode no address bar or menu
Edit:
https://github.com/chromium/chromium
I have a Java Applet. On IE, it works fine, On Firefox, Firefox frequently given a dialog box saying "The plugin is unresponsive/hung. Do you want to continue waiting for it or kill it?".
In order to troubleshoot, it would be useful to know how firefox detects that the plugin is unresponsive - has Firefox published this info anywhere?
I found this page - https://developer.mozilla.org/en-US/Add-ons/Plugins/Out_of_process_plugins/The_plugin_hang_detector
However this talks about killing the plugin & not giving this error message.
Following are additional measures you can take to resolve Unresponsive Script error.
Waiting longer for the error to resolve itself automatically
Blocking the offending script
Yanking the guilty add-ons
Disabling the hardware acceleration tool.
With one of these few steps, you won’t have to worry about the
Unresponsive Script error, can continue enjoying your browsing
activities on Firefox.
Fix Unresponsive Script Error in Firefox are briefly described below:
Change Script Runtime Value
In the Firefox configurations you’ll get the script runtime value. You’ll need to modify the default value and change it to “20”.
Open Mozilla Firefox.
Type “about:config” in the Address Bar.
Press ENTER.
A warning message will appear. Click “I’ll be careful, I promise!”
link to continue.
Double click a string named “dom.max_script_run_time”.
Replace its value with “20” and press ENTER.
Note: In case the problem still persists you can restore the default value by right clicking the string, selecting “Reset” option.
Use YesScript Plug-In
Install YesScript.
Close and re-load Mozilla Firefox.
Click the Tools menu, select Add-Ons.
Select “YesScript” and click Options.
A new dialog will appear. Enter the website URL which displays you
script error.
Click Add button. This will fix Unresponsive Script Error in
Firefox, Chrome & IE.
Start Firefox in the Safe Mode
In the safe mode a browser is loaded without loading any add-ons. Start the browser in safe mode to resolve faulty add-ons.
Click the Firefox button.
Click Help | Restart with add-ons disabled.
Alternatively, you may press Shift key while starting Firefox.
Disable Hardware Acceleration
Some computers may not support hardware acceleration of the browser. Disable this feature to fix Unresponsive Script Error in Firefox, Chrome & IE.
Click the Firefox button, select Options.
Click Advanced tab.
Uncheck the box “Use hardware acceleration when available”.
Close and re-open the browser.
Restore Default Theme
You might have to restore the default theme. Some of the features of existing theme are not supporting.
Click Firefox button, select Add-Ons.
Click Appearance tab on the left.
Set your default theme.
Disable Synchronization in Firefox
Do not let firefox synchronize items such as apps, settings, tabs, history, passwords, etc Disable the synchronization feature.
Click Firefox button.
Select Options.
Click the Sync tab.
Disable the synchronization feature.
Resource Link:
How to Stop Script Errors on Firefox
I've been pondering over this problem most the afternoon and haven't yet found the most ideal solution so thought I would see what others think..
There is a legacy Win16 application that has to be modified (with the least effort) in order to communicate with a web based application.
The idea is such that in the Win16 app, the user will want to look up a specific code, so they'll click a button which will then launch the browser and allow them to navigate a specific set of pages until they find the result they desire, then they have the option of either pressing Select or Cancel.
Pressing Select should pass back a small string back to the app (around 10 characters) and close the browser. Cancel will likewise send a Cancel message back to the app and again close the browser window.
I can't see many choices available in implementation as the Win16 app is not able to call webservices, so I'm looking at using the clipboard, however that is not without problems.
I hope there's some other alternative I haven't thought of,
As always - all advice appreciated.
Thanks,
I have a simple java applet that retrieves an image from a server and prints it out. The only problem is that I get the following java security warning:
Researching on this site and all over the web, some people suggest that I sign the applet (I tried that to no avail) and others suggest that I Modify a local java security setting but that isn't feasible for my clients.
Not only do I get this warning at the start of my applet, but seemingly any time the code attempts to interact with the printer, the dialog re-appears. Also, note that there is no checkbox next to 'Always allow this applet to access the printer'. These symptoms show on any browser.
How do I get java to respect the users choice to allow it to send jobs to the printer?
You might use the JNLP API services in a sand-boxed applet in a plug-in 2 JRE. They will still prompt the user each first time they go to print, but should also put an 'always allow' check-box on the dialog (though it really only applies for that run). See a demo. of the PrintService.
See also the applet info. page that includes a link on the Next Generation in Applet Java Plug-in Technology which "..brings new abilities to applets: such as .. allowing embedded applets to gain full access to the services of Java Web Start."