Clever Geek Handbook

Reloading UwAmp causes Chrome pages to crash

Whenever UwAmp reloads (like when I change php.ini or switch to a different php version), it often resets all open Chrome pages, be they pages I test on UwAmp or something totally unrelated like Facebook. They are empty and I have to reload them. Sometimes it closes Chrome completely, I have to restart it and I get a message that Chrome closed unexpectedly. What gives? Is this a known bug? Is there a way to prevent this? How and why does UwAmp even control Chrome? This applies to Windows 10 x64, UwAmp 3.1.0, latest 64-bit Chrome.

Thank!

EDIT: It just closed Notepad ++ on me, so it is not specific to Chrome. There also appears a message that sometimes appears in UwAmp saying that the process cannot be killed because access is denied. Is UwAmp trying to kill the wrong process? This also happens when I manually click the Stop button.

+3


source to share


2 answers


This is the problem I am facing. If I quit UwAmp, sometimes it will close another program (Firefox, qBittorrent, Spotify ...)

I reported this issue to the developer but received no response.



So, I think we'll have to live with him.

+2


source


When you start a session / computer, first open any other software you want to use (chrome, firefox, aBittorrent, Sportify or whatever). Then open uwamp at the end .



It shouldn't reset any other software when you stop / start apache / mysql or close uwamp.

0


source






More articles:


All Articles