Flex creationComplete() not executing for certain machines - apache-flex

I have a creationComplete="myMethod(event)" in my s:Application, and it runs fine on my 3 flex (Flash Builder 4) development machines. However it is not working on the 2 end user machines I tried it on today!
It is not executing the creationComplete at all, but it is running the application and it seems like all the other code is running fine - with the exception of possibly some other creationComplete code for other components in the app.
On my machines I have tested it under IE 8 and 9, FireFox and Chrome - on all 3 machines.
On these two machines it has the problem on both IE 7 and IE 8. I even installed FireFox new and it also has the issue. After installing the latest flash player and deleting all browser history/cookies it still has the problem.
What might cause the creationComplete to not execute?
Update:
I tried using initialize() and no difference.
However, I believe I found the line of code causing the problem:
var isDebug:Boolean = new Error().getStackTrace().search(/:[0-9]+\]$/m) > -1;
If I comment that out, it works fine. Why? I need that to know if my app is running in development/debug mode or on an end users machine.

It appears (I haven't tested this myself) that you are unable to get the stackTrace of an error in non-debug mode?
That's my assumption from your description of the problem. If this is the case, you could just check if getStackTrace() != null.
EDIT: Confirmed, getStackTrace() returns null in a non-debug environment

Maybe this line throws an exception (that'd be funny, wouldn't it ? ) that you can't catch when in non-debug mode...
Have you tried this :
import flash.system.Capabilities;
[...]
var isDebug:Boolean = Capabilities.isDebugger;

Related

Error: "command line driver for internet explorer has stopped working " when trying to destroy the driver in selenium

When running automation tests with selenium, I have been getting this error routinely, but not always, after a test passes. After a pass, it tries to destroy the driver but stalls, and this is not acceptable when running many tests back to back. Seems to happen in tests that switch the iframe often, but I cannot figure out a solution. I tried switching to defaultcontent, which I saw as a fix somewhere else, and it does not work. I am running windows 7 and internet explorer 10, but the issue persists in XP Mode on IE 8 as well.
IE Driver 2.32.3.0
It fails when:
if (driver != null)
{
Driver.Quit();
driver = null;
}
The issue also seems to happen after I use a foreach loop through a table that has 60+ rows. Perhaps it is just a memory issue.
I clicked debug on the error and got this in a new instance of visual studio:
Unhandled exception at 0x771a15de in IEDriverServer.exe: 0xC00000FD: Stack overflow.
CONFIRMED: The issue does not occur on IE driver 2.34

Phonegap-Xcode4-AppDelegate

ok, so I am running this phone gap app in Xcode4. It finally runs fine in an iPad simulator. I was even able to make it work in a real iPad device. Then after couple of times downloading the code from Xcode to iPad, it started giving me this error:
int retVal = UIApplicationMain(argc, argv, nil, #"AppDelegate");
The app just gets stuck there. I am new to this and really need help with this.
You may be having an issue with the linked Phonegap files. Try doing a clean and then a run build.
Unfortunately, when the app fails on the Main line it doesn't help to debug the error any. Check the console and try hitting the continue button to see if it throws a better error.

Can't debug ASP.NET in VS2005 won't stop at break point

I have an puzzling problem. I have a new ASP.NET web application in VS2005 that runs fairly well, but I am having a problem and would like to set a break point to see what is going on. I have compiled the project in Debug mode. I have debug=true set in the web.config. But it appears that the IDE is not attaching to the process at all. Have I overlooked something? I am using the development server and not IIS. This has never been a problem in the past, but is this time.
Have I overlooked anything? Thanks for any help.
Rob
I had this issue a while back with VS2005. I don't remember where I got the following instructions from (copied them to a file which I'm now copying to you) but doing the following steps worked for me. It has something to do with IE8 attaching itself to multiple processes and messing up the debugger. Word of warning, this has you editing the registry, so use at your own risk / take all your normal precautions, etc.
Open RegEdit
Go to HKEY_LOCALMACHINE -> SOFTWARE -> Microsoft -> Internet
Explorer -> Main
Add a dword under this key called TabProcGrowth
Set TabProcGrowth to 0
If you run into the same problem on
Vista or newer, you will also need to
turn off protected mode.
Please note also that I was/am running XP at the time, so I did not have to use the "Vista or newer" clause there. No idea if that has any adverse effects either.
Sorry if I am stating the obvious, but you need to Start Debugging <F5> rather than just running the executable after compiling. Are you doing this?
If you don't hit the breakpoint, you are either not debugging (F5) or your code isn't reached at all. If you want to know which of the two is happening you can throw an exception right at the code where your breakpoint is. If your application is failing at the exception, you know you are not running it with the debugger. If it doesn't fail at the exception you are simply not reaching that piece of code and you will have to look harder for which code you are actually running.
throw new Exception("if I see this exception, I am not running the debugger");
Or maybe you are running two instances of the development server. I've had that sometimes. Look in the Windows system tray for the icon. If you see two (or more) you can right click to stop them and restart debugging.

Severe Flex issues

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.

Flex Builder 3 debugging trace output

I have installed Flex Builder 3 and Flash Player 10 on my machine.
I don't know where the trace output goes because I just don't see it (I tried debug and output windows).
Also the breakpoints don't hit.
Salut Omule :)
If you press the Debug Icon(the bug thingy) or go to Run > Debug you should go to the Debugging perspective.
If might be handy to install the Flash Tracer plugin for Firefox to see your traces from the browser.
First you need to make sure you have the Debug version of Flash Player 10. You can do that by checking is Debugging is true using this test.
You can view traced messages in the console (Menubar - Window - Console).
But since you said that breakpoints are not hit, I guess the problem is somewhere else. Make sure that you are debugging instead of running the app (select Debug from the Run menu or just hit F11 while at the corresponding mxml file).
If that doesn't help, and if you are on Firefox, try uninstalling the last addon that you installed. Some addons (including older versions of google toolbar and adblock plus) have known to block swfs from connecting to the flex builder's debugger.

Resources