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.
Related
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.
Can someone please shed some light or point me in a different direction.
We are using adobe flash that launches an app inside of a JSP. Up until yesterday everything was running fine without any issues. Today when the Flash Object launches you can see the initialize bar where before you hardly seen it.
While working within the app as well all the operations are very slow (not much but a 2 second delay on most of the things is visible).
I have 3 browsers installed on my PC
IE 11 running Flash version 23.0.0.207
Chrome 55.0.2883.87 running Flash version 24.0.0.194
Waterfox 32.0 also running the same Flash version as IE 23.0.0.207
Running the app from all 3 these browsers is slow apart from Waterfox.
I deleted all the caches from the flash settings in control panel and for chrome I used the web interface (http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager07.html).
I cleared all browser caches. We are running McCafee which I disabled.
I had a look at any windows updates that was done recently which I uninstalled.
What could be different between these? What else can be checked to see what is making this app slow in IE and Chrome?
The slowness could be caused by the files not being cached by the browser like they used to be. I would start there. If you reload the page and you're not seeing a 304 "Not Modified" for the swf(s) you're loading them from the server each time where they used to be loaded from the browsers cache.
Here's some more info on the subject: https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/http-caching
Both Chrome and IE have developer tools you can load to see the http calls and check the headers and response codes.
https://msdn.microsoft.com/en-us/library/dd565628(v=vs.85).aspx
https://developer.chrome.com/devtools
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.
Ever since Flash Player 10 came out, the debugger version causes what seems like a crash in my browser, either Safari, or Firefox, on Mac OS X. It's been consistently happening with 10.0, 10.1 and 10.2.
And it's not just on the applications I develop. Six or seven times out of ten, when I visit sites like Gamespot with Flash video delivery and a banner ad or two, the debugger kicks out an error and, upon dismissing that error, I can't regain focus of my browser. Clicking a window does nothing but trigger the Mac OS X error sound. I have to force-quit and start again.
The Adobe forums have been no help, and everything else I've seen relative to the debugger crash issues doesn't seem to solve my problem. Any ideas?
I'm not sure if this works on a Mac as well, but on a Windows machine, this hack saved me already some time: Often it is just enough to kill the task "plugin-container.exe". This will stop all flash movies immediately and unfreeze your browser. So you can work on without losing all work done in other browser tabs and waiting for your browser to restart.
I'm having a strange issue with Chrome.
I'm working on development with a very image heavy website. If I reload a page over and over again, eventually half the images or more will just disappear. (they don't seem to be broken, just not visible).
If I clear my local cache in Chrome and refresh the page, the images return.
Any idea what may be causing this and how to possibly fix?
edit: just to note, it's not just me. Others hav reported the same issue on the website I'm working on. Always Chrome.
Images, which contains "content-length" header randomly disapper, removing this at the server side solves this bug...
(chrome dev team has this issue in "open" state in their bug tracing system)
I've been getting this recently too. I generally use the latest dev channel for Chrome and assumed it was related to that, but even when launching the regular version of Chrome I get the same issue. I've only noticed it for the past 2-3 months though. Hard-refresh does the job, but it's a really odd bug.