I was using Ripple Chrome extension for test running my phonegap apps, and I did all settings for Ripple, like making a Chrome shortcut with --allow-file-access-from-files and in Chrome extension list checking "allow local file access" for Ripple.
On running my HTML file which I made for phonegap build, Chrome is taking a good time to deliver a response. Everything is working, the only issue is the delay on response.
I tried on another desktop, and there it is quiet and fast. I re-installed the extension and restarted Chrome and OS a couple of times to no effect.
For your information, I had similar issues when using Chrome. Make sure Chrome isn't running in the background when you close it. Since a few versions of Chrome, this is enabled by default. Check your taskbar to see if this is the case.
If Chrome is indeed running in the background, right-click on the chrome-icon in the taskbar and disable "running in background". This worked for me and now Ripple fires superfast.
You probably need to confirm your system spec. development workstations are known to be resource demanding, particularly the RAM, and processors. if your app was faster on another system, you might want to check that system's spec also and compare with yours.
Related
I have developed a Google Extension for which I created a Windows installer package. That installer writes the corresponding registry entries as explained in https://developer.chrome.com/extensions/external_extensions#registry
All that works well in some computers. So, after I run the installer package and then run Google Chrome, a little popup appears telling me to enable the extension. I answer “Yes” to that question and from that time on, the extension works as expected.
However, in some computers, with the same version of Chrome (53.0.2785.116 m), the installer writes the corresponding entries to the registry but when I run Chrome, nothing happens and the extension is not listed in the chrome://extensions/ page.
In such cases, I can connect to web store to install the extension manually. However, this extension launches an application because it implements Native Messaging. When I install the extension manually it works (the native messaging host application is launched and works) but when I close and re-open Chrome, the host application is not run. To run it, I need to manually disable and then re-enable the extension.
Very strange what happening. Can you help me on this please?
Based from this thread, (which is somewhat related to your issue), when you close the Chrome, it will fire onDisconnect event that's why the application is not running.
Native messaging means only Chrome can start a host instance when it "connects". It's a misnomer, since connect() means "launch a new copy and talk to it".
There is no way to "attach" to an already-running process. If you close the host, stdio pipe is broken the Port object fires onDisconnect event. Then you need to re-launch the host from the extension to be able to talk to it.
You can check on this link. Just make sure that no antivirus or firewall programs on your computer are causing the problem. If you can open Google Chrome when the firewall is off, you may need to create an exception in your antivirus or firewall settings.
However, in some computers, with the same version of Chrome (53.0.2785.116 m), the installer writes the corresponding entries to the registry but when I run Chrome, nothing happens and the extension is not listed in the chrome://extensions/ page.
You may be encountering blacklisting if that extension was ever installed, then uninstalled.
What if the user uninstalls the extension?
If the user uninstalls the extension through the UI, it will no longer
be installed or updated on each startup. In other words, the external
extension is blacklisted.
How do I get off the blacklist?
If the user uninstalls your extension, you should respect that
decision. However, if you (the developer) accidentally uninstalled
your extension through the UI, you can remove the blacklist tag by
installing the extension normally through the UI, and then
uninstalling it.
I'm running Google Chrome on Windows 10, latest editions. Chrome refuses to open any pages, returning "Aw snap" error messages. To resolve this I've:
Removed all extensions.
Uninstalled and reinstalled Chrome.
Tried Chrome on a different user.
Ran Chrome Cleanup Tool.
Deleted my Google folder in Appdata.
Incognito pages don't work either.
None of these worked. Firefox at all times is working perfectly so its not an internet problem.
Anyone have any ideas on how to fix this?
Please follow below steps, to resolve "Aw snap" error messages with Chrome browser.
Steps To Resolve:
Go to Chrome shortcut in the Desktop (If not exists create one)
Right click -> Properties
In the target field, At the end add a space followed by the below -no-sandbox
Apply-Ok
Launch chrome using the shortcut
Follow the below steps
Go to windows task manager
go to details tab
kill all the chrome process
run the chrome it will open
It is likely that malware is trying (and failing) to modify the page that is loading. I've also seen this as a symptom of machines that had nasty redirect malware removed, as the redirects that the malware creates no longer have anywhere to resolve.
I highly recommend a fresh Windows 10 install, only way to be sure you're fully free of whatever may have infected your current Windows installation.
I wonder if anyone could help me explain this weird thing. I've used Google Chrome incognito mode for a few days, but I observe that it causes the entire performance to slow down and often time unresponsive and even crashes for no reason.
Ubuntu 16.04 TLS
Chrome 58.0.3029.81 (64-bit)
Had same issue with incognito tab. If smth opened in incognito, others instances of chrome start lagging/crashing/not responding.
According to this article Google Chrome Forum step 1 helped me in solving this issue.
Uncheck Use hardware acceleration (Menu> Settings> Show Advanced Settings > System menu).
After this everything is smooth and flying :)
I have a packaged app that calls chrome.runtime.reload(). On a desktop OS (Windows, OSX) this call will cause the application to close, but not restart unless there is an additional Chrome page open.
I assume this is because if it is the only Chrome app running, it closes the Chrome process entirely and there is nothing to restart it.
Adding the background permission looks like it should work, according to the documentation but it does not seem to actually start Chrome when the user logs in (and keep it running) as the documentation states.
A user can override this globally with a setting.
In Chrome's settings with "Show advanced settings":
System > Continue running background apps when Google Chrome is closed
Perhaps it is disabled on your development system.
I have been having an issue lately with Google Chrome. Some sites, seems to be completely random, are returning a 503 Service Unavailable error message. The last one I received was from my hosting provider when trying to access my CPanel. I can access the same URL completely fine in Firefox or IE. It seems to be isolated to Chrome.
I have tried the following:
Disabled all extensions
Logged in/out of my Google account
Cleared all cache and history
So far, nothing seems to correct the issue. It's becoming more and more aggravating from what was once a pretty reliable browser.
I am running:
Windows 7
Chrome Version 36.0.1985.143 m
I was hitting the same issue. Mostly, it would occur on intranet sites at work, but it happened with a few exterior sites. Loading in IE Tab would work fine.
I was able to solve the issue by upgrading to 64-bit Chrome. I'm not sure why that fixed it, but I think it had something to do with a conflict between Java and Chrome (It looks like I have both 64bit and 32bit Java installed side-by-side).
My solution:
Uninstall Chrome with clear personal data option selected
Install Chrome again but without admin right (install for your personal
user)
Use Chrome as normal