Workarounds for project crashing when exporting?
I have developed a project in captivate 6 which is now crashing captivate when I export it. I can preview it in 'Web Browser' and 'HTML 5 output'. But when I export it as a SCORM package it crashes. I was able to do that yesterday but today it's crashing.
Any suggestions? Any one?
Slides contain nothing fancy except just mp3s, text and graphics.
Specs
Captivate 6 project
Tested on both Mac and PC
From,
Luke L
Hi Luke,
In Project Preferences, Start / End there is an option preload startscreen.
Best regards.
Philippe
Le 15 oct. 2012 à 21:48, Luke L PSA <[email protected]> a écrit :
Re: workarounds for project crashing when exporting?
created by Luke L PSA in Import/Export - View the full discussion
thank you tchiboo.
Which start screen is this? Thanks for the help desperate to know.
Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/4775908#4775908
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4775908#4775908
To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4775908#4775908. In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Import/Export by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.
Similar Messages
-
InDesign Crashes when exporting to InCopy
I support several hundred InDesign/ InCopy users. We have been using this workflow for several years.
Approximately a month ago, we migrated to CS5 (7.0.3). I began to immediately get support calls that InDesign and InCopy were crashing. A few of the calls were that InCopy was crashing when pasting text from MS Office, but he overwhelming majority of the calls are for InDesign crashing when exporting stories to InCopy. If exported one at a time, the stories export fine. When exporting all stories or an entire text layer of stories, it will crash nearly without fail.
Our environment consists of Mac Pro 2x2.66Ghz and 2.8Ghz Intel Core Duo 2 iMacs running 10.5.8. with CS5 7.0.3. This is happening on multiple machines. A few of them have been gone over to verify base OS integrity, permissions repaired, DiskWarrior run etc… to make sure we did not have individual machine issues.
I need resolution for both issues, but the crashing while exporting is so prevalent that my graphic designers are starting to really get aggravated.
I searched the forum for "InCopy", for "export" and for "crash." None of those terms returned a single hit. I can't imagine those terms are not in this forum, so I am working on the assumption that searching must be broken at the moment.
Thanks in advance for any guidance,
KevinTry posting on the InCopy forum. There was another similar report there...
Did you fill out a bug report?
Harbs -
Flash CS5.5 crashes when exporting movieclip for Actionscript
Hello,
My Flash CS5.5 crashes when exporting movieclip for Actionscript (select movieclips -> modify -> convert to symbol -> check export for actionscript). I think this only happens when Photoshop CS5 is open.
Does anyone know how to fix this? I'm using Win7 64-bit. The only open programs are Flash, Photoshop, and Firefox.Oddly enough, I opened up Flash again, today, just to see if it was still the same, and it had worked. Everything seemed normal, I opened a new document and started working. Then, out of nowhere it stopped responding again. So I waited for it to respond, it didn't. I closed it from the task manager, and now it's back to the original problem of crashing when I try to create a new document or open an old ontrie
Update: I tried the cleaner, as you'd suggested. Followed all the steps, but to no avail. Think it may have something to do with my machine, and less with the software? -
IMovie 11 crashes when exporting to Quicktime
iMovie 11 crashes when exporting to Quicktime. Some people have posted that this problem disappeared when they upgraded from Lion to Mountain Lion. However, I am running Mt.Lion and it still happens. If there is no fix for this bug, does anyone know a workaround that will produce the same ultimate result..namely, a Quicktime movie that is not too large to attach to emails. Apple, please fix this. Thank you.
Update after two Apple iApps specialists spent 1.5 hours on the phone with me: There are 3 "poison pills" (that we know of) that will cause the crash if any of the three is part of the movie: Picture-in-picture, side-by-side, or a circle open/close transition. Otherwise, no crash. The specialist made a movie on his own computer, containing the poison pills, but he exported to Quicktime without a crash. There is at least one report in the threads of a problem like mine. Thus, some Gremlin is causing this, in some computers. The iApps specialist was curioius to know whether a lot of people have this problem, or only a few. (If a lot, then it is worth submitting to the engineers to fix.) He said if you have this problem, call Apple. I asked if such people should post a "Me too!" on this thread. He said no, better to call Apple and report it. So that's the story. I can live without those poison pills in my export-to-quicktime movies. I am just a consumer, not a pro, and I can live with it. But it would be nice if Apple could fix this.
-
Crystal Crashes when exporting to PDF
Hi Experts,
Crystal reports crashes when exporting a report to PDF. I am using Crystal Reports for SAP Business One, what could be causing this..is it a patch level problem ?Hi,
Please check this thread http://scn.sap.com/thread/3303863.
What is your B1 version and PL?
Thanks & Regards,
Nagarajan -
Media Encoder crashes when exporting from Premiere Pro
Media Encoder crashes when exporting from Premiere Pro. I am queueing multiple files for export and Media Encoder will crash. The computer system has 32GB of RAM and the videos export fine in Premiere, but that requires exporting each one individually. Each video file is being down converted and some can be quite long (upwards of 3-5 hours). Nothing else is running on the computer that would take up memory.
Any idea why Media Encoder will crash?Try turning off GPU acceleration.
-
My new iMac with FCPX crashes when rendering complex templates and crashes when exporting with Motion 5
Using Motion 5.0.6 and Final Cut Pro X 10.0.7 on New iMac (December 2012) Mountain Lion,
Intel Core i7 quad-core a 3,4GHz, Turbo Boost fino a 3,9GHz
32GB di SDRAM DDR3 a 1600MHz - 4 x 8GB
Fusion Drive da 3TB
NVIDIA GeForce GTX 680MX 2GB GDDR5
During the rendering of complex FCPX mac crashes and I have to force a restart.
I also happens when I try to export movies with Motion 5.
Does anyone have the same problem with my new iMac?Problems such as yours are sometimes caused by files that should belong to you but are locked or have wrong permissions. This procedure will check for such files. It makes no changes and therefore will not, in itself, solve your problem.
First, empty the Trash.
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Triple-click anywhere in the line below to select it, then drag or copy it — do not type — into the Terminal window:
find . $TMPDIR.. \( -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 -o -acl \) 2> /dev/null | wc -l
Press return. The command may take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear.
The output of this command, on a line directly below what you entered, will be a number such as "35." Please post it in a reply. -
InDesign Crashes When Export to PDF - Only When Hyperlinks Checkbox is Enabled
I think I've read every single posting on the web for InDesign crashing on export, and have tried pretty much all of the solutions with no luck.
I am exporting a document (a table of contents document) in InDesign to PDF. With any of the export options on EXCEPT the hyperlinks option, it does fine. When I click on the hyperlinks option, it crashes.
I've recreated this document several times, e.g. exporting to IDML (which also causes it to crash), copying the text out and pasting it into a new document (still crashes)...the problem file is the one titled Intro_Electrical. I've tried replacing it with another document, but it still crashes. I've tried creating a new book, but it still crashes.
The link to the files is here:
https://www.box.net/shared/stbtj81v3j
Normally this would not be a big deal, but I have an ugly feeling that several of my foundation documents are based off of this file. If at all possible, I would like to be able to correct this issue instead of having to turn off the hyperlink option.
If you can offer any advice for correcting this, I'd really appreciate it. I've been dealing with this problem since CS4 and was hoping that it was something that would be fixed with CS5, but apparently not...or it's just me, I'm not sureThe table of contents is build ussing TOC module. It's collecting content from 7 book documents. I have almost the same file build in an other language and it's working perfectly. Never had this issue before. I can not find the difference between both documents. I tried to deleting all the chapters and ad them one by one but it's crashing the moment that hyperlinks are used no mater how many chapters from other documents are added. However if the table of contents is made only from one documnet - inside of that document hyperlinks are stable and pdf can be produced not cousing any issues.
I will try to delete page by page and check if I can discover problem maker. As this is going to be soooooooo time consuming I'm waiting for any other sollution. Anyone? -
Is ILife 11 the current version today? (May 2014). ILife 11 on Amazon appears to be 3+ yrs old?
When searching for ILife 11 on the Apple Store, I am directed to a separate purchase of Iphoto version 9.
Somewhat confusing, Apple is always so clear with these things.
The goal is to upgrade my Iphoto 8.2.1 to Iphoto 11.
I have a Macbook Pro, Maverick 10.9.2 and Iphoto is crashing when exporting photos.
I understand ILife is the way to fix it.
Thanks!The current version of iPhoto is iPhoto 9.5.1., and it is the latest version of iPhoto '11.
If you are running Mavericks 10.9.2, you can buy iPhoto 9.5.1 from the AppStore - it is the currently sold version.
The iLife bundle is called iLife '11, and the iPhot version in iLife '11 is iPhoto 9.x.x. - that is confusing allright
I have a Macbook Pro, Maverick 10.9.2 and Iphoto is crashing when exporting photos.
While it is certainly useful to upgrade to the current iPhoto version to be fully compatible with MacOs X 10.9.2, there may be a differnet reason for the crashes. Is there an error message with the crashes? When did these start? Did you import new photos or videos? Install other software? -
CS2 InDesign crash when exporting
Hi,
I've got a copy of CS2 InDesign at work that crashes when exporting a certain file to PDF.
The files have limited information on each page except for placed PDF & JPG images. The images themselves seldom get above 300kb each, but there are lots - some times 5 per page in an 80 page document. It's a document to be printed so the images are as small as they can be.
When exporting the document, ID crashes without warning - it just vanishes, no dialog box saying 'This application unexpectedly quit' or anything.
Is this common? I have plenty of memory on the Mac, and no other applications or windows are open at the same time.
Any suggestions as to why this happens?
All text in the PDF images are outlined in Illustrator so presumably it's not a type recognition issue.
Any suggestions welcome.
cheers
GHi Bob,
System spec is PowerPC G5, version 10.4.11. I'll have to ask our Mac expert
if CS2 is fully patched.
Cheers for your response.
G -
Final Cut Express FCE Crashes when exporting to Quicktime or Quicktime conv
Final Cut Express FCE Crashes when exporting to Quicktime or Quicktime conversion!
This started completely out of the blue last night. The export gets about 30-50% done and FCE disappears from the screen and the "FCE quit unexpectedly" message pops up. This has never happened before and I was doing exports of this very project all week. All other projects won't expect, the current project won't export when brought into a new file, I tried reinstalling FCE, and I deleted the pref files spoken about in the forum.
Any Ideas!!!????Try repairing permissions and re-boot.
Al -
Lightroom 5.4 reaches 10% and crashes when exporting a slideshow video.
Lightroom 5.4 reaches 10% and crashes when exporting a slideshow video every time. I have Abobe Premiere elements 10, which works fine for creating a slideshow. Could there be a conflict? Any suggestions most welcome as this problem is driving me bom-boms.
Regards DaveThanks so much ... just tried it and it worked perfectly. I just used a small external drive to transfer them, and ticked the option to 'copy and import photos to new location', so not only the catalogue, but also the photos themselves are on my iMac. Very simple. Thanks.
-
Incopy CS6 crashes when exporting to pdf
Incopy 6 crashes when exporting to pdf. Message – unknown error
Hi Sushmar
My editor edits with Incopy 6, everything goes well until she wants to export a pdf, Incopy 6 then crashes. Incopy 5.5 does not have this problem. Please point me in the right direction, as we have extremely tight deadlines and no other way of working.
Tx
LVG -
Motion is constantly crashing when exporting a huge project
Hi Folks,
I just started with Motion a few weeks ago.
After making a lot of rookie mistakes, I think I got the basics now.
Motion opened up a new world of working with videos for me.
But I reached a point, where playing around does not help any more.
I need some advise from a skilled Motion designer.
My question:
Generally - What are the limits of a Motion 4 project regarding size and complexity and how I can expand it.
In particular - How can I produce a video of my really big motion project.
My small problem:
When working in Motion, I have to watch the memory usage (I use "istat menus" for this).
When memory becomes almost used up, I save the project then close and re-open Motion.
In the meantime, I have a detailed knowledge of the actions that I should avoid to maximize
the time between the close & re-open actions.
This helps reducing Motion crashes. I think Motion has a bug with memory handling somehow.
Although working with Motion this way is exhausting, this is only my small problem.
My big problem:
Motion does not export (render) my project. I don't mind waiting 24 hours for the result, but there is no result.
Motion 4 always crashes after some time. Typically after 4 to 5 hours. The whole computer gets stuck,
the only thing I can do is recycle power. I can not show the result of my work. All I can do is blame "the software".
For this I need a solution, and I need it ASAP!
What I did so far:
I tried everything. Really…
I do not run any other software parallel with Motion. No Mail, no Safari, no nothing -> this helps a lot while editing !
Disabling render options motion blur, shadows, reflections and DOF helped in the beginning when the project was not finished.
Reducing quality helped in the beginning but I did not tried it again because the results are unusable.
Trashing preferences with "option-CMD Park+Ride" did not help.
Deleting the preference file did help making the software more responsive. Almost no beachballs after that.
Repairing permissions…. Checking filesystem… playing with preferences… nothing helped.
Then I was at a point, where I was mentally prepared for the ultimate step:
I wiped the hard-drive and installed Snow Leopard and FCP from the original DVDs.
Did not help. (BTW this takes a whole working day and half of the night).
Of course, I always apply the latest updates and patches.
Last night, I ordered a new iMAC (27", Quadcore, 8GB Ram) to be sure it is not a hardware defect.
Unfortunately its ETA is 2 weeks.
The machine I am actually using: 24" iMac 3,06MHz core2 duo with 4GB of RAM and GT130.
About my project:
length: 42 seconds
Format: 720p50
Contents: approximately 10 greenscreen videoclips 720p50 ( 10 to 20 seconds long) with Primate RT filter, 100 images (PDF), 500 rectangles.
Camera: one camera with 8 non-overlapping framing behaviors.
plugins: some filters from noise industries and FxFactory. No dubious untested 3-rd party plugins.
Untested ideas:
- Output parts of the project and assemble them in final cut. (I got this idea 1 second ago while writing this post). Anyone tried this?
- Single-stepping through the project and capturing a screenshot of every single frame (42*50 = 2100 oh my god!) Maybe by using a macro?
- Using a new computer with faster graphic-board and more RAM. As far as I know, Motion is a 32bit application and can not address more than 4 GByte of RAM. Also it will not use more than one CPU core. Will it help anyway?
- Installing some secret Pro-App beta-patches to fix Motion. Are there any? If so, how to get them?
- Searching for some hidden file that lists the filter, action or object that caused the last crash. Maybe I only have to rearrange or remove something to make it work perfectly.
Anyone out there who has experience with complex Motion-projects ?
Byebye and Tschüß
ManfredI gave it a try and replaced all *.pdf files by *.psd or *.jpg files, keyed all video clips outside of Motion and replaced the original footage with the assigned keyers, despillers and color-correctors by ready-to-use ProRes4444 files. If this changed anything, then it was very subtle. Without "shadow", "reflections" and "depth of field" applied, I can export the project. This takes 40 minutes or so.
With this three things checked, Motion crashes (see below). The final export also needs to have lights enabled and maybe motion blur.
My big hope is, that the 27" iMac can handle it because of its 8GB Ram and the 4870 Graphics (arrives on Feb,10 thumbs up). The iMac I am using now has only GT130 and 4GB Ram, maybe this is too weak? Otherwise I have to split the project into pieces an assemble them in final cut. There are no cuts, the whole thing is one flow which makes this idea difficult.
Here the latest crash report (although I dont think it makes any sense to anyone but hope dies last):
Process: Motion [436]
Path: /Applications/Motion.app/Contents/MacOS/Motion
Identifier: com.apple.motion
Version: 4.0.1 (698)
Build Info: Motion-6980000~14
Code Type: X86 (Native)
Parent Process: launchd [125]
Date/Time: 2010-01-27 00:00:36.955 +0100
OS Version: Mac OS X 10.6.2 (10C540)
Report Version: 6
Interval Since Last Report: 373471 sec
Crashes Since Last Report: 5
Per-App Interval Since Last Report: 58356 sec
Per-App Crashes Since Last Report: 3
Anonymous UUID: 0F1AA23E-656B-43EC-B8C6-F16DBE334461
Exception Type: EXCBADACCESS (SIGBUS)
Exception Codes: KERNPROTECTIONFAILURE at 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 com.apple.CoreFoundation 0x900b4413 CFQSortArray + 259
1 com.apple.CoreFoundation 0x900c77ec __CFRunLoopDoObservers + 1020
2 com.apple.CoreFoundation 0x900843e2 __CFRunLoopRun + 1154
3 com.apple.CoreFoundation 0x90083864 CFRunLoopRunSpecific + 452
4 com.apple.CoreFoundation 0x90083691 CFRunLoopRunInMode + 97
5 com.apple.HIToolbox 0x9030ef0c RunCurrentEventLoopInMode + 392
6 com.apple.HIToolbox 0x9030ecc3 ReceiveNextEventCommon + 354
7 com.apple.HIToolbox 0x9030eb48 BlockUntilNextEventMatchingListInMode + 81
8 com.apple.AppKit 0x96a7aac5 _DPSNextEvent + 847
9 com.apple.AppKit 0x96a7a306 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156
10 com.apple.AppKit 0x96cf1335 -[NSApplication _realDoModalLoop:peek:] + 720
11 com.apple.AppKit 0x96cf0ab1 -[NSApplication runModalForWindow:] + 273
12 com.apple.ozone.framework 0x00a4b21e -[OZExportProgressController openDialog:withTitle:windowTitle:withDoneMsg:startFrame:lastFrame:] + 366
13 com.apple.ozone.framework 0x00a49660 -[OZExportManager initRender:nodeIndex:range:] + 1088
14 com.apple.ozone.framework 0x00a43ef3 -[OZExportManager initRender:] + 275
15 com.apple.ozone.framework 0x00a3d400 -[OZExportController _exportDidEnd:returnCode:contextInfo:] + 416
16 com.apple.AppKit 0x96f839f6 -[NSSavePanel _didEndSheet:returnCode:contextInfo:] + 295
... many lines removed here ....
Model: iMac9,1, BootROM IM91.008D.B08, 2 processors, Intel Core 2 Duo, 3.06 GHz, 4 GB, SMC 1.45f0
Graphics: NVIDIA GeForce GT 130, NVIDIA GeForce GT 130, PCIe, 512 MB
Memory Module: global_name
AirPort: spairportwireless_card_type_airportextreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.10.91.26)
Bluetooth: Version 2.2.4f3, 2 service, 1 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Serial ATA Device: WDC WD1001FALS-40K1B0, 931,51 GB
Serial ATA Device: OPTIARC DVD RW AD-5670S
USB Device: USB2.0 Hub, 0x05e3 (Genesys Logic, Inc.), 0x0608, 0x24100000
USB Device: Composite Device, 0x1604, 0x8007, 0x24140000
USB Device: USB2.0 Hub, 0x05e3 (Genesys Logic, Inc.), 0x0608, 0x24130000
USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8502, 0x24400000
USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8242, 0x04500000
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x06100000
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8215, 0x06110000
FireWire Device: d2 quadra (button), LaCie, Up to 800 Mb/sec
FireWire Device: d2 quadra (button), LaCie, Up to 800 Mb/sec
FireWire Device: d2 quadra (button), LaCie, Up to 800 Mb/sec
FireWire Device: d2 quadra (button), LaCie, Up to 800 Mb/sec -
Mac Projector Crashes When exported From Flash CS5.5
Something strange that i noticed, when i had exported a presentation for a Mac,
on a 64 bit windows 7 using flash cs5.5.
the applicaton gets the paths of a few swfs from an XML file
and loads them one after the other.. there is a small bit of interactivity.
.. tested this projecter on various versions of MAC, it crashes often,crashes earlier if i switch applications. what follows here is a part of a report that was generated on an OS X 10.7.3,
works fine if the projector is exported from flash cs5.
i need it to work when exported from flash cs5.5.. any suggestions on what i need to change in my application so that it works when exported from flash cs5.5?
Your help would be appreciated Thanks in Advance
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000500d98eb
VM Regions Near 0x500d98eb:
Memory tag=240 000000000ebd0000-000000000ec90000 [ 768K] ---/rwx SM=NUL
-->
__TEXT 0000000070000000-0000000070142000 [ 1288K] r-x/rwx SM=COW /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio
Application Specific Information:
objc_msgSend() selector name: orderOut:
objc[9434]: garbage collection is OFF
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x92115d47 objc_msgSend + 23
1 com.macromedia.Flash Player.app 0x00467d96 main + 240950
2 com.macromedia.Flash Player.app 0x0047efda main + 335738
3 com.macromedia.Flash Player.app 0x002feae2 0x1000 + 3136226
4 com.macromedia.Flash Player.app 0x0033a77b 0x1000 + 3381115
5 com.macromedia.Flash Player.app 0x00462718 main + 218808
6 com.macromedia.Flash Player.app 0x004628b2 main + 219218
7 com.apple.CoreFoundation 0x98e0b3df __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 15
8 com.apple.CoreFoundation 0x98e0ad96 __CFRunLoopDoSources0 + 246
9 com.apple.CoreFoundation 0x98e34c68 __CFRunLoopRun + 1112
10 com.apple.CoreFoundation 0x98e3447c CFRunLoopRunSpecific + 332
11 com.apple.CoreFoundation 0x98e34328 CFRunLoopRunInMode + 120
12 com.apple.HIToolbox 0x9289117f RunCurrentEventLoopInMode + 318
13 com.apple.HIToolbox 0x928984e7 ReceiveNextEventCommon + 381
14 com.apple.HIToolbox 0x92898356 BlockUntilNextEventMatchingListInMode + 88
15 com.apple.AppKit 0x98fe8a9c _DPSNextEvent + 678
16 com.apple.AppKit 0x98fe8306 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 113
17 com.apple.AppKit 0x98fe4675 -[NSApplication run] + 911
18 com.apple.AppKit 0x99278261 NSApplicationMain + 1054
19 com.macromedia.Flash Player.app 0x000032a2 0x1000 + 8866
20 com.macromedia.Flash Player.app 0x000031c9 0x1000 + 8649
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x97d3f90a kevent + 10
1 libdispatch.dylib 0x99a75c58 _dispatch_mgr_invoke + 969
2 libdispatch.dylib 0x99a746a7 _dispatch_mgr_thread + 53
Thread 2:
0 libsystem_kernel.dylib 0x97d3e83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9237ce78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9232482a pthread_cond_wait + 48
3 com.macromedia.Flash Player.app 0x003ff62f 0x1000 + 4187695
4 com.macromedia.Flash Player.app 0x0001a06c 0x1000 + 102508
5 com.macromedia.Flash Player.app 0x003ff70c 0x1000 + 4187916
6 com.macromedia.Flash Player.app 0x003ff73a 0x1000 + 4187962
7 com.macromedia.Flash Player.app 0x003ff847 0x1000 + 4188231
8 libsystem_c.dylib 0x92378ed9 _pthread_start + 335
9 libsystem_c.dylib 0x9237c6de thread_start + 34
Thread 3:
0 libsystem_kernel.dylib 0x97d3e83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9237ce78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9232482a pthread_cond_wait + 48
3 com.macromedia.Flash Player.app 0x003ff62f 0x1000 + 4187695
4 com.macromedia.Flash Player.app 0x0001a06c 0x1000 + 102508
5 com.macromedia.Flash Player.app 0x003ff70c 0x1000 + 4187916
6 com.macromedia.Flash Player.app 0x003ff73a 0x1000 + 4187962
7 com.macromedia.Flash Player.app 0x003ff847 0x1000 + 4188231
8 libsystem_c.dylib 0x92378ed9 _pthread_start + 335
9 libsystem_c.dylib 0x9237c6de thread_start + 34
Thread 4:
0 libsystem_kernel.dylib 0x97d3e83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9237ce78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9237cf7b pthread_cond_timedwait_relative_np + 47
3 com.macromedia.Flash Player.app 0x003ff5f8 0x1000 + 4187640
4 com.macromedia.Flash Player.app 0x001c58fe 0x1000 + 1853694
5 com.macromedia.Flash Player.app 0x003ff70c 0x1000 + 4187916
6 com.macromedia.Flash Player.app 0x003ff73a 0x1000 + 4187962
7 com.macromedia.Flash Player.app 0x003ff847 0x1000 + 4188231
8 libsystem_c.dylib 0x92378ed9 _pthread_start + 335
9 libsystem_c.dylib 0x9237c6de thread_start + 34
Thread 5:
0 libsystem_kernel.dylib 0x97d3e83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9237ce78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9237cf7b pthread_cond_timedwait_relative_np + 47
3 com.macromedia.Flash Player.app 0x003ff5f8 0x1000 + 4187640
4 com.macromedia.Flash Player.app 0x00305328 0x1000 + 3162920
5 com.macromedia.Flash Player.app 0x003ff70c 0x1000 + 4187916
6 com.macromedia.Flash Player.app 0x003ff73a 0x1000 + 4187962
7 com.macromedia.Flash Player.app 0x003ff847 0x1000 + 4188231
8 libsystem_c.dylib 0x92378ed9 _pthread_start + 335
9 libsystem_c.dylib 0x9237c6de thread_start + 34
Thread 6:: com.apple.audio.IOThread.client
0 libsystem_kernel.dylib 0x97d3cc22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x97d3c1f6 mach_msg + 70
2 com.apple.audio.CoreAudio 0x9cd8e9fe HALB_MachPort::SendMessageWithReply(unsigned int, unsigned int, unsigned long, unsigned long, mach_msg_header_t*, unsigned int) + 122
3 com.apple.audio.CoreAudio 0x9cd8ea6a HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, unsigned int) + 60
4 com.apple.audio.CoreAudio 0x9cd86e5f HALC_ProxyIOContext::IOWorkLoop() + 1145
5 com.apple.audio.CoreAudio 0x9cd86926 HALC_ProxyIOContext::IOThreadEntry(void*) + 136
6 com.apple.audio.CoreAudio 0x9cd86898 __HALC_ProxyIOContext_block_invoke_6 + 20
7 com.apple.audio.CoreAudio 0x9cd8681d HALB_IOThread::Entry(void*) + 69
8 libsystem_c.dylib 0x92378ed9 _pthread_start + 335
9 libsystem_c.dylib 0x9237c6de thread_start + 34
Thread 7:
0 libsystem_kernel.dylib 0x97d3f02e __workq_kernreturn + 10
1 libsystem_c.dylib 0x9237accf _pthread_wqthread + 773
2 libsystem_c.dylib 0x9237c6fe start_wqthread + 30
Thread 8:
0 libsystem_kernel.dylib 0x97d3f02e __workq_kernreturn + 10
1 libsystem_c.dylib 0x9237accf _pthread_wqthread + 773
2 libsystem_c.dylib 0x9237c6fe start_wqthread + 30
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00dbe0e0 ebx: 0x00dbe0e0 ecx: 0x99985548 edx: 0x500d98cb
edi: 0x0000036e esi: 0x00aad0e0 ebp: 0xbfffe4f8 esp: 0xbfffe488
ss: 0x00000023 efl: 0x00010202 eip: 0x92115d47 cs: 0x0000001b
ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f
cr2: 0x500d98eb
Logical CPU: 1Looks like it was a memory problem with the jvm.ini file.
Pumped it up to 256 and it works now.
Hope this helps anyone else in the future if they come across it.
Thanks.
Maybe you are looking for
-
After doing a clean install of 10.5 and importing all of my mail messages from my .mac account, I noticed that many of the messages in my sent folder had the wrong date. Apparently they were marked with the date on which I first synchronized my 10.5
-
Firefox stops responding while loading a specific website
Whenever I open firefox and immediately try to load the website http://www.espncricinfo.com/ , firefox stops responding. But if I try to load this site after browsing some other sites, the problem seems to resolve automatically. The website loads wit
-
Can't get PersistenceUnit to work
Hi all, I am setting up the Netbeans 6.0 IDE with JSF1.2, Tomcat 6.0 and Hibernate through JPA. I am newbie on JavaEE though not on JavaSE and Netbeans. However I am having painfully difficulties in making some tests and trials, to gain deeper knowle
-
Spry Photo Gallery not viewing
am new to web design and followed this tutorial to make a Spry Photo Gallery: http://www.adobe.com/devnet/dreamweaver/articles/spry_photo_album.html I am using Dreamweaver CS3 and when I preview my files, everything is perfect and in place. When I up
-
Really not sure what to categorize this question as......
How do I fix a problem that I have with an online game site. I downloaded a game from Shockwave and it wouldn't work. So I tried trouble shooting and my computer stated that the game had incompatible files. I need help with resolving incompatible