CS3 Publish Crash Bug?
|
|
Thread rating:  |
dbchen - 13 Oct 2007 18:49 GMT After a couple months of using Flash CS3, it suddenly crashes whenever I try to open FLA files or attempt to test or publish SWFs. Terrible timing since I have a client barking at me for updates. I'm running on XP SP2 and I haven't installed any new programs.
Initially I wasn't able to open FLAs without crashing, but was able to open smaller FLAs before larger ones (20MB) and the larger one would then open fine. But now when I try to publish or test SWFs, Flash just crashes. I've never had this happen to me in any previous versions. Coming from Adobe, this is extremely surprising to me as all of their other programs have been very stable.
I'm wondering if Adobe's Dev Team is aware of this bug and/or if we should be expecting a patch release soon?
redsox05 - 23 Oct 2007 16:20 GMT I'm having the same problem and nobody seems to have an answer.
ChrisElmes - 23 Oct 2007 20:05 GMT Report the bug, just in case they are not aware of it - as the the "important note" at the bottom of the screen says, this forum is not an official customer support channel. So just asking the question here doesn't mean that now they know about the problem!
Use the bug reporting page : http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
BSpero - 29 Oct 2007 21:38 GMT Hey guys, I just had a pretty long conversation with Adobe support and may have an insight. I have a separate drive that I keep all my projects on and that I work off of. It's not a network drive, just a second internal one. When I installed CS3 and began working on some of my stuff, Flash would crash intermittently, as well as when I tried to preview and publish files. After working at it for a long time, we figured out that if I had content on my root drive, then I would not get the errors and crashes, but when it lived on my projects drive, then it would continue to plague me. So, the Flash engineer told me that they recommend keeping the project that you're working on on the same drive that Flash is installed on. I proceeded to tell her how foolish I thought that advice was, and foolish that the program was acting that way, but she insisted that was the only way to get around this. Of course I have no choice, since I need to be able to work. There were some other odd behaviors, like crashes on projects that had originated in Flash 8, but not on native CS3 projects, but it basically came down to where the file lived. SO, I guess they know about this problem, but it doesn't seem like good practice to keep your projects on your system drive. For now I am copying them over when I need to work, and then putting them back on the projects drive when I am done. This is on a PC running Windows XP Pro. Maybe this sheds some light on your problem?
O,V - 09 Nov 2007 20:25 GMT I also had been using Flash (CS3) for some time with no problems. Just last week when I went to publish a fla to swf, Flash crashed with an error window wanting me to "send error report". I've tried to open the file in an older version of Flash with no problems but now I cannot publish or preview my files using Flash CS3 without it crashing. I only have one hard drive and am running Windows XP. I uninstalled and reinstalled CS3 and there's no difference. Please, can anyone suggest a patch or something to fix this problem?
Twice21 - 30 Nov 2007 01:50 GMT I have a (similar, yet different) problem. As stated here many times, I have been using CS3 for quite a while. Now, working on a DEADLINE CRUNCH FOR A CLIENT, a project will not publish. No error messages; no 'crash' per se. When I choose to PUBLISH, I get the familiar progress bar. But at about 20% - 25% the dialot disappears. That's it. No files are written (SWF, HTML, EXE) but there is no error. This particular project has been growing and I do periodic Publishing to preview it and to share progress with the client. In an effort to troubleshoot I: a. Removed all but one scene b. reduced the length of the timeline c. deleted unused resources
I need help FAST.
moose2007 - 30 Nov 2007 23:33 GMT I am having the same problem- I am unable to publish files that I created within the last few weeks. If I try to re-open the same file after the crash, Flash will crash again. I have found that I am able to edit and save the files if I open an old file (created before the problem started) and then open the file I need. However, if the file won't publish I'm doing this work for nothing. I opened a support ticket with Adobe, hopefully they will have some insight. I have been using CS3 since early summer on a WinXP SP2 machine, and I only have one drive locally. I do not use Flash remotely. They recommended deleting and having Flash recreate the Configuration folder, but that did nothing. Testing it, I realized that it was any file at all- I even created a file with one frame with a colored box on it- nothing else. That crashed too. So it's not the content.
I also experienced a problem with editing Flash files created in Flash 8, but I don't have a lot of files from that version.
johnkerry - 05 Dec 2007 00:32 GMT I have the exact problem. Has anyone found a workaround or fix for this?
No error messages; no 'crash' per se. When I choose to PUBLISH, I get the familiar progress bar. But at about 20% - 25% the dialot disappears. That's it. No files are written (SWF, HTML, EXE) but there is no error.
Broax - 02 Sep 2008 18:58 GMT I'm have your exact problem I need to finish the project as the deadline is tomorrow and I needed to fix a small problem with music loop and finish a scene! Please tell me you've got the solution! please try to help me!! :(:(:(
>I have a (similar, yet different) problem. > As stated here many times, I have been using CS3 for quite a while. Now, [quoted text clipped - 11 lines] > > I need help FAST. Walter Elias - 05 Dec 2007 01:37 GMT Can others please report whether they experience this? I want to know how common the problem is. I use Flash heavily since 2000, but have resisted buying CS3. I was considering finally buying it next week, but am scared off by these comments. I rely too much on quick turnaround work for my clients and can't afford crashes and bugs like this.
digi-sign - 05 Dec 2007 15:04 GMT Hi Everyone, I appear to be having problems with CS3 crashing also. It seems that every time I try to animate a line CS3 crashes. What I have been doing is making a small line, adding another keyframe and then growing the line and creating a shape tween. The idea is to make it seem like the line is drawing across.
I am wondering, is it just me and I am doing it the wrong way or is it a bug in flash. I just can't believe that such a simple thing would make it crash...I have tried various different ways of animating this line, but it has crashed around 12 times now!
I am using flash on Vista, I can give you the specs if it is necessary, but its only on a new laptop I bought less than 6 months ago. Appreciate any help on the matter.
O,V - 05 Dec 2007 15:50 GMT I was editing a file I created in an earlier version of Flash (MX) and went to save it as the default fla CS3 format but then couldn't publish without a crash in CS3. I got around this 2 ways, yet both are not ideal. First, I went back to using Flash MX and was able to edit and publish successfully. Second, I opened the MX created flash file in CS3, edited, published and then carefully saved it as a Flash 8 document, not the default CS3 format.
Tom Pesto - 05 Dec 2007 18:33 GMT maybe you can try renaming the configuration folder for Flash cs3. the configuration folder for Windows XP is in c:/documents and settings/<your username>/local settings/application data/adobe/flash cs3/en/
This helped me once out once. Hope it does the trick.
digi-sign - 06 Dec 2007 15:35 GMT Turns out that my problem was actually to do with the Shape Tween thats I was using, I found an interesting post on someone's blog that suggested that if you delete the history and make sure that the subselection tool isn't selected when scrubbing the timeline, it should no longer crash. Et Voila!
http://www.biteycastle.com/blog/2007/07/bug-hunting.html
BWolfe [ADOBE] - 07 Dec 2007 20:46 GMT I'm watching this thread and will try to make some time to do a little research. Anyone who's crashing on publish should -absolutely- open a support case via http://www.adobe.com/support/flash!!!!
asdfssvdfvdegrv - 04 Jan 2008 00:39 GMT I swear I got the crash after the 9.0.2 update was applied.
My main swf is mostly empty, and writing all of the code via external AS classes. I am using a MacBook Pro, OSX 10.4.11.
My crashes do not happen immediately however; it dumps me out only when I do a Test Movie (publish is fine), and at the stage where my swf is in the process of loading, or begins to load an external file through the URLLoader object (I'm calling various loads to XMLs, PHPs, FLVs, and JPGs).
This happens consistently to two separate projects I am working on, both of which access external files in one form or another.
I have done the delete aso files routine. Not helpful. The crashes are intermittent, though ? you won't know exactly when it will crash, but it will eventually once the swf is left to run within the Flash IDE.
The curious thing is that everything worked without a hitch before the 9.0.115.0 update. Running the swf file via the standalone player (both debug and regular versions) works perfectly, it's only when Test Movie is running that the Flash IDE croaks on me.
After hours of desperate investigation I noticed something: by enabling Omit Trace Actions (i.e. checked) in my publish settings I have not yet had Test Movie crash on me. Yet. So it seems like the traces from the swf are making Flash crash.
Can anyone try this out? I am completely stumped.
asdfssvdfvdegrv - 04 Jan 2008 15:02 GMT unfortunately i stand corrected.
flash eventually crashed with Omit Trace Actions turned on. It took quite a while for it to do so, however. i thought i had it pegged. But once it crashed with the same error, subsequent test movies start to crash at much quicker intervals, i.e. like it was before.
here's the beginning chunk of the error report:
Date/Time: 2008-01-04 09:51:21.192 -0500 OS Version: 10.4.11 (Build 8S2167) Report Version: 4
Command: Adobe Flash CS3 Path: /Applications/Adobe Flash CS3/Adobe Flash CS3.app/Contents/MacOS/Adobe Flash CS3 Parent: WindowServer [77]
Version: 9.0.0.494 (9.0.0)
PID: 1395 Thread: 19
Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_INVALID_ADDRESS (0x0001) at 0xff80149b
Thread 0: 0 libSystem.B.dylib 0x900248c7 semaphore_wait_signal_trap + 7 1 ...ia.Flash Player.authplaylib 0x318de198 0x31514000 + 3973528 2 ...ia.Flash Player.authplaylib 0x3190fa37 ExternalPlayer_Initialize + 112303 3 ...ia.Flash Player.authplaylib 0x3164f23f 0x31514000 + 1290815 4 ...ia.Flash Player.authplaylib 0x315ee98d 0x31514000 + 895373 5 ...ia.Flash Player.authplaylib 0x316f76c6 0x31514000 + 1980102 6 ...ia.Flash Player.authplaylib 0x316fa1ef 0x31514000 + 1991151 7 ...ia.Flash Player.authplaylib 0x316f79f7 0x31514000 + 1980919 8 ...ia.Flash Player.authplaylib 0x316fa1ef 0x31514000 + 1991151 9 ...ia.Flash Player.authplaylib 0x316f79f7 0x31514000 + 1980919 10 ...ia.Flash Player.authplaylib 0x316fa1ef 0x31514000 + 1991151 11 ...ia.Flash Player.authplaylib 0x316f79f7 0x31514000 + 1980919 12 ...ia.Flash Player.authplaylib 0x316fa1ef 0x31514000 + 1991151 13 ...ia.Flash Player.authplaylib 0x316f79f7 0x31514000 + 1980919 14 ...ia.Flash Player.authplaylib 0x316fa1ef 0x31514000 + 1991151 15 ...ia.Flash Player.authplaylib 0x316f79f7 0x31514000 + 1980919 16 ...ia.Flash Player.authplaylib 0x316fa1ef 0x31514000 + 1991151 17 ...ia.Flash Player.authplaylib 0x316f79f7 0x31514000 + 1980919 18 ...ia.Flash Player.authplaylib 0x316fa1ef 0x31514000 + 1991151 19 ...ia.Flash Player.authplaylib 0x316f79f7 0x31514000 + 1980919 20 ...ia.Flash Player.authplaylib 0x3166e2b0 0x31514000 + 1417904 21 ...ia.Flash Player.authplaylib 0x3177c9e8 0x31514000 + 2525672 22 ...ia.Flash Player.authplaylib 0x318f788f ExternalPlayer_Initialize + 13575 23 ...ia.Flash Player.authplaylib 0x3178c83c 0x31514000 + 2590780 24 ...ia.Flash Player.authplaylib 0x318f7f48 ExternalPlayer_Initialize + 15296 25 com.apple.HIToolbox 0x92e1fa4a TimerVector + 31 26 com.apple.CoreFoundation 0x9082d76a CFRunLoopRunSpecific + 3341 27 com.apple.CoreFoundation 0x9082ca56 CFRunLoopRunInMode + 61 28 com.apple.HIToolbox 0x92de7878 RunCurrentEventLoopInMode + 285 29 com.apple.HIToolbox 0x92de6f82 ReceiveNextEventCommon + 385 30 com.apple.HIToolbox 0x92e2fa74 _AcquireNextEvent + 58 31 com.apple.HIToolbox 0x92e2f8bc RunApplicationEventLoop + 150 32 com.adobe.flash-9.0-en_us 0x00816295 0x1000 + 8475285 33 com.adobe.flash-9.0-en_us 0x0071be51 0x1000 + 7450193 34 com.adobe.flash-9.0-en_us 0x0071befc 0x1000 + 7450364 35 com.adobe.flash-9.0-en_us 0x00003162 0x1000 + 8546 36 com.adobe.flash-9.0-en_us 0x00003089 0x1000 + 8329
oh and i forgot to mention something: i tried publishing my projects on the pc, and publish/test movie won't even work now. i just get an immediate crash for that.
is anyone reading this, and have any suggestions?
Walter Elias - 05 Jan 2008 01:27 GMT Yes, I have a suggestion:
Follow Bentley Wolfe's advice in his post above, and make an official report to Adobe with all the details. It is very rare that any Adobe developers actually read this forum. Once you (and everyone else in this thread) make an OFFICIAL report on their bug report form, the problem is officially logged. But if hardly anyone makes an official report, they don't consider it to be a major bug and nothing will be done about it in the short term.
asdfssvdfvdegrv - 05 Jan 2008 01:53 GMT Thanks, I have already sent in a bug report before posting here, but just wanted to know if anyone has come across this matter and managed to fix it.
I hope they find the source of this problem. It is making development impossibly slow.
The only workaround I have for anyone with this same situation is to publish/debug the SWF. The debugger seems like the only place to get trace output within the Flash IDE and not crash, probably because it is using the standalone flash player to launch the SWF.
sgellen - 07 Mar 2008 07:46 GMT I'm also having recent problems with Flash CS3 suddenly crashing whenever I try to publish a FLA files or attempt to view the actionscript in the FLA. I now cannot use Flash CS3 to create and publish any FLA/SWF.
I'm running on XP SP2 and I haven't installed any new programs.
I've never had this happen to me in any previous versions.
I'm wondering if Adobe's Dev Team is aware of this bug and/or if we should be expecting a patch release soon?
Could someone from Adobe please confirm that this problem previously reported by others in the forum is being addressed by Adobe.
lokalhorst - 07 Mar 2008 19:48 GMT since i updated to player 9.0115 it is de facto impossible to preview any .fla within the flash IDE. Each project with a 'complexity' of more than a few classes is going to crash the whole application with an 'authplay.dll error'.
I'm really pissed of by the arrogance and ignorance upon what big big Adobe is handling the customer complaints. I live in germany, and different to US customers, i had to pay 1.276 Dollar ONLY for Flash CS3 (yes it's true) and this crap is buggy like 20$ shareware. For a hardware product which such a 'support' i would ask and get a refund. In the meantime, Adobe is celebrating themselfes in front of a bunch of handselected loyal fans and praising the incredible awesome new features of the upcoming Flash 10. And, yes, you can bet, you will find a lot of the present bugs in Flash 10 too. If you do not like it , go and buy Flex.
:evil;
lokalhorst - 29 Mar 2008 12:46 GMT Also with the Flash 9.0.3 update, every attempt to 'test' a movie with Ctrl+Enter gives a sudden crash (authplay.dll). The only way i found to reduce the probability of crashing from 100% to something like 30% was to change the format in the Publish Settings dialog box from .swf to .exe (Windoze Projector). But anyway, this bug still exists for Windows XP and looks like an almost XP exclusive behavior (suspicion: Adobe has 'optimized' for Vista).
Yes, i'm becoming a real Adobe Fan...keep it up guys!
:evil;
RocketStevo - 02 Apr 2008 10:08 GMT I have that problem too, when I tried to view my movie or open the action script in windows, flash CS3 closed down on me? I have the same problem as BSpero that my flash closed on me because I was working on a file that was from Flash 8 and not from Flash CS3.
I have already reported the problem, but I wonder if there is any other solutions from making Flash closed down when I want to preview my movies or open the action script? I was thinking of uninstall Adobe Flash and tried to install it again to see it is better? Is that a bad idea to do? Also what did BSpero do to fix the problem that I'm having now?
Ludowing - 10 Mar 2008 11:23 GMT Hi everybody.
I think I found a solution, or at least, this worked for me: I changed the directory where I save my files. Currently I'm just putting them on the desktop, and things work fine (Flash 9.0.3 [AIR update] on Vista).
I was having all the Publish/Test/Actionscript issues, and this happened even on an EMPTY canvas! I tried a few things and noticed I was able to do anything as long as I didn't save the FLA.
So, remembering about the message in this thread stating that Flash is somewhat "drive-sensitive" (a thing that didn't apply to me, since both Flash and my files are on the main drive), I simply tried to change the dir I store the FLA and... voilà!... job done, no crash.
I hope this will help you.
>I'm also having recent problems with Flash CS3 suddenly crashing whenever I try >to publish a FLA files or attempt to view the actionscript in the FLA. I now >cannot use Flash CS3 to create and publish any FLA/SWF. biomorphic - 02 Jul 2008 05:12 GMT Same publishing and exporting freeze, different reason. Flash CS3, Mac 10.5. 3. Publishing worked as expected until I added sound files.
First, I cleared the second half of the key frames with sound, still froze. Then I cleared the first half, and it published. Then I cleared little groups of key frames until I narrowed it down to one sequence of two sound files repeating over 26 frames.
The two sound files repeated each using more than 1 frame for the first 12 frames. For the last 14 frames, each file was allotted just 1 (key)frame. I cleared the last 14 frames, and it published, telling me that the problem was not a troublesome sound file - since the same two files published just fine when given more than a single frame apiece.
The relatively simple solution was to create a single sound file containing the two sounds repeating over and over for the duration of the 14 frames. I cleared the last 14 frames again, imported the new sound file, and popped it into place.
It published.
|
|
|