Muse 2014.2 crashes constantly (Win 8.1)

Like the subject says, Muse crashes constantly. Just can't use it. Sometimes it crashes when I try to create a new site, sometimes I can go as far as making one text frame...
I can't give any more specific examples; it just crashes constantly.
All other CC apps works perfectly on my Win 8.1 machine (i7 6-core, 32gb memory, GTX680 display adapter).

Adobe Muse CC 2014.2.1 is released today which includes fix for reported issues.
Please install the update : Release notes | Adobe Muse CC
Thanks,
Sanjit

Similar Messages

Premiere Pro CC 2014 crashing constantly

Premiere Pro CC was great. Premiere Pro CC 2014 is not so great!
Constantly crashing every time I go to render after a while.
It happens so inconsistently I cannot explain.
I wish Adobe would see this post and contact me to resolve.
We pay for 5 seats every month and should not have to deal with software crashing constantly.
Thanks,
J

Hi, I have the same problem too.
Premiere pro cc 2014 crash constantly. I found problem in the overflow of RAM when I quickly scan (review) my clips on the timeline or resize the clips.
My configuration:
Premiere pro cc 8.1; 16Gb RAM; SSD 120(where i store and work with my video); CPU Intel i72700K; Windows 7 Pro x64

MUSE 2014 crashes when trying to open a page in 'Design View'

I get this error message when I try to open an existing page in Design View.
The page tries to open, displays part of the page, then stalls, then crashes.

Still trying to use MUSE 2014, after launching the program I can open two pages from the Plan view, when attempting to open a third I got this message:
I am running Windows 7 64 bit operating system with an Intel Core i5 CPU with 8gb of RAM.

Why Muse 2014 crashes?

My muse 2014 started crash after opening page or two.
I noticed that issue since installing recent Microsoft updates few days ago.
Because i have already saved my site in 2014, I'm not able to use regular Muse CC, because it doesn't read new type of files. Muse CC works with no problem at all.
Now i decided to uninstall M2014, but cant reinstall it. In Adobe Application manager it still shows Up to date, and i don't see any option to install it again.
What is solution guys?
Thanks,
Arm.

This is an issue with some users.
Re: Muse CC 2014 hangs opening page.
With regards to not being able to re-install Muse2014, you could try to log out of Creative Cloud.
Then log back in and see if it clears the program.

Premiere Pro CC 2014 and Media Encoder CC 2014 Crashing constantly

Running out of options and ideas...
Symptom: Every time I work on any project in Premiere Pro CC 2014 or try to render out in Premiere Pro CC 2014 or Media Encoder CC 2014, the software crashes after 2-3 minutes of use/rendering when the GPU is enabled in Premiere/Media Encoder, or after 5-10 minutes of use/rendering in software only mode. The crash is a software crash, Windows continues to run fine.
I have tried all the standard list of steps that adobe reps post on threads like these - clearing media cache, software only on render, new project, etc. https://helpx.adobe.com/x-productkb/global/troubleshoot-system-errors-freezes-windows.html
Windows event is not that helpful to me:
Faulting application name: Adobe Premiere Pro.exe, version: 8.2.0.65, time stamp: 0x5486db4a
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ff5ecb4de40
Faulting process id: 0x1dc8
Faulting application start time: 0x01d04a503cd82df2
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
Faulting module path: unknown
Report Id: cacdfbab-b717-11e4-826d-8863dfc268bc
Faulting package full name:
Faulting package-relative application ID:
I have wiped adobe off the machine and reinstalled - same problem. I have tried projects that crash the machine on other machines and it works fine.
The machine is new, clean install and runs everything else great - 3ds max, high res games, scientific computing - max memory use, etc.
Spec:
5K iMac running bootcamp and Windows 8.1
Intel Core i7-4790K @ 4.0 GHz
32 GB ram
1TB SSD
AMD Radeon R9 M295X 4GB GDDR5
I have used this bootcamp/imac configuration for 5+ years on 3-4 machines and everything has always just worked great. Guess it was my time for a problem, but I'm open to new ideas to try...
Finally - I hope someone from Adobe reads this. I have spent 2 nights on the phone with support. The first night I got an over confident answer that it's a gpu driver issue, just go with software only (no luck - same crashes and different drivers aren't solving the problem). Tonight I was hung up on "by accident" as the agent looked up my video card after waiting 15 minutes to talk to someone, only to be hung up on a second time while on hold after calling back and waiting 20 minutes (because I assume the Adobe call center closed). No message to say so, just hung up on. An overall very disappointing experience.
Thanks in advance to anyone with ideas on things to try,
Cheers!

I am having a similar problem.
Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
My timeline is 2K, 58 minutes in 23.976
Only effects applied are Lumetri LUTs - no third party.
I've exported as recently as a week ago without issue.
Running OSX 9.5 on an X99 board
3.75 GHz 8-core
64GB 2400 MHz RAM
EVGA Titan Black 6GB
Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
Thanks Adobe, for checking this out.

2014 Crashes Constantly

I have been working on an edit over the past couple days and Premiere Pro 2014 has been crashing about 5-10 times an hour. Tried reinstalling it...didn't work.
My setup:
MacPro 2014 8-Core 32GBRam
Mavericks
G-Raid 8TB Video Drive
Drobo 20TB
First I get a message that says it has "encountered serious problems and is shutting down"...ridiculous

More information needed for someone to help... please click below and provide the requested information
-Premiere Pro Video Editing Information FAQ http://forums.adobe.com/message/4200840
Some Mac notes that may help
-next link says After Effects, but check YOUR permissions !!!
-http://blogs.adobe.com/aftereffects/2014/06/permissions-mac-os-start-adobe-applications.ht ml
-Mac 10.9.4 and OpenCL issue https://forums.adobe.com/thread/1514717
-Mac 10.9.3 workaround https://forums.adobe.com/thread/1489922
-more Mac 10.9.3 https://forums.adobe.com/thread/1491469
-and https://forums.adobe.com/thread/1507936

Muse 2014 crashes @ 60% upload to FTP

Im trying to Upload my website and it crashes at 60% my fTP is hostgator. This was working fine yesterday and today it crashes. this is unacceptable. I need to update my website.

Hi Robert,
Please check this related thread, unable to complete upload to ftp host
- Abhishek Maurya

Updated to Adobe Muse 2014 this morning and have worked in it for the last 8 hours. Now when I try to publish the updated site to Business Catalyst for my client to preview it crashes everytime. I have tried just publishing altered files only, then tried

Updated to Adobe Muse 2014 this morning and have worked in it for the last 8 hours. Now when I try to publish the updated site to Business Catalyst for my client to preview it crashes everytime. I have tried just publishing altered files only, then tried the whole site again, and then tried publishing as a new site altogether. Thought I would then try to export as HTML in the hope of uploading the files via an FTP client and Muse crashes and locks up again. I am extremely stressed about this as I am in the last few days of of website I have been working on now with no issues since December. We are due to go live and my client needs to see it. I am desperate for an answer. It is not looking good. I am on an Apple Mac and have not had any isses publishing it for the last 6 months. Not very happy to say the least. Need desperate help.

Hi Zak, I got onto Adobe Customer Care Live Chat this morning and gave them the error message. After some trouble shooting with them it appears the older archived file of the site still publishes. I have now reverted back to the old file and copied and pasted out of the new file and from some ideas given to me by support I am now able to publish to Business Catalyst. It seems there was something corrupt within the new pages added yesterday. I have no idea if this would have still happened if I hadn't updated but I am glad it wasn't a Muse specific problem. I am loving using Muse and the support from Adobe has been excellent. Thanks everyone. By the way I do love the new version and apart from this hick up that lost me a few hours, aged me some more and gave me grey hair I really love Muse. Thanks again.

Help! Muse 2014.3 keeps crashing when I attempt to save my .muse file

I have the latest version of Muse [2014.3] Since the update the application repeatedly crashes at the least 'provocation'.
I'm building a multipage website for a client and brought the last file home [I'd been working on it at my office]. One or two of the image files needed updating, which I did. When I attempted to save the updated file I got [and keep getting] a fatal error.
The error message reads: "Dangling Ref or Ownership: BoxPageItem refers to unknown UID, BoxPageItem refers to unknown UID, BoxPageItem refers to unknown UID".
The application then hangs and I have to force quit. This is happening repeatedly and the dialogue tells me nothing about how to fix these errors [3 image errors perhaps, since the current crashes happen after updating images?]. I'm in a serious time crunch now, how can I recover my file to continue working on this project and what is causing the problem? Anyone help me?
Is this version of Muse really that unstable?
Thanks,
Charlie

Hi Fabia,
I think I fixed it over the weekend. But interestingly, my problem was images inside compositions too.
I did something similar to you, where I didn't let Muse update when the file opens [which was causing the crashes]. Instead I located the images in the assets panel, opened them in Photoshop and resaved them. Then I imported and saved after each one. This seemed to work.
For me, the 'container' was apparently OK, I had the background fill set to none anyhow, so reasoned there might be a problem with one of the seven images [seven in my case, but which one, or maybe all?]. Since then, I've been able to add content and save normally, and this morning I've been able to let the client see the site progress, as promised.
Thanks for the reply and good luck with your project.
Charlie

MUSE 2014.2 Keeps Crashing on Opening Screen

Muse keeps crashing when I try to open it. I don't know what is going on and this is getting really frustrating.

Were you using the Self-Hosted Fonts feature with 2014.1? (We've had one report of a crash that was caused by the installer failing to migrate all the preference files related to self-hosted fonts.)
Are you on Mac or Windows? What is the behavior you're encountering? If there is an error message please post a screenshot. If there's an Apple Crash Report dialog please copy/paste the contents of the report here.
Also, please send us the MuseLog.txt file from your Documents folder at [email protected] along with a link to this thread for context, of copy and paste the last few pages of that file into a message here.
Thank you.

Is anyone else having an issue with Muse 2014.2 Freezing/Crashing at launch? It worked perfectly up until tonight and nothing has changed on my computer. I'm running windows 8.1. I've tried logging in and out of CC, I've uninstalled and reinstalled Muse t

Is anyone else having an issue with Muse 2014.2 Freezing/Crashing at launch? It worked perfectly up until tonight and nothing has changed on my computer. I'm running windows 8.1. I've tried logging in and out of CC, I've uninstalled and reinstalled Muse twice with no change. Please advise. Thanks!

Are you getting any error when Muse crashes? what's the one function it lets you do before it freezes?

NVidia GeForce 344.11 Driver Release date 9/18/2014 crashes Win 8.1 Pro

NVidia GeForce 344.11 Driver Release date 9/18/2014 crashes/kills/shuts down Win 8.1 Pro, which also fails to start!
The previous version 340.52 worked ok.
Solution to get a working system:
1) let Win 8.1 take into use the previous working version (you may loose some app updates)!
2) let Win 8.1 pro update itself (takes a long time but its worth waiting!)
Note:
a. Ten points to Win 8.1 Pro being able to restore the previous working version
note: compare to Linux with eternal rest loop and "kernel in panic" state if you use NVidia's new drivers!!
b. Zero points to NVidia from this bug!
Continuation: waiting for a well tested new NVidia driver while using the older one

Hi, had exactly the same last night, on my relatively clean 8.1 64bit, GeForce Experience flagged up a recommended upgrade from 340.52 to 344.11 on my GTX650 ASUS card. Bumbled along for a while, then blue screened, reported kernel damage,
wouldn't even get far enough to restore, so had to use the 8.1 disks. Today, given its a completely clean system I tried again to prove the Nvidia was to blame, and again GeForce flagged up this upgrade, there's nothing on the system except
for Office and Avast, and again completely crashed and cycled the blue screen trying to boot. This time it eventually went into repair mode and restored right back to a clean 8.1 without the DVD's, but still had to reinstall my apps. Lots about
this on forums, seems this upgrade scrambles the registry big time. Anyone know what the actual cause of this was ?? Pretty fed up with Nvidia releasing untested crap like this.

Muse 2014.2 Crashes upon loading site.

Muse continually crashes when trying to open site.... crash log in comments....
any help appreciated....Thanks

Thread 10:
0   libsystem_kernel.dylib
0x00007fff90401132 __psynch_cvwait + 10
1   com.adobe.ape.engine
0x0000000117d0b534 TThreadWait::Wait(unsigned int) + 116 (OSXMiniThreads.cpp:268)
2   com.adobe.ape.engine
0x0000000117d18686 avmplus::PlayerAvmCore::ScriptTimeoutProc(void*) + 310 (PlayerAvmCore.cpp:1144)
3   com.adobe.ape.engine
0x0000000117d0b2fa TSafeThread::RunHelper() + 106 (OSXMiniThreads.cpp:190)
4   com.adobe.ape.engine
0x0000000117d0b36d TSafeThread::Run(EThreadType) + 61 (OSXMiniThreads.cpp:203)
5   com.adobe.ape.engine
0x0000000117d0b05e ThreadStartProc(void*) + 62 (OSXMiniThreads.cpp:80)
6   libsystem_pthread.dylib
0x00007fff8dccd2fc _pthread_body + 131
7   libsystem_pthread.dylib
0x00007fff8dccd279 _pthread_start + 176
8   libsystem_pthread.dylib
0x00007fff8dccb4b1 thread_start + 13
Thread 11:
0   libsystem_kernel.dylib
0x00007fff90401132 __psynch_cvwait + 10
1   com.adobe.ape.engine
0x0000000117d0b534 TThreadWait::Wait(unsigned int) + 116 (OSXMiniThreads.cpp:268)
2   com.adobe.ape.engine
0x0000000117e779bf CorePlayer::CoreLoop() + 223 (splayer.cpp:23705)
3   com.adobe.ape.engine
0x0000000117d0b2fa TSafeThread::RunHelper() + 106 (OSXMiniThreads.cpp:190)
4   com.adobe.ape.engine
0x0000000117d0b36d TSafeThread::Run(EThreadType) + 61 (OSXMiniThreads.cpp:203)
5   com.adobe.ape.engine
0x0000000117d0b05e ThreadStartProc(void*) + 62 (OSXMiniThreads.cpp:80)
6   libsystem_pthread.dylib
0x00007fff8dccd2fc _pthread_body + 131
7   libsystem_pthread.dylib
0x00007fff8dccd279 _pthread_start + 176
8   libsystem_pthread.dylib
0x00007fff8dccb4b1 thread_start + 13
Thread 12:
0   libsystem_kernel.dylib
0x00007fff903fc52e mach_msg_trap + 10
1   libsystem_kernel.dylib
0x00007fff903fb69f mach_msg + 55
2   com.apple.CoreFoundation
0x00007fff8b026b14 __CFRunLoopServiceMachPort + 212
3   com.apple.CoreFoundation
0x00007fff8b025fdb __CFRunLoopRun + 1371
4   com.apple.CoreFoundation
0x00007fff8b025838 CFRunLoopRunSpecific + 296
5   com.apple.AppKit
0x00007fff960a58f7 _NSEventThread + 137
6   libsystem_pthread.dylib
0x00007fff8dccd2fc _pthread_body + 131
7   libsystem_pthread.dylib
0x00007fff8dccd279 _pthread_start + 176
8   libsystem_pthread.dylib
0x00007fff8dccb4b1 thread_start + 13
Thread 13:: com.apple.NSURLConnectionLoader
0   libsystem_kernel.dylib
0x00007fff903fc52e mach_msg_trap + 10
1   libsystem_kernel.dylib
0x00007fff903fb69f mach_msg + 55
2   com.apple.CoreFoundation
0x00007fff8b026b14 __CFRunLoopServiceMachPort + 212
3   com.apple.CoreFoundation
0x00007fff8b025fdb __CFRunLoopRun + 1371
4   com.apple.CoreFoundation
0x00007fff8b025838 CFRunLoopRunSpecific + 296
5   com.apple.CFNetwork
0x00007fff8e26de90 +[NSURLConnection(Loader) _resourceLoadLoop:] + 434
6   com.apple.Foundation
0x00007fff93e00b7a __NSThread__main__ + 1345
7   libsystem_pthread.dylib
0x00007fff8dccd2fc _pthread_body + 131
8   libsystem_pthread.dylib
0x00007fff8dccd279 _pthread_start + 176
9   libsystem_pthread.dylib
0x00007fff8dccb4b1 thread_start + 13
Thread 14:
0   libsystem_kernel.dylib
0x00007fff90401946 __workq_kernreturn + 10
1   libsystem_pthread.dylib
0x00007fff8dccb4a1 start_wqthread + 13
Thread 15:: com.apple.CFSocket.private
0   libsystem_kernel.dylib
0x00007fff904013f6 __select + 10
1   libsystem_pthread.dylib
0x00007fff8dccd2fc _pthread_body + 131
2   libsystem_pthread.dylib
0x00007fff8dccd279 _pthread_start + 176
3   libsystem_pthread.dylib
0x00007fff8dccb4b1 thread_start + 13
Thread 16:
0   libsystem_kernel.dylib
0x00007fff90401132 __psynch_cvwait + 10
1   com.adobe.ape.engine
0x0000000117b530a1 BackgroundWorkManager::ThreadProc() + 289 (OSXThreadUtilities.h:185)
2   com.adobe.ape.engine
0x0000000117b52e2e BackgroundWorkManager::ThreadProc(void*) + 14 (backgroundwork.cpp:188)
3   com.adobe.ape.engine
0x0000000117d0b2fa TSafeThread::RunHelper() + 106 (OSXMiniThreads.cpp:190)
4   com.adobe.ape.engine
0x0000000117d0b36d TSafeThread::Run(EThreadType) + 61 (OSXMiniThreads.cpp:203)
5   com.adobe.ape.engine
0x0000000117d0b05e ThreadStartProc(void*) + 62 (OSXMiniThreads.cpp:80)
6   libsystem_pthread.dylib
0x00007fff8dccd2fc _pthread_body + 131
7   libsystem_pthread.dylib
0x00007fff8dccd279 _pthread_start + 176
8   libsystem_pthread.dylib
0x00007fff8dccb4b1 thread_start + 13
Thread 17:
0   libsystem_kernel.dylib
0x00007fff90401132 __psynch_cvwait + 10
1   com.adobe.ape.engine
0x0000000117b530a1 BackgroundWorkManager::ThreadProc() + 289 (OSXThreadUtilities.h:185)
2   com.adobe.ape.engine
0x0000000117b52e2e BackgroundWorkManager::ThreadProc(void*) + 14 (backgroundwork.cpp:188)
3   com.adobe.ape.engine
0x0000000117d0b2fa TSafeThread::RunHelper() + 106 (OSXMiniThreads.cpp:190)
4   com.adobe.ape.engine
0x0000000117d0b36d TSafeThread::Run(EThreadType) + 61 (OSXMiniThreads.cpp:203)
5   com.adobe.ape.engine
0x0000000117d0b05e ThreadStartProc(void*) + 62 (OSXMiniThreads.cpp:80)
6   libsystem_pthread.dylib
0x00007fff8dccd2fc _pthread_body + 131
7   libsystem_pthread.dylib
0x00007fff8dccd279 _pthread_start + 176
8   libsystem_pthread.dylib
0x00007fff8dccb4b1 thread_start + 13
Thread 18:
0   libsystem_kernel.dylib
0x00007fff90401132 __psynch_cvwait + 10
1   com.adobe.ape.engine
0x0000000117b530a1 BackgroundWorkManager::ThreadProc() + 289 (OSXThreadUtilities.h:185)
2   com.adobe.ape.engine
0x0000000117b52e2e BackgroundWorkManager::ThreadProc(void*) + 14 (backgroundwork.cpp:188)
3   com.adobe.ape.engine
0x0000000117d0b2fa TSafeThread::RunHelper() + 106 (OSXMiniThreads.cpp:190)
4   com.adobe.ape.engine
0x0000000117d0b36d TSafeThread::Run(EThreadType) + 61 (OSXMiniThreads.cpp:203)
5   com.adobe.ape.engine
0x0000000117d0b05e ThreadStartProc(void*) + 62 (OSXMiniThreads.cpp:80)
6   libsystem_pthread.dylib
0x00007fff8dccd2fc _pthread_body + 131
7   libsystem_pthread.dylib
0x00007fff8dccd279 _pthread_start + 176
8   libsystem_pthread.dylib
0x00007fff8dccb4b1 thread_start + 13
Thread 19:
0   libsystem_kernel.dylib
0x00007fff90401132 __psynch_cvwait + 10
1   com.adobe.ape.engine
0x0000000117b530a1 BackgroundWorkManager::ThreadProc() + 289 (OSXThreadUtilities.h:185)
2   com.adobe.ape.engine
0x0000000117b52e2e BackgroundWorkManager::ThreadProc(void*) + 14 (backgroundwork.cpp:188)
3   com.adobe.ape.engine
0x0000000117d0b2fa TSafeThread::RunHelper() + 106 (OSXMiniThreads.cpp:190)
4   com.adobe.ape.engine
0x0000000117d0b36d TSafeThread::Run(EThreadType) + 61 (OSXMiniThreads.cpp:203)
5   com.adobe.ape.engine
0x0000000117d0b05e ThreadStartProc(void*) + 62 (OSXMiniThreads.cpp:80)
6   libsystem_pthread.dylib
0x00007fff8dccd2fc _pthread_body + 131
7   libsystem_pthread.dylib
0x00007fff8dccd279 _pthread_start + 176
8   libsystem_pthread.dylib
0x00007fff8dccb4b1 thread_start + 13
Thread 20:
0   libsystem_kernel.dylib
0x00007fff90401132 __psynch_cvwait + 10
1   com.adobe.ape.engine
0x0000000117b530a1 BackgroundWorkManager::ThreadProc() + 289 (OSXThreadUtilities.h:185)
2   com.adobe.ape.engine
0x0000000117b52e2e BackgroundWorkManager::ThreadProc(void*) + 14 (backgroundwork.cpp:188)
3   com.adobe.ape.engine
0x0000000117d0b2fa TSafeThread::RunHelper() + 106 (OSXMiniThreads.cpp:190)
4   com.adobe.ape.engine
0x0000000117d0b36d TSafeThread::Run(EThreadType) + 61 (OSXMiniThreads.cpp:203)
5   com.adobe.ape.engine
0x0000000117d0b05e ThreadStartProc(void*) + 62 (OSXMiniThreads.cpp:80)
6   libsystem_pthread.dylib
0x00007fff8dccd2fc _pthread_body + 131
7   libsystem_pthread.dylib
0x00007fff8dccd279 _pthread_start + 176
8   libsystem_pthread.dylib
0x00007fff8dccb4b1 thread_start + 13
Thread 21:
0   libsystem_kernel.dylib
0x00007fff90401132 __psynch_cvwait + 10
1   com.adobe.ape.engine
0x0000000117b530a1 BackgroundWorkManager::ThreadProc() + 289 (OSXThreadUtilities.h:185)
2   com.adobe.ape.engine
0x0000000117b52e2e BackgroundWorkManager::ThreadProc(void*) + 14 (backgroundwork.cpp:188)
3   com.adobe.ape.engine
0x0000000117d0b2fa TSafeThread::RunHelper() + 106 (OSXMiniThreads.cpp:190)
4   com.adobe.ape.engine
0x0000000117d0b36d TSafeThread::Run(EThreadType) + 61 (OSXMiniThreads.cpp:203)
5   com.adobe.ape.engine
0x0000000117d0b05e ThreadStartProc(void*) + 62 (OSXMiniThreads.cpp:80)
6   libsystem_pthread.dylib
0x00007fff8dccd2fc _pthread_body + 131
7   libsystem_pthread.dylib
0x00007fff8dccd279 _pthread_start + 176
8   libsystem_pthread.dylib
0x00007fff8dccb4b1 thread_start + 13
Thread 22:
0   libsystem_kernel.dylib
0x00007fff90401132 __psynch_cvwait + 10
1   com.adobe.ape.engine
0x0000000117b530a1 BackgroundWorkManager::ThreadProc() + 289 (OSXThreadUtilities.h:185)
2   com.adobe.ape.engine
0x0000000117b52e2e BackgroundWorkManager::ThreadProc(void*) + 14 (backgroundwork.cpp:188)
3   com.adobe.ape.engine
0x0000000117d0b2fa TSafeThread::RunHelper() + 106 (OSXMiniThreads.cpp:190)
4   com.adobe.ape.engine
0x0000000117d0b36d TSafeThread::Run(EThreadType) + 61 (OSXMiniThreads.cpp:203)
5   com.adobe.ape.engine
0x0000000117d0b05e ThreadStartProc(void*) + 62 (OSXMiniThreads.cpp:80)
6   libsystem_pthread.dylib
0x00007fff8dccd2fc _pthread_body + 131
7   libsystem_pthread.dylib
0x00007fff8dccd279 _pthread_start + 176
8   libsystem_pthread.dylib
0x00007fff8dccb4b1 thread_start + 13
Thread 23:
0   libsystem_kernel.dylib
0x00007fff90401132 __psynch_cvwait + 10
1   com.adobe.ape.engine
0x0000000117b530a1 BackgroundWorkManager::ThreadProc() + 289 (OSXThreadUtilities.h:185)
2   com.adobe.ape.engine
0x0000000117b52e2e BackgroundWorkManager::ThreadProc(void*) + 14 (backgroundwork.cpp:188)
3   com.adobe.ape.engine
0x0000000117d0b2fa TSafeThread::RunHelper() + 106 (OSXMiniThreads.cpp:190)
4   com.adobe.ape.engine
0x0000000117d0b36d TSafeThread::Run(EThreadType) + 61 (OSXMiniThreads.cpp:203)
5   com.adobe.ape.engine
0x0000000117d0b05e ThreadStartProc(void*) + 62 (OSXMiniThreads.cpp:80)
6   libsystem_pthread.dylib
0x00007fff8dccd2fc _pthread_body + 131
7   libsystem_pthread.dylib
0x00007fff8dccd279 _pthread_start + 176
8   libsystem_pthread.dylib
0x00007fff8dccb4b1 thread_start + 13
Thread 24:
0   libsystem_kernel.dylib
0x00007fff90401946 __workq_kernreturn + 10
1   libsystem_pthread.dylib
0x00007fff8dccb4a1 start_wqthread + 13

June 18, 2014 Muse Update crashes Muse

Just upgraded to Mavericks OS so that I could install the June 18 upgrade. After opening Muse, I click on "Install Now" and Muse immediately crashes—several tries, with OS restarts. Fortunately, Muse opens when I decline the new install. Puzzled!

I should clarify. I did not do anything pother than click on updating now and it crashes, but will open if I click on update later. I did not add or change anything system-wise before that.

Muse 2014.1 update crash "Two objects claim ownership of UID: U6665 Class: RectPageItem

I updated and now I can't resave the older version. Please help, I need to get going asap.
Thanks,
Matt

Actually, I know what's going on. The problem is with all the text boxes containing images, being copied into phone version. In other words; as long the images inside text boxes are in desktop version, they are okay but as soon these text boxes are copied into the phone version, it sets your muse to crash.
To fix my problem, this is what I did:
- I went back to earlier version when I had only desktop version (since muse wouldn't even allow me to delete phone version and crashed every time I attempted)
- In desktop version; moved all the images out of the text boxes.
- activated phone version
- copied the content from desktop version into phone version and re-sized/re-arranged them as usual
That's it. Just make sure all the text boxes with images inside them, should not be copied into phone version. You will need to strip out the image from all the text boxes BEFORE you copy them into phone version.
Good luck and let me know if anyone finds this fix working for them.
Shahid

Muse 2014.2 crashes constantly (Win 8.1)

Similar Messages

Maybe you are looking for