Actionscript 3 - Disadvantages To Release Flash Application Which Was Compiled In Debug Mode?
Sep 30, 2011
I want to release my flash application not in release mode but in debug mode to see result of trace() after releasing the app.
I don't care that debug mode makes processing speed little slow.Except for processing speed, are there disadvantages to release flash application which was compiled in debug mode?Is it possible that the app throws exception or Flash Players of the app's users crash due to debug mode?
I have a set of users who run my application in non debug mode. Off late they have been reporting lot of issues. But I am not able to debug as there is no log file.Is it possuible in flex 3 to do logging in a file without running in debug version. I understand trace only works if we run application in debug version.
When I first downloaded Flash CS3 Professional, I was able to enter an exceedingly useful debug mode by compiling using ctrl+shift+enter instead of ctrl+enter. I could toggle break points, step in, step over and view values stored in variables at a whim.
I must have accidentally toggled some option somewhere, because this interface no longer shows up. Instead, the only extra interface I get is the output menu with the following text "Attemping to launch and connect to Player using URL <file path> [SWF] <file path> - 71984 bytes after decompression" and while the swf does halt if the as3 code reaches a break point, it doesn't tell me which break point nor give me any options to progress the flow (not even through the pull down menu I have to utilize in order to end the so called debug session).
I have firefox 3.6.15 with flash debug version 10.3. whenever an error occurs a popups comes up with the error and a stack trace but it does not line numbers of each leaf in the stack trace which makes it more difficult to debug. how to configure it to actually show line numbers ?
I think it may relate to how I compile my flash application. (i think!) i use eclipse FDT 4.2 to compile and i added the following compiler flags: -debug=true -compiler.verbose-stacktraces i think these parameters should be enough but I may be wrong.
I have some ActionScript3 code that for some reason only crashes in a stack overflow when compiled for 'Release' mode. The method it crashes in doesn't call any other function and does therefore not recurse in any way.The weird thing is that when compiled in 'Debug' mode it works perfectly.The 'Release' mode also starts working if I enable 'Verbose stack traces' in the compiler options.
Edit: Here is the stack trace:
Stacktrace: VerifyError: Error #1023: Stack overflow occurred. at Extensions::CRunObjectSelection/filterNonQualifierObjects() at Extensions::CRunObjectSelection/filterObjects()[code].....
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 upsloose all event catchingWeird positioning of a buttonI 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.
I am working on a feature for an application that requires Flex 4 functionality. Due to some migration issues of the application from Flex 3.5 to 4.0, I have decided to implement this feature as a module that is compiled with Flex 4.0. The theory is that the application would remain compiled in Flex 3.5 and load the module when it needs it.[code]
I have developed an site in flash doesnt throw any error in Flash IDE debug mode, But when I launch this in web browser it throws error.
Disadvantage of showing error in browser window is that it wont show the line number of the error. Is there any otherway to get the line number of error, when running in the browser.
I've built a simple application in Flex Builder 3 with some trace() calls. It's an "ActionScript Project", no MXML or AIR involved. I don't run the app from within Eclipse, I just open the generated html file with Firefox.
I'm using the Flash Player 10 Debug version. I've correctly set mm.cnf to log trace output, following the official instructions. A flashlog.txt file is generate in the appropriate location.
Despite all that, trace output is not shown in the log file. What am I doing wrong?
(I suspect it's a compiler option, but I can find no such option in the project options in FlexBuilder)
(If I do run the app from Eclipse, by pressing F11, I can see trace output but only inside Eclipse, not in the log file)
Is there any way to debug fullscreen mode? I Ctrl+enter and I see the swf but the fullscreen button never works, like when I forgot the allowFullScreen param in my HTML code.Do I have to add some parameter to the CS5 properties?
when I export a bin-release of my application, all my text fields have a different line spacing from that of the bin-debug version. How is this even possible?
Has anyone else come across something like this before?
I want to have separate output directories for debug and release builds. However, I don't see any proper option in FlashDevelop. Is this thing achievable, and if so, how to do this? If not, how to determine if current build is compiled as debug or release?
SWF caching has bit me quite a few times now. I want to debug in the browser because that's where the swf will run. But Firefox sometimes caches local files incorrectly, thinking that it has the latest version when it doesn't. This can cause a huge headache with debugging, causing me to wonder why something doesn't work no matter what I do.
The workaround I use is to create a custom html file in bin-debug that loads the swf with a random string appended so Firefox never caches it. This works fine, but every time I start a new project, I need to remember to do this.
I've had no such problem like this until today. Basically when i try and drag an object from photoshop to the stage in flash, everything looks great on the stage and usualy everything looks fine in the test / debug mode. But suddenly i've come up against a very anoying problem. Everything looks great on the stage, but as soon as I go to test the movie, the image quality of whatever it is I have imported goes terrible. Like its been compressed to less than 10kb!The image looks fine on the stage but the problem accurs when I try to test to movie.I have tried importing different size images, not transforming the images in flash, making sure all the settings (I know of) are on high.
A client is running into some problems with an application, and cannot install the debug flash player, meaning debugging is very hard. Does anyone know of a way to display the system's trace messages in a textfield on the stage for example? This way I could find the error by having it trace to their screen. I suppose a workaround would be to try/catch all over the application but that is not ideal and very cumbersome.
i like to know that there is way to remove all data after unload swf .Calling Loader.unloadAndStop(); remove content and loaded bytes , but loaded classes stays in application domain .If i load it to separated new ApplicationDomain , gc is going to collect them after unload and remove all references ?
I compiled a simple AS3 project using Flex 3.5 (also tried Flex 4.1) to create a small swf which draws a simple red square on screen. Nothing too complex that requires special flashplayer support (see code below)
package { import flash.display.Sprite; /**
[Code]....
and tried to load it into a AS2 swf I have compiled using Flash CS4. But that just didn't work. I don't get any errors when loading and the AS2 swf can load any swf, either compiled in AS2 or AS3 by Flash.
I have an html file which I want to use every time I debug my flex application. I don't want an new html file to be generated every time. How can I do this?
set some filters on the bitmap after it has been loaded.During development (Debug mode), everything worked and the even has been fired just fine.But now I switched to Release mode and the complete event doesn't fire anymore.To load the image, I set the source property of the image to an URL that points to a PNG image. That does still work in release mode, so the image appears correctly.It's just that the "complete" event doesn't fire, no matter what I try.
I'm currently trying to implement an automated bug reporter for a Flex application, and would like to return error messages to a server along with the function/line number that caused the error. Essentially, I'm trying to get the getStackTrace() information without going into debug mode, because most users of the app aren't likely to have the debug version of flash player.My current method is using the UncaughtErrorEvent handler to catch errors that occur within the app, but the error message only returns the type of error that has occurred, and not the location (which means it's useless). I have tried implementing getStackTrace() myself using a function name-grabber such as [code]
but that will only work because of arguments.callee, and so won't go through multiple levels of function calls (it would never get above my error event listener).Anyone have any ideas on how to get informative error messages through the global error event handler? There seems to be some misunderstanding. I'm explicitly avoiding getStackTrace() because it returns 'null' when not in debug mode.
I'm an application developer, and my standard usage of Flash is as follows: I'm creating an executable application, which contains a ShockwaveFlash object instance, which in turn is displaying a Flash Movie Clip - also created by myself. The executable application and the contained Flash clip are communicating via the ActionScript ExternalInterface (using XML strings) and the FSCommand.
I'd like to be able to debug the ActionScript code of the Flash file while I'm running/debugging my executable application. For that, I need to be able to start a remote debugging session from the Flash object running inside my executable. Problem is, I did not find any way of doing this.
When I publish the Flash SWF file with "permit debugging" checked, I'm able to start a remote debugging session when I'm displaying the file in a player or a browser (the "debugging" option is shown at the right-click menu of the Flash object), but I'm not able to do the same with the object inside my executable (the "debugging" option doesn't exist on the menu).
Environment Details: The executable application is using the ShockwaveFlash COM file to create the ShockwaveFlash object. The executable application is created using VB.NET, Visual Studio 2008, .NET 3.5. The Flash SWF file is created using Adobe Flash Professional CS4. I'm developing under Windows XP (SP3).
I have a custom cursor movieClip that changes depending on which side of the screen its on in my Flash application. This works fine, and even when the Flash test window is resized. However when going to fullscreen mode, it stops working. This code is called every frame, so shouldnt the stageWidth/stageHeight adjust accordingly when going to fullScreen mode?
I have an AIR application which uses RemoteObject to comunicate with remote services in PHP (using Zend AMF). The application works great, but I can't debug the PHP side (the Flex debugger works fine, the PHP side is the problem). I'm using Flash Builder 4.5 for PHP, when I write a Web Application (not AIR), I can choose to debug the application as "Web (PHP) Application", and the breakpoints in the PHP side are working as expected. But I can't see any similar option for Desktop Applications (AIR). Does somebody know if it's possible (and how) to debug the PHP side in an AIR application?
I have a swf that I need to attach the flex builder debugger to. I have full access to the source code, and can make a debug build of this swf.
However, this swf is being loaded by a non-debug build of another swf which I don't have source code to, and can't make a debug build with.
I've tried mocking this up with two very simple swfs, and while it works fine when both are debug builds, when the outer swf is a non-debug build, while I can get the debugger to connect, I don't get trace messages, breakpoints don't work, and it seems to lock up the flash app.
I have a flex app using the 4.5.1 sdk and AIR 2.7 running on an Android 3.2 tablet. During use, I can get it to crash fairly regularly. It's usually when I'm rapidly scrolling around in a List control. I can't seem to find the cause.
The application will just suddenly close. It happens in both debug and release builds.
When in debug mode, it just disconnects from the debugger and doesn't give me any useful information.
I'm at a loss on how to debug this. What are some techniques I can use?
I found the "adb logcat" command. Relevant info from the log below, unfortunately it doesn't mean much to me.
I just took over a clients flex project and I can't get the app to reflect even a simple trace statement. Before I took over, the project was last successfully built using the Flash Builder Beta 2 environment/sdk. I have the latest release version of Flash Builder 4.
Upon importing the project into FB4, I got a ton of errors. Most of them mostly because of the changes made to the sdk from beta2 to release.
Some of the things I corrected:
- mx namespace from [URL]
- video player skinning: a lot of the state names for the video player component had been changed, more required states had been added. also there were other video related component and property names that had to be updated.
But I fixed all that and the application was finally able to compile (although with some warnings mostly of the duplicate variable type)
The only thing now is that whatever change I make to the project doesn't get reflected in the build (debug or release). I changed existing traces, added additional traces. Nothing shows up. I even removed the applicationComplete property in the main.mxml. Everything still ran like nothing changed.
Also I can't seem to debug the app. Whenever I try to debug.. flash builder says.. "Swf Application doesn't contain the required debugging information ... "
