Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Adobe Animate crashed before reaching 60% of SWF export

New Here ,
Jan 31, 2018 Jan 31, 2018

I am trying to export a 15 second frame-by-frame animation I made in Adobe Animate CC. However, whenever I try to export the file as a movie (.swf format) it reaches about 57% before crashing. I have tried exporting on different laptops (MacBook Air and MacBook Pro), but nothing seems to help. Exporting a more primitive animation of about 2 seconds works quickly and correctly - so I really don't know whats happening.

Any help would be greatly appreciated! (Sorry if this answer is incredibly simple, I am very new to the program)

Here is the crash report:

Process:               Adobe Animate CC 2018 [10995]

Path:                  /Applications/Adobe Animate CC 2018/Adobe Animate CC 2018.app/Contents/MacOS/Adobe Animate CC 2018

Identifier:            com.adobe.Adobe Animate CC 2018.application

Version:               18.0.1 (18.0.1.115)

Code Type:             X86-64 (Native)

Parent Process:        ??? [1]

Responsible:           Adobe Animate CC 2018 [10995]

User ID:               1014142737

Date/Time:             2018-01-31 22:17:22.763 +0100

OS Version:            Mac OS X 10.12.6 (16G29)

Report Version:        12

Anonymous UUID:        6C4FCED7-FD65-9C98-8FDB-7EA03E607B90

Sleep/Wake UUID:       1C28C62D-2188-4E0A-99DE-8281A24FB559

Time Awake Since Boot: 26000 seconds

Time Since Wake:       6400 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)

Exception Codes:       KERN_INVALID_ADDRESS at 0x0000600007200000

Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11

Termination Reason:    Namespace SIGNAL, Code 0xb

Terminating Process:   exc handler [0]

600
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Community Expert , Jan 31, 2018 Jan 31, 2018

is there anything in your library?  if so, check for a corrupt library item:

1. create a duplicate test fla (so you always preserve the original unchanged).

2. with the duplicate remove the top 1/2 of assets and test.  if there's no crash, there's likely a corrupt asset among the removed items>restore that dupcliate (or recreate it) and remove the top 1/2 of the top 1/2 (top 1/6) and test.  etc.  you should be able to narrow down the corrupt asset within n+1 steps where you have 2**n library asset

...
Translate
Community Expert ,
Jan 31, 2018 Jan 31, 2018
LATEST

is there anything in your library?  if so, check for a corrupt library item:

1. create a duplicate test fla (so you always preserve the original unchanged).

2. with the duplicate remove the top 1/2 of assets and test.  if there's no crash, there's likely a corrupt asset among the removed items>restore that dupcliate (or recreate it) and remove the top 1/2 of the top 1/2 (top 1/6) and test.  etc.  you should be able to narrow down the corrupt asset within n+1 steps where you have 2**n library assets.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines