I am experiencing an issue related to the displaying of any content within the JxBrowser, but only for 1 specific client PC.
The JxBrowser seems to correctly process the content that is sort of present, because if I click on an area where I know there is a link, the new page is opened (but not rendered too).
The "pages are not displayed" means that the content is completely white. Furthemore, the pointer is repetitively blinking between the normal arrow icon and the waiting circle, as something is going on in the background every about 1 sec.
A previous version of the application that embeds the JxBrowser doesn't produce the same problem.
Later on, I have also upgraded the JxBrowser version from the 6.23 to 6.24.3, but this did not solve.
Deleting any caches produced by the presence of the JxBrowser on the PC did not solve either.
What should I investigate to try and address this situation?
First of all, please note that JxBrowser 6 is no longer supported and it's a very old version based on Chromium 69. A lot of popular websites might not work properly in this Chromium version.
If the issue is reproducible only in a specific environment, then it's probably an environment-specific issue. If we are talking about rendering, then usually Chromium cannot render content when there's an issue with GPU drivers and the rendering mode (heavyweight or lightweight).
From our practice, disabling GPU very often helps in such cases. Please try passing the --disable-gpu switch and see if it helps. If it doesn't help, then the issue is probably in something else and additional research or even access to this environment is required. But again JxBrowser 6 is no longer supported.
As an option you can try JxBrowser 7 and see if it helps, but it's not that easy because this version has a new API which is not backward-compatible with the previous version.
Related
The problem is awkward because everything worked fine. I opened the laptop and somehow it crashed and didn't corresponding to any commands so I had to turn it off. After I started again and after building my project(just in case anything was wrong) and opened my web page I realized that bootstrap is not working at all, and I can't figure out why because I didn't do anything. I tried to install a lower version and didn't worked and after I install the latest stable version and not didn't worked again. If you need any source code let me know and I will edit my post. I will put a picture below which describes what I am talking about(or at least I hope so).
It has the appearance of running in IE Compatibility mode, even though you're on Chrome. Try refreshing your cache (Control+Shift+Delete), rebuilding your project, and using a different browser.
I've run in to this issue before and refreshing the cache usually does the trick.
I've encountered a problem that has completely stumped me, and unfortunately I don't really know how to go about trying to diagnose the problem either.
Basically I have a client who's website loads and then just hangs using FF25 on OSX 10.9, it only happens on this website, no other website. I've heard of problems before with this combination that resulted in people having to disable their plugins, so I told them to disable plugins/clear cache and get back to me. They've done this but to no avail. I've also read that it may be a CSS issue with fonts(no idea why it would be).
I've been all over the Mozilla forums but no one has raised such a query that replicated my problem on just a single website. Here probably isn't the best place to raise such an issue, but I'm sure someone must of encountered the same problem and resolved it some way or another.
Thanks.
There are memory allocation issues that appeared in FF25 (certainly on Windows; FF26 and 27 seem much "better"). These issues seem to be js/heap related. See, for example, https://bugzilla.mozilla.org/show_bug.cgi?id=936784
You can investigate yourself how the browser is using memory by browsing to about:memory in a new tab.
It seems a little odd that this does not happen if the browser console is open - and even after closing the browser console and refreshing the page it continues to load fine.
What might be happening (or not happening) with the console open which would prevent this error from happening?
We've tested it on 10.7, 10.8 and 10.9 and all three have this problem, but only on Firefox 25.
In response to Codacoder, that bug appears to be related to leaving Firefox unattended and an ongoing incremental memory usage issue - this happens the second the page loads, rendering the browser un-usable and requiring a manual kill of the browser. Not sure if it's the same issue?
Ruth
I'm a C++ programmer, but I'm a newbie in Flex. I'm developing a Flex 3 application for a social network using the FlashDevelop. For debugging I'm using the stand-alone FlashPlayer (10.3 debug) downloaded from Adobe. The application is a simple audio player which shows artist/album images.
The application worked properly on both local computer and remote server until I made some layout changes in Main.mxml. I added some HBoxes and changed Image placement. After that the application still works on my local computer, but it doesn't work properly after I upload it to a server.
Application buttons are not highlighted on over/out/click events, images loaded from the Internet are not displayed, text changed dynamically is not displayed, but when I click buttons a sound file is loaded from the internet and starts playing. It looks like some events which are responsible for components displaying are not dispatched, because some part of functionality not related to displaying still works.
To make sure that this is not a server problem, I rolled back to the previous revision. All works fine.
I suppose that this is a known issue, but I have no idea what is the reason.
Could anyone please help me to resolve the issue?
Thanks.
UDP: I observed the issue in IE and FF, I didn't test Opera and Chrome.
Are you tying to access the pixel data of the images in the new version? If so, that might be the problem, as pixel data for loaded images is not (always) accessible so that might throw a security error, which in turns breaks the rest of the interface.
Also, did you try running the remote version in the debugger? If so, is there any exception being thrown?
And no, it's not a known issue, it's the kind of annoying and hard to debug error that you sometime get when using the Flex SDK.
I'm really confused about this problem, and I'm pretty new to Flex. Basically, anything I try to build with mxmlc fails to run now, giving me the above three errors depending on what I do. It was working 30 minutes ago, I've been spending that time trying to figure out what has changed. I redownloaded the Flex SDK, cleared my assetcache, have cleared Firefox's cache. (I'm using Linux.) Even if I compile with -static-link-runtime-shared-libraries=false, since it seems like #2048 is a RSL problem, it still refuses to run.
Another strange thing, if I keep
<policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
<rsl-url>textLayout_1.0.0.595.swz</rsl-url>
in my flex-config file, then firebug tells me that my swf file is trying to access a copy of that in the app's folder, giving error 2032. And if I stick the one I have in frameworks/rsls/ then it gives me error 2046. I don't know how it could not be properly signed, unless Adobe magically changed a signature and didn't update their flex SDK.
Any help will be appreciated.
On Linux I sometimes get these errors. It seems that the Flash Player cache sometimes get corrupt. When I delete the asset cache I then have to reboot in order for things to work again. Not fun. I filed a bug a while back but without having a consistent way to recreate the corruption I can't help them reproduce the issue. Please file a bug if you have a consistent way to reproduce the issue.
Okay, more weirdness. Simply restarting Firefox seems to have allowed the applications to work again. Facepalm
Today I experienced that problem in one browser but not in other. I have Ubuntu 10.04 and in google chrome 6 I received error #2046. In FireFox and Opera everything worked well. The problem has been solved when I reloaded my chrome browser.
This is an off the cuff answer, maybe not correct, but I encountered a similar issue recently and discovered that the issue was that our app was not compiling the Flex libraries into the SWF. Because of this, in some cases the Flash player would for whatever reason decide that the cached Flex libraries (.swz files, aka Runtime Shared Libraries or RSLs) were incorrect versions and so would refuse to load them, giving similar errors without explanation. These cached libraries are separate from the browser cache, they are cached for the whole OS. You could try explicitly linking the Flex libraries into your SWF to troubleshoot the problem. If it goes away, that's a useful clue.
I seem to be having difficulties getting the trace function to output anything to the console in either Eclipse with the Flex Plug-in, Flex Builder, or even FlexBeans (the Netbeans plug-in for Flex). I have removed and then reinstalled the Flash player 10 debugger version for both Firefox and IE, rebooting after uninstalling them and then after re-installing them. I have removed all old versions of Java and updated to the most recent version.
mm.cfg is configured correctly to allow the trace actions to appear in flashlog.txt
I tried removing the Flex Plug-in for eclipse to re-install, and now that I re-installed, I cannot create new Flex projects. I would rather not uninstall Flex Builder for fear that it will also behave strangely.
ANY ideas would be useful. Ideally, I need the plug-in to work, but any way I could get tracing to output to the console (in ANY IDE) would be better than what I have now.
I'm not sure what you mean by "Flash debugger for both Firefox and IE"; are you referring the debugger versions of the Flash Player available here?
http://www.adobe.com/support/flashplayer/downloads.html
If not, you definitely need those installed in order to be able to write trace() output to the IDE console.
I'm almost positive that this is not the issue, but it has confused me on a couple of occasions.
The Debug Application (as opposed to Run Application) keyboard command is different on Mac and PC. I use both and have gotten them mixed up, which results in my Running when I think I am Debugging, which of course leads to know trace outputs in the console.
Most likely not it, but doesn't hurt to mention it (I hope) :)
-- Evan
How are you testing the debugger? Have you tried going somewhere like with lots of ads that generally still have their traces in? Or are you just testing it with your own swfs? Have you installed the projector debug version? How is eclipse / flex configured to launch test swfs? Is it in the browser, or in the stand alone player? Do you have any weird mxmlc settings?
I assume you've followed all these instructions?
http://kb2.adobe.com/cps/193/tn_19323.html
This is actually a combination of issues. The minor issue was that one application was interfering with Flex Builder Plug-in. The major issue had to do with a setting which had gotten changed on the Flash debugger.
If you right-click the running SWF and then click Debugger, you can (essencially) tell the VM where to listen for trace actions. This had been set to another machine on the network, and not my local machine. As soon as that was switched, everything restored itself.