I need to disable flash from showing these error messages when an error occurs. I am completely aware of the error I'm receiving, and it does not cause my application from working correctly. I simply need to disable these messages. Is there a setting in flash or a flex compiler command or something? Thanks, David.
There are a lot of things you can do with your mm.cfg file (google it's usage)
For instance if you put:
SuppressDebuggerExceptionDialogs=1
In there it will prevent the debugger version of flash from popping up error windows in your browser.
No, unfortunately there's no such thing. Though, the errors will not be displayed to users that have the release version of the flash player installed, and not the debugger one.
There's a very hot feature request for the flash player but the implementation seems far from happening: Ability to intercept system error dialogs. There are a lot of comments some heated, some sarcastic but Adobe seems to still ignore this issue.
UPDATE
The feature has since been implemented. Last comment says:
This has been fixed with Flash player 10.1
http://labs.adobe.com/technologies/flashplayer10/features.html
Global error handler The new global error handler enables developers
to write a single handler to process all runtime errors that were not
part of a try/catch statement. Improve application reliability and
user experience by catching and handling unexpected runtime errors and
present custom error messages. When using the global error handler in
a SWF running in the debug player, error pop-ups will not be shown.
Related
I am using JxBrowser (6.23.1) on windows 10 and using the 64-bit library. however, when i startup the demo application I get the following Log message.
SEVERE: [0528/084716.632:ERROR:browser_process_stub.cpp(279)] NOT IMPLEMENTED
Can anyone shed light on this and whether this is an issue?
I have tried to find anything in relation to above error code, but did not find anything.
The browser_process_stub.cpp(279)] NOT IMPLEMENTED message means that Chromium engine tries to get access to the specific code of JxBrowser which is not implemented at the moment due to the fact that this functionality is not supported by JxBrowser at the moment. This method does not affect the existing JxBrowser functionality, so you can safely ignore this error message.
https://i.stack.imgur.com/pFR3B.png
Only one error：
08:22:50 FATAL: [0325/202250.082:ERROR:gpu_process_transport_factory.cc(1018)] Lost UI shared context.
It can happen that the Chromium engine can lose UI shared context in some cases. Usually, Chromium will restore the context and continue rendering. In that case, something happened that prevented Chromium from restoring the context.
As a workaround, you can try using accelerated lightweight rendering. It is faster than the usual lightweight rendering and does not use GPU. As a downside, the WebGL functionality will be disabled.
Could you please try enabling the full Chromium logs, reproduce the issue and send them to me? You can enable Chromium logs with the following Chromium switches: --enable-logging --v=1. The output will be saved to the file chrome_debug.log in Chrome's user data directory. Also, JxBrowser logs could be helpful too. You can find how to enable JxBrowser logs using the following link: Logging
In addition, the message you got, can be produced by the Chromium engine when the --disable-gpu or --disable-gpu-compositiong switch is passed to it.
A Qt project gives a number of errors - that I do not actually consider errors I think:
Some examples:
Fontconfig error: "/etc/fonts/conf.d/65-khmer.conf", line 32: out of memory
// ?
QGraphicsItem::ungrabMouse: not a mouse grabber
// i think happens when the mouse grab didn't quite happen, user moved too fast...
A few others
the first one seems it has an answer here https://askubuntu.com/questions/421891/fontconfig-error-out-of-memory
So I cannot fix it through software, the user must fix it... since it is system dependent...
Even built in release, these errors will still show up on command line... Since they do not cause the application to behave abnormally, I don't think the user should see them.
How can I build/deploy the application without these errors showing ?
ideally of course there would be no errors in a deployed application, but I don't know what I can do about those types of errors...
It is possible to redirect a stream (in this case stderr) after the fact using
freopen("/dev/null", "w", stderr);
Just place this in your main before any other code runs and you should be good. Keep in mind that this might need more work on Windows.
If the error message is posted through the Qt Message infrastructure (qDebug etc.) you can set a new message handler through the function qInstallMsgHandler.
I'm working with a Flex 4 application (MXML and ActionScript front-end using BlazeDS and Java back-end) and I am trying to find the origin of an error.
The user sometimes (maybe once a week) gets a pop-up window with "RPC Error" in their web browser. If they retry the operation, they get the same error. Restarting the browser or maybe just reloading the page makes the error go away. Looking in the server log, I don't see any error on the server side. How can I figure out the cause of the RPC error? Can I configure some setting in the browser or Flash player to get additional info?
Thanks for any ideas. I've searched the web & some forums including SO but I've come up empty-handed.
Edit: in this case it appears the problem was loss of the network connection (user was connected via cell modem). I'm still interested in any ideas about how to troubleshoot this problem.
I like to do my development in Firefox and using Firebug as a console. When the Flex app starts, open up Firebug and look at the Net tab. It will bring up all the RPC calls made while Flex is initializing, which can be very useful for these kinds of bugs.
I have this very strange problem on a big flex app where it would run fine with the debug swf if the user has debug flash installed but will have some disparities for people with standard version of flash.
These disparities include:
No pop ups
loose all event catching
Weird positioning of a button
I read somewhere that updatedisplaylist was handled differently ?
For now i will try the export release way instead of the bin-debug swf, and to go back in the commits to see what was the turning point.
Any similar experiences ?
I've been using Flex for a long time and have never heard of any problems like these being related to using the debug vs standard versions of the Flash player, but I have experienced problems similar to what you're experiencing.
When an exception occurs in your application, like attempting to access something in a null class or trying to access element 10 in an array that only has 9, the debug player will pop up a window stating that an exception has occurred and give you a stack trace, even if you're not actively debugging the app. The standard player does not, so the user will have no way of knowing that something went wrong.
In my experience after an uncaught exception occurs it can make all running code from that point on very unstable, causing all of the problems you list and more.
I doubt your problem has anything to do with the two different players beyond the standard one not giving you any feedback about the state of your app.