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
Related
This is a really weird problem that appeared in the recent version of Chrome.
I have a huge app that loads hundreds of stylesheets (in dev mode). When the page loads, obviously all styles are applied but background images are missing!
If I just do nothing and wait, suddenly the images start loading randomly...
Using dev tools I checked the network tab to see if the images are requested.. but no, just a few of them appear in contrast to the previous version of Chrome.
Does anyone know if any kind of optimization has been added in Chrome that makes images load lazily? Obviously that implementation is buggy and does not consider a page with a lot of stylesheets!
This problem does not affect the app in production, where all the stylesheets are packed and reduced to just ~10.
Tested on Linux and Windows 7
I had a similar problem with our web site on Chrome 27.0.1453.93 and 27.0.1453.94. It turns out that Chrome seemed to think that all of our .gif images were corrupt. They wouldn't render in Chrome but they would render fine in IE, Firefox, and older Chrome versions.
I'm not sure what the underlying issue was, but I opened the images in Photoshop and re-saved them and now it works fine.
I'm having troubles testing a StageVideo file locally. The HTML file that contains the swf loads perfectly in Chrome & FireFox, but when I go to open it in Internet Explorer 9 nothing happens (it just shows a white screen).
I've added the permissions for the location to the 'Global Security Settings' tab of the Flash settings manager (on the Macromedia website). I've also checked in the IE9 settings to make sure that it allows GPU rendering.
Has anyone encountered anything similar or have any suggestions as to why it might be blocked in IE9?
Thanks in advance.
My gut feeling is that you don't have the latest Flash Player for IE, but do have it for Chrome/FF since they're 2 different versions. The swf probably doesn't even load up because of the Flash Player requirement.
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.
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.
I'm using Mobile Safari's cache manifest file to store a multi-page data entry application that is run on an iPod Touch (version 3.1.3) in offline mode. The application writes to the client-side database by way of the persistence.js ORM. This all works fine.
However, I run into the occasional, extremely hard to reproduce problem whereby Safari just seems to forget that the pages are cached. When this happens, the "Cannot Open Page" alert appears, which is the same one that comes up when you attempt to visit a non-cached website with the wi-fi turned off. The only way that I've found to fix this is to reconnect to a wireless signal and visit the site while online, which seems to set the cache straight. This is easy to do when you're in the office, but not so easy to do out in the field.
I'm not trying to reference anything outside of the cached resources, and I've verified that the application is cached by running through the entire site while disconnected, sometimes successfully for days on end. I feel like there's a bug in the OS that messes with the validity of the cache. I'm not necessarily looking for a solution to the problem (but that would be nice), but rather just some confirmation that others have encountered this problem.
Using a cache manifest and lot of troubleshooting, I am able to reliably cache an entire application; Do note that this is a single page app with only a few separate file resources.
As a further enhancement, I have been trying to modify the DOM based on
window.applicationCache status
to inform the user about updates, ie:
tap here to apply update
If that were possible, I could swap the cache
window.applicationCache.swapCache();
Which would allow me to swap in the updated cache and then restart the page to provide a streamlined update mechanism.
Potentially even more streamlined than apps from the apple store.
I suspect that the applicationCache API was hamstrung by Apple to hinder web apps for this very reason. Having said that, I believe the level of support for "html5" APIs on mobile devices is among the most robust in apple's safari.
Following are a few problems I have noticed so far, in no particular order. Please note that this is not a comprehensive list of bugs.
I never get an 'updateready' event; this alert line never runs:
window.applicationCache.addEventListener('updateready', function(e) {
alert('updateready event status=' + window.applicationCache.status );
}, false);
I can not manually check for updates. The following code gives me an exception
try{
window.applicationCache.update();
}catch (err){
alert('exception:\n' + err);
}
It seems that as soon as I start to interact with the cache state at all, the caching stops working. The bugs are fiendishly elusive; pinning down & isolating any one issue can take a lot of time, especially since all this code runs flawlessly on other browsers (chrome).
Now here's a good one:
I suspect that if you pin an app to your home screen, iCloud "backs up" resources and restores them after you run the app for the first time from the home screen. To avoid this issue, you may sometimes have to rename files. I have proven that apple makes discrete backups of obsolete components by
removing them entirely from my app server
deleting the pinned web apps from home screen
clearing all the caches
opening the app url in safari
verify that its the newest version
pin to home
verify that the pinned app the newest version
close it
run again - and its back to the old one, no longer on your server.
Finally, if you run the pinned app while the phone is in airplane mode, iCloud will not be able to restore the obsolete files. This proves that it's coming from over the air.