Whenever UwAmp restarts itself (for example, when I modify php.ini or switch to a different version of php) it often crashes whatever Chrome pages I have opened, whether they are pages that I'm testing on UwAmp or something completely unrelated like Facebook. They go blank and I have to reload them. Sometimes it closes Chrome altogether, I have to restart it and I get the message saying that Chrome closed unexpectedly. What gives? Is this a known bug? Is there any way to prevent it? How and why does UwAmp even have control over Chrome? This is on Windows 10 x64, UwAmp 3.1.0, latest 64-bit Chrome.
Thanks!
EDIT: It just closed Notepad++ on me, so it's not specific to Chrome. There's also a message that pops up sometimes within UwAmp, saying that the process couldn't be killed because access was denied. Maybe UwAmp is trying to kill the wrong process? It also happens when I manually click the "Stop" button.
That's an issue I encounter too. If I exit UwAmp, sometimes it force closes another program (Firefox, qBittorrent, Spotify...)
I had reported this issue to the developer, but got no reply.
So, I guess we'll have to live with it.
When you start your session/computer, open first all the other softwares you wish to use (chrome, firefox, aBittorrent, Sportify or whatsoever). Then at the end, open uwamp.
It shouldn't crash down other softwares when you stop/start apache/mysql, or when you close down uwamp.
A workaround is to open uwamp.ini and change the AUTO_RESTAT_CONFIG_CHANGED to "0".
This will disable uWamp's auto-restart feature during server configuration changes.
Related
Context: I have three web browsers installed on my Windows 10 computer which are Chrome, Firefox, and Opera.
Problem: Whichever browser I newly open, they all start with this website:http://007eecfcfedlkh.jumpkj.chuairan.com/index.html
How it happened: I clicked a link on a website yesterday and it automatically downloaded several applications and automatically installed themselves without showing any instructions to install them.
Thing I have tried: I have reset the browser On startup setting to open my homepage, but it still opens with the aforementioned weird URL.
Thing that may help: Opera browser is very considerate cause it has this option regarding the On startup setting, which is Ask me when Opera is started by a shortcut specifying an URL.
Analysis and need your help: Usually, I start a browser by clicking on the shortcut in Windows start menu, or the shortcut in desktop. This worked normally until the problem appeared. According to Thing that may help, this hostile URL must reside somewhere. Where can I find this unwelcoming shortcut on my computer? How come this shortcut can attach itself to every web browser on my computer? What is the next step I can do to resolve this problem? Is this kind of a virus?
Usually when that happens, you'll have to:
reset the browser settings (or at least reset the startup websites on settings)
go to the browser .exe, open it's properties and remove any flags that were added on the path.
I think you shoud uninstall these applications first.
My issue is similar that of the user who posted this question earlier this year. I was doing some work automating tests with Cypress, and ended up in a state where the address bar indicates that the "browser is under remote control" with the robot icon but otherwise works as intended.
I have tried restarting my computer, uninstalling and reinstalling Firefox, "Refreshing Firefox" using the troubleshooting menu, and clearing the startup cache. Yet the problem persists.
This older post is from a user who was using Selenium/gecko and he/she claims the marionette.enabled config value was getting in the way.
EDIT: Changing this did solve my issue! But after flipping the flag you must restart the application.
Firefox will be my primary browser either way, but I'm not a fan of the striped address bar. It's quite the eye sore!
Any advice? Thanks in advance!
See EDIT above.
Navigate to about:config
Flip marionette.enabled to false
Restart browser
I currently run a 64bit Windows 10 development box. I have old VB6 source that I have to unfortunately keep updated for the time being. For some reason all the sudden I noticed that one of the applications I have just built seemed to stay running in the background after the GUI was closed.
I started debugging the issue more and more until I found out that the only time it would seem to persistently stay open in the background after the GUI was closed was if I clicked the button on my form that would call the Common Dialog control to show the file open GUI. I only have to show the file open window and then hit cancel for this to happen.
This ONLY seems to happen on ONE of my dev machines (not the other). Every time I use that CD file open box I have to open task manager up and end the task. I also tried to make sure all forms were closed when my main form starts to Unload. Nothing seems to work or shed any clue on what the issue is. I have also double checked that the following files are now all the same coping them from the known working dev machine to my broken one and re-registering them.
COMDLG32.OCX
comdlg32.oca
comdlg32.dll
COMDLG32.DEP
Both machines are running the same exact OS Win10 Pro 64bit.
That does sound strange, getting different results on the two machines. Pragmatically, you can work around the problem (without actually understanding it) by making sure that you execute an End statement. (You can put it in the QueryUnload event to make sure it's hit if the user clicks the "X".)
We are having some wierd behavior in firefox with silverlight. We have tried everything and I am hoping for some more ideas. Below is the behavior
Install firefox (3.6.12) and silverlight (4.0.50917.0). The versions there are locked and not controlled by us and on all our users machines.
Visit our silverlight application (also tried simple application with just a background)
Instead of seeing our application, you see "Get Microsoft Silverlight"
-- (about:plugins reports silverlight 4.0.50917.0 installed and enabled)
Visit site in IE, app works
Install or uninstall any plug-in (tried Firebug and IETab2)
After install, click "Restart" when prompted
After FF restarts, silverlight works as expected
Close firefox and reopen.
Once again, silverlight is broken
Any ideas? We tried the CWDIllegalInDllSearch entry in the registry to no avail. Please help!
I think it is a problem with Firefox that has been fixed with Version 3.6.14. See this BugReport on Bugzilla. A memory leak in prior versions, cause some problems in the Silverlight detection script of Firefox.
I can only suggest to update Firefox to version 3.6.14. But before i would try it in a local test environment to check if its really a bug in Firefox.
Update:
It seems to be a general problem with Firefox 3.6.x, cause some users report the same error as your with higher versions than 3.6.14. See here and here.
The only thing that springs to mind is disabling the plugin-container
In Firefox address bar type about:config
Read the warning, choose your preference to always remind you or not and accept
In the search bar of the config options now type: npctrl
You should then see the entry: dom.ipc.plugins.enabled.npctrl.dll
Change the value from true to false (simply double-clicking will change this for you)
Restart Firefox
EDIT
There is another workaround which is to disable then re-enable silverlight plugin. Rather than re-isntalling.
Since the latest update to Firefox 3.6.13 I can no longer debug flash apps. If I have the debug flash player installed, it hangs when loading my application, and never connects to the debugger.
I'm running Flash Debug 10.2 (latest one).
I've tried uninstalling / reinstalling, but I get the same experience.
When the page loads, the browser hangs, 10+ seconds later, the page continues. It happens on my application as well as sites like Hulu.
Anyone else have similar issues?
I already disabled the dom.ipc.plugins.enabled.npswf32.dll and set timeoutSecs to -1.
--EDIT--
This issue seems to happen in all browsers (IE, Firefox, Chrome) with Flash Debug player 10.1 or 10.2. I'm not quite sure what the issue might be.
Somehow my hosts entry for "localhost" got mangled when editing the file. This caused the debugger to look for a debug host on another machine. It then waited for the timeout before continuing to work.
Fixing the localhost issue fixed my debugging issue.