RoboHelp 8 project crashed again
Last week my large RoboHelp project crashed (due to the November 2 bug or whatever), and I was able to recover the project by opening the HHP file and importing missing files. Importing the missing files also seemed to fix the broken links for the images.
The bad news is that late this afternoon the project crashed again. (And this project is due Monday morning, so the timing is not good.) I tried rebooting, renaming the cpd file, and opening the project -- with bad results, namely, the "missing files and broken links" problem all over again. So now I'm trying to decide whether I should:
- Open the HHP again (which will probably require a lot of importing work)
-or-
- Open the previous day's project backup (which will also require a lot of work)
Any advice?
When can we expect Adobe's fix for the November 2 bug?
Thank you!
Hi!
I'm also experiencing a RH8 crashing issue...however, I'm not sure if my issues are related. Peter, maybe you can tell me; I figured I'd try here before creating a new thread.
I'm having trouble opening certain project files...period. As soon as I launch RH8 and select my project from the list of Recent Projects, I get the "Adobe RoboHelp 8 has encountered a problem..." window right away. What did I do wrong? This problem just surfaced for me this week. Now, I'm working on a different project, and just a little while ago, it's crashing when I open certain files. I was just working on this particular project a couple of hours ago w/ no problems, but now, everytime I select that file, I crash. So, I have a couple of things going on and I'm really not sure what happened.
Is this fixable? Is it related to the Nov. bug being discussed? Today's crashed project has only few files, but the one that's been giving me problems all week is HUGE (60-70 topics, hundreds of images).
Thank you!!
Similar Messages
-
RoboHelp HTML v5 Crash when I try to open topic
I did a minor edit on a small topic in an existing project.
Robohelp crashed before I could save. I ended the task and reloaded
the project into HR, and received this msg:
The reference to the file, "C:\help projects\UW\IDI UW\Chap
15\file:\C:\help projects\UW man.css" from the file ""C:\help
projects\UW\IDI UW\Chap 15\syndrome.htm" contains illegal
characters and will not be shown in the project manager.
RH crashed again. I loaded the referenced file in Internet
Explorer, found the funky path displayed on the error msg, modied
it, and saved the file. When I tried to open the project in RH and
open the topic, I didn't receive the error message again, but RH
did crash. Ended the task w/Windows Task Manager, loaded RH and
opened the project. I then deleted the offending topic and
reimported it from an MS Word file. No error msg., but RH crashed
again.
I was able to edit another topic, save, and regenerate.
However, now RH crashes no matter which topic I try to edit. The
last time I worked on this project was 11/07, and everything went
smoothly then.
It's late Sunday evening. I'm stumped. Great issue for a
Monday morning. Any ideas?I decided to try the oldest trick in the book and reboot the
computer. That resolved the problem! Duh!
However, I need to edit the index on the project, and RH
crashes when I try to open the index designer. I haven't tried to
reboot. I am opening another topic on this one. I found many issues
with RH crashes, and maybe that will help someone else, when we
have a resolution. -
Project crashing caused by Memory?
I am having a program crash problem with Final Cut Pro when working with any number of projects (big or small). One large project (33MB), I cannot even open without FCP crashing. +*When I say crash, I mean that the program quits without notice and all windows disappear immediately without warning (i.e. no spinning beach ball or frozen windows). A dialog box then appears oon screen telling me that FCP quit unexpectedly and offers me a report or send Apple a message.+
This is my set up: I am running Final Cut Pro HD on a Dual 2.3 GHz PowerPC G5 with 4GB RAM with Mac OS X (10.4.11). My OS and all apps live on a 230 GB Internal start-up HD (159GB available) and my projects and all related assets live on a 500GB external Seagate high speed USB 2 Drive (14GB available). No other USB 1 devices are on the bus.
In order to correct the problem did the following in this order:
1- Used FCP Rescue to trash and reset FCP. No effect
2- Used Mac's Disc Utility to Repair Disk Permissions and Repair Disk (both run twice). No effect
3- Copied project file to main start-up drive in order to eliminate possible issue with linked asset. Project crashed FCP at launch.
4- Reformatted start-up Drive and performed clean install of OS and FCP. No Effect. Project still caused crash at launch.
Non of these seemed to work, so I started with a auto-saved backup of the project. I saved it as a separate copy with a new name. It opened without a crash, yet all media clips needed to be reconnected. Hooray! So, I started reconnecting media. As I do this, I reconnect small bunches of clips at a time and click save. During this long process, the program crashed again. So, I restarted FCP and the project opened without crashing. I continue to reconnect media as before. Now it takes half the time to crash again. I use FCP Rescue to trash prefs and restart FCP again, but as the program loads the project, it crashes before it can finish opening the project.
It seems to me that each time FCP crashes with a project open, it damages the project file somehow to the point that it will not open at all. Even after purging program preferences and attempting to reopen the crashed project file. Is this possible? Is there some other cause for projects to crash and or not open this way?
Now I am wondering if it is hardware causing the crashes leading to the corrupt files. I ran Apple's Hardware test and the MAC passes both the fast and long test. I also downloaded Temperature Monitor to check memory temp for overheating. It is running between 74-77˚C (165-170˚F), a few degrees higher during a render test. Does anyone know if this memory temp is an issue or what acceptable tolerances are for the G5 with FCPHD? I am out of ideas and hope that someone out there might have some ideas. +Any advice is appreciated.+It sounds like you may have a piece of corrupt media (or several pieces of corrupt media). First of all, usb is not recommended for working with fcp. Don't think it's the source of your problem, but...
First, generally speaking, project files should reside on your startup disk and all media on other drives.
Are you using any nonstandard codecs or formats?
Are all your drives formatted macosextended? You might want to run diskwarrior on all drives.
Once the above are eliminated, try this. Copy your fcp project file to your startup drive and disconnect the media drive. Open fcp and launch the project. All media will be offline. Save your project. Reconnect your media drive, and launch fcp and the project. Gradually reconnect your media until you find the problem clips. -
Adobe Premiere Elements 0.9 project crash, HELP!
This is the first time I am using these forums, so I hope I posted this in the right sektions.
I need help and solutions for a Project which constantly crashes on my Adobe Premiere Elements 0.9. This program has been awesome and helped me create some projects and videos successfully, up until.... well for about 3 days ago when my latest project crashed when I had just antered and checking the storyboard etc, triggering a "Serious Error" message and then it shuts down. I try again and again, but everytime I try to put something (any sound or video etc) on the storyboard and start working etc the same damn "Serious Error" message and then allways shuts down. It's allways this same and only project (which has worked fine before) that crashes like this...
In an attempt to first solve the problem myself I went through the Premiere Elements 9 files and deleted finnished projects and automatic saved process on projects etc, but still won't work even better... The funny thing is that when I open another project (a finnished project I left saved just in case) and go through the storyboard there and messes around a little and such, it won't crash nor trigger the same message as my latest project. And that program even has some effects on every footageclip on it too, but still it works fine. Haven't touched the program or the program until and since yesterday night to give it some rest but it still won't work, the project just keeps crashing like when and since it first started a few days ago.
I have also read through and tried some things from this Help/Troubleshoot page:
http://helpx.adobe.com/premiere-elements/kb/troubleshoot-damaged-projects-premiere-element s.html
I have so far been doing 1 and 2 of the "Beginning Troubleshooting", otherwise I have been reading it all and such. I am also kinda afraid to do the 3 of the first quests because I worked so hard on this project and even tough it just keeps crushing, I'm afraid to lose it. Other, I have deleted audios and such from my filegallery on my Adobe Premiere Eements, stuff I don't need anymore because its projects are already done. After I did that I also tried to create a new project just for testing. The amazing this about this is that this the new created project I created works just fine, I could do all kinds of the stuff, effects and advanced editing which I did on the same project before it started crushing. Tough I didn't save that test-project since I didn't find a reason to since it worked so good. And so the thing is that I can start and create a new project and start working and do usual stuff on it with no problem, same when I open up another project and do stuff, it all works just fine! It is just this one and only project that keeps crushing with this "Serious Error" message, all the time... Does anybody else have, or has had the same problem? What could the problem and error be and how to fix it?
This crushing project do has some effects on every footageclip/videoclip on it, to set the right mood for the musicvideo I'm making. I am making a musicvideo, and I haven't even done the half of the project/video. The song I am making this musicvideo with is about 00:07:32 in length, and (tough this detail may have no influence or meaning) the music is Symphonic Metal. The actual file of the song is 6,96 MB in size. This is also not the first time I've done such projects with such long songs on this same program either, one of my last videos I managed to successfully make and create a musicvideo with a song which was about 13 minutes and 30 seconds in length, and I also used effects on pretty much every videoclip on that project too.
The current filesize so far on the actual project.prel-file of my project that keeps crushing is 9.73 MB.
I am also using Adobe Premiere Elements and doing this troubleing, crashing project on a PC, a Fujitsu Windows (I believe Windows 7, or even updated to a newer version?). It has a regular ATI-card. The computer also has 2 modems and there's still some pretty GB amount free on them. The PC's main system also has a RAM in 6.00 GB and the operative system is the 64-bites.
In short, the PC should just fine be able to handle Adobe Premiere Elements 0.9 and all its projects, just as it has handled it all before plus all my PC games at that. So it must be something with my Adobe Premiere Elements and that specific project which is the problem, but what is the problem and the serious error and how to fix it?
Could it help to save and create the actual video in this crashing project, delete that project then start a new project, upload and put in the videofile of the crashing project in that new project and then continue from there?
In either cases, I need help with this. Please, help!Thanks so much for your reply, Steve!
Even tough I trust you guys enough here on the official Adobe site/forums to answer those questions as best I can, I am at the same time not very fond of giving away too much information because of safety. I understand I have to If I'm to recieve the accurate answers and solution, but as this is the internet you can never know. But again, I trust you guys enough on here and thus I'll try to answer those questions as best I can, even tough I am not very good with such stuff about computers. The PC I am using is also not only mine, it is the family computer also which me and my whole family uses.
The operating system on my computer (according to the computer propotions etc) is a 64-bites operating system and the computer/PC is also a Windows 7 Home Premium.
The processor the computer/PC have is a Intel(R) Core(TM) i5 CPU and the RAM is 6.00 GB. However, (and I hope I make this understandable because the computer/PC is in swedish)the subscore of RAM in the computer's Performance-Classification/Ranking is 7,5. The processor subscore is 7,3 per second. And the free space? Well, we have two modems, let's say a modem A and a modem B. Adobe Premiere Elements 0.9 is set to save all its stuff etc on modem B, while modem A is the main modem and spaces all main stuff and other things of the computer/PC. Modem A has about 314 GB of free space, while modem B has 207 GB of free space. Modem A's capacity is a total of 489 GB in which 175 GB has been used, the modems filesystem is a NTFS. Modem B is also a NTFS filesystem and its capacity is a total of 439 GB in which 232 GB has been used. And the Disk Cleanup? I believe my that latest ran it for about a few weeks ago. We also have a CCleaner also. But about the Disk Defragmenter, I have no idea. What exactly does a Disk Defragmenter do?
You mean, entering my project that keeps crushing and simply rename it by using "Save As"? If that is what you mean, I dunnow If that actually worked. When I still tried to do stuff and edit the crashing project (tough as said, it hardly took any changes and process before it triggered that message) and then crashed and shut down, and I opened up the program again (trying to open the same project that way), it asked me If I wanted to re-create the missing process from the last crash of the same project. I tried it and it automaticly was renamed to a for example Project.copy. But when I tried to work with that it was to no futher success, the project kept crashing. I haven't renamed the project by "Save As" tough, but I doubt it'll work, I even tried to rename the actual project file in the Adobe Premiere Elements files but nope... the project keeps crashing. But also about the same question, "Save As" under a new name but in its own folder? You mean the actual project folder or Adobe Premiere Elements preview folder of the projects?
My camcorder is pretty old by now, have had it since I turned 15, it has worked pretty good since then. Its model is a Sony Handycam, Carl Zeiss Vario-Tessar OPTICAL 20x. Even tough the last thing maybe doesn't say anything, this is all I know about my camcorder, except that it is a model no. DCR-HC17E PAL. But in that Project which keeps crashing, there are only a few actual camcorder clips used as I am making a Game-MusicVideo and most of the footage of the Video-game (actually a PC game) I'm making a musicvideo of is downloaded from Youtube mostly from a guy I asked permission for to download his recorded footage of the game. I used a Youtube downloader called ClipConverter. As I don't have a SD card I cannot make this footage myself. But some footage I recorded on my camcorder, but If I can find high quality clips and get them, I will. The other footages is actual official trailers of the PC games which also was downloaded from the net. But I can give you the stuffs filetypes and hoping that may help. The downloaded footage which was downloaded by this ClipConverter, are MP4 files. The other stuff (which were official trailers) and most of them are also MP4 files, the others are QuickTime-film files. Many of these downloaded footages and trailers are also in HD quality, at least some of them I think.
The actual filetype ofthe footage I myself recorded with my camcorder are, well.... it says Videoclip in the file. Maybe it is AVI?
The project settings? You mean the settings you set at first when starting as a new project? The general settings are, in editingsettings it is AVCHD 270p square pixel. This is kinda hard for me to tell since everything is in swedish in my program. But these settings has worked perfectly before, same with all files, footages and videoclips I have been using, also all the soundfiles etc. Even the actual crashing project worked perfectly before it started crashing... So why does it so suddenly start crashing now?
The audio is a song I copied directly from its album and CD into the computer/PC and it seems to be in WMA format in filetype.
And lastly, no I haven't rendered the timeline of the project ever, not even on my other projects. What does the rendering do and is useful for? I have very little knowledge of it. Other, I keep the Timeline mode open all the time because I can edit my videos much better with it, but perhaps that editing method make little influence of the actual problem.
Other, yesterday when writing the post and topic, I forgot to mention that I restarded my computer right after I created a new project, that testing project. When finnished with the testing I restarted the computer. Since then I haven't touched the crashing project since now tonight, when checking its settings for this post. I am also right now trying to create and save the actual videofile of it, saving it on my computer. I'll soon see If it's successful without any crashing interruptions, plus that the video itself works and is smooth when I'll play it on Windows Media Player like all the rest of my other videos. I do this just in case I must create a new project to be able to continue with my musicvideo, as the first part of it I worked very hard on.
Other and again, I am still puzzled about why this is even happening, that this project which worked perfectly fine before, just suddenly starts triggering that "Serious Error" message and crashes. And in this program which worked so perfect before. Has this happened to anyone else before? Has anyone else experienced the same issue I have? Is this a knowledgable issue which has solutions and ways to fix it?... :/ -
Cannot open Robohelp 8 project in Robohelp 9
I cannot open my old Robohelp 8 projects from Robohelp 9. When I open it, it shows me a prompt to make a backup and upgrade the project. Then I click Upgrade, it returns an error:
"open project was cancelled or the application was unable tp load the database for <path to my project>"
Creating or opening new projects in the 9 format works fine.
The old Robohelp project was created on a different PC. I just copied the whole folder to a new PC with Robohelp 9. The oroject is not corrupted I can still open it on my old PC with RH8.
Any suggestions how to fix that?
ThanksThere isn't a Save As option but usually it is as simple as copying the project from one location to another.
No it doesn't write an absolute path as if it did that, none of us could move projects.
Do you have a second machine (not with SSD) that you can install RoboHelp 9 on in trial mode? With that you could perhaps put the project on an external hard disk and prove it works there as it does for me?
Are you copying just the project out of your profile? So C:\Users\XXXXX\Documents\My RoboHelp Projects\Project1 becomes D:\Project1. If not, try that.
After moving, getting the error and trashing the CPD, do you get the error again if you reopen after that?
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge -
My project crashes Final Cut Pro on multiple machines
I'm just getting ready to wrap up a project and I now can not render or export anything without the spinning beach ball and then either a "force quit" or it crashes for me. I'm running FCP 6.0.4 on a DVCPro HD 1080i60 Project and Sequence. The entire timeline is 4 minutes but all of the clips not covered with b-roll are keyed in Motion using the "send to" command. Everything was working fine until yesterday when FCP became very buggy, crashes randomly and often. I can view all of the keyed clips in the FCP timeline, they used to render out and play fine but not anymore. I've cleaned up all of the clips in Motion after I started having issues like removing extra layers that were turned off before exporting. Occasionally the clips do randomly show up pink or purple in the timeline and I have to do a 'send to' Motion again to get the keyed clip back. I've opened the project on 2 - G5's as well and the project crashes. CPU usage is minimal when it locks up.
Any help here would be great. Thanks!
- GregDo a test. With the range tool make a very short range selection of your project and Share>DVD. In the export dialoge >Settings, choose Hard Drive for Output Device. Click on the Add button for menu background. When the next window appears, hit cancel. See if it exports and burns a disk image, If it does, try the complete project.
BTW, is your project length 79 minutes or 79 seconds?
Russ -
Compressor 4 crashes on opening keep getting this warning: The application “Compressor” unexpectedly quit while trying to restore its windows. Do you want to try to restore its windows again? Tried Restoring windows. It crashes again. Tried not = Same result. This is the first time I've actually used the app although I purchased it back in April (I think). I had my first longform project completed in FCPX and tried sending it to Compressor 4 and got this result over and over again.
Steve,
Sorry to say I've not had any success in getting Compressor 4 to work. I've tried every suggestion mentioned earlier on this topic to no avail. Compressor 4 is dead in the water. On the last two projects I had to go back to Compressor 3.x.xx to complete the projects. The only hint that I have of wha may have happened concerns something I did early on. When I bought this computer I decided to replace the hard drive with a larger one. Since I already had my software up and working on the drive that came with the computer I decided to clone everything to the new larger drive. As I recall, Compressor 4 worked on the original drive but it doesn't work on this cloned version. So maybe there is a relationship there. I haven't had a chance yet to reinstall my old drive and see if C 4 works on it. If it does work then I know the source of the problem but not how to fix it on the new drive. Did you do anything like cloning your drive recently too? It's just a thought and may not lead anywhere but later this week when I catch a break I'll give the old drive a try and will post my results.
Thanks,
Peter -
Robohelp 7 open Robohelp 9 project?
as I search through internet, I understand that robohelp 7 unable to open robohelp 9 project
we have two robohelp 7 licenses and three robohelp 9 licenses
when working on project in robohelp 9, it need to upgrade the project, but robohelp 7 is unable to open the project after upgraded
Is it any way opening Robohelp 9 project(converted from version 7 project) in Robohelp 7?
Is it upgrade Robohelp 7 to 9 is the only way? We do not wish to upgrade is because i am wondering if later Adobe release robohelp 10, and by that time we need more robohelp license and we purchased additional license, we will need to upgrade all other old robohelp product?Hello again
Yep, conditional tagging is handled in the project before you compile or generate, so indeed they would be lost as would any information you excluded via the tab and build expression.
Not perfect, but at least you get a project you may continue editing in version 7.
Cheers... Rick
Helpful and Handy Links
RoboHelp Wish Form/Bug Reporting Form
Begin learning RoboHelp HTML 7, 8 or 9 within the day!
Adobe Certified RoboHelp HTML Training
SorcerStone Blog
RoboHelp eBooks -
After effect 2014 is crashing again and again pls... help
My after effects 2014 is crashing again and again after applying any effect
my laptop config. is as follow
Model alienware 17x r4
i7 extreme edition
16gb ram
1.5tb hard disk
2gb nvidia 660
windows 8.1
Pls.....help its urgentUpdate your graphics driver. Anything beyond that would require much more info about your project settings, footage used and whatnot.
Mylenium -
Make a decompiled CHM into a Robohelp 8 Project
Hello everyone,
I apologize for the novice level of my question, I've only started using Robohelp a few days ago. My company wants me to update our software's help file (it was originally created in RH6, I believe). Unfortunately the last person to work on it no longer works for us, and he apparently has all copies of the project files used to compile it originally.
I found how to decompile the CHM into its component files but when I decompiled it I didn't get a XPJ project file. I'm unsure how to make this project "whole" again, is there any way to re-integrate this into a project (hopefully retaining the TOC, Indexes, images, links, etc.) or do I have to create a new project and import each file individually?
I searched these forums and Peter Grainge's site for a while but couldn't find an answer, I apologize if this has already come up and I missed it. Any help or guidance you folks can give me will be greatly appreciated.
Dan AmatoHi there
Did you catch the Reverse Engineering page on Peter's site?
Click here to view the gnireenignE esreveR topic on Peter's site
Cheers... Rick
Helpful and Handy Links
RoboHelp Wish Form/Bug Reporting Form
Begin learning RoboHelp HTML 7 or 8 within the day - $24.95!
Adobe Certified RoboHelp HTML Training
SorcerStone Blog
RoboHelp eBooks -
Captivate 7 Project Crashing iPad Safari
I have a particular slide in my HTML5-published Captivate 7 project that repeatedly crashes my 2nd generation iPad's browser (Safari).
The slide contains 18 png images (total size <3mb), nine text entry boxes and 9 click boxes. Shuffling some of the content along the timeline to stagger the amount that loads simultaneously helps the slide to load without crashing but as soon as I tap one of the hotspots the browser crashes again.
It seems like a memory issue on the iPad and I was wondering whether anyone else had encountered, and overcome a similar issue and how they did it?
This is a major concern for me as these are basic things that I am trying to achieve and it seems as though I'm spending more time trouble shooting my content than actually developing it at the moment.
Thanks.I've been carrying out further tests based on my post above and have a few more details.
The items that seem to be causing the problems are nine individual groups, each containing an image, an image button, a text caption and three smart shapes. None of the groups are set to be visible on output and are shown using an advanced action (show) that is attached to one of nine click boxes on the slide. Once a group has been shown it can be hidden again by clicking the image button within the group, again using an advanced action (hide).
To test that this was the cause of the issue I first removed all of the hidden groups from the page and published the project. Safari on my iPad didn't crash when there were no hidden groups.
Next I gradually added one group at a time back in to my project, finding that it didn't crash with five hidden groups but it did with any more.
I hope that this is of some interest and that there might soon be a way to get around this. Personally I think that the addition of a popup slidelet that is native to captivate might be the way forward.
Although the post I'm linking to here started off discussing rollover slidelets there is some discussion relating to pop ups towards the end: http://forums.adobe.com/message/4663740#4663740 -
PE 13 crashes due to incompatible video driver detected. Running on Win 7 SP1 with ATI 540v video card/driver. Deleting bad driver file in adobe program data does not fix the problem, it simply replaces the text file and crashes again. My video driver is just fine. Any help out there?
rb
Your video card driver may be fine for something, but just not compatible with Premiere Elements 13/13.1.
For those with the display card error, the answers include
a. assure your video card/graphics card driver version is up to date according to the web site of the manufacturer of the card -
if necessary consider a driver roll back.
b. determine in Device Manager/Display Adapters if the computer is using 2 cards instead of 1
c. delete the BadDrivers.txt file
the rationale for that deletion is found in post 10 of the following older post...principle applies to 13 as well as 9.
Re: Premiere Elements 9 Tryout Serious Display Problem
Have you looked for computer ATI card settings that might be more compatible with Premiere Elements 13/13.1?
When is the program crashing - just opening a new project or rather crashing if editing a particular video format at the Timeline level?
ATR -
I have repeatedly clicked repair just to have it reopen and then crash again.
This is the error message:
Process: iPhoto [7170]
Path: /Applications/iPhoto.app/Contents/MacOS/iPhoto
Identifier: com.apple.iPhoto
Version: 9.2.1 (9.2.1)
Build Info: iPhotoProject-628000000000000~1
App Item ID: 408981381
App External ID: 4641130
Code Type: X86 (Native)
Parent Process: launchd [246]
Date/Time: 2012-03-06 18:38:34.883 -0800
OS Version: Mac OS X 10.7.3 (11D50b)
Report Version: 9
Interval Since Last Report: 179095 sec
Crashes Since Last Report: 10
Per-App Interval Since Last Report: 5360 sec
Per-App Crashes Since Last Report: 9
Anonymous UUID: E9F9CCA2-3EF4-42BB-A28B-E27CACBB6C68
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
VM Regions Near 0:
--> __PAGEZERO 0000000000000000-0000000000001000 [ 4K] ---/--- SM=NUL /Applications/iPhoto.app/Contents/MacOS/iPhoto
__TEXT 0000000000001000-0000000000d1b000 [ 13.1M] r-x/rwx SM=COW /Applications/iPhoto.app/Contents/MacOS/iPhoto
Application Specific Information:
objc[7170]: garbage collection is OFF
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.apple.iPhoto 0x00824501 0x1000 + 8533249
1 com.apple.iPhoto 0x001678d6 0x1000 + 1468630
2 com.apple.Foundation 0x9854ae25 __-[NSNotificationCenter addObserver:selector:name:object:]_block_invoke_1 + 49
3 com.apple.CoreFoundation 0x912d3cb3 ___CFXNotificationPost_block_invoke_1 + 275
4 com.apple.CoreFoundation 0x9129ea38 _CFXNotificationPost + 2776
5 com.apple.Foundation 0x98536012 -[NSNotificationCenter postNotificationName:object:userInfo:] + 92
6 com.apple.Foundation 0x9854b2a6 -[NSNotificationCenter postNotificationName:object:] + 55
7 com.apple.iPhoto 0x0016716a 0x1000 + 1466730
8 com.apple.iPhoto 0x00167111 0x1000 + 1466641
9 com.apple.iPhoto 0x0015c6f4 0x1000 + 1423092
10 com.apple.CoreFoundation 0x912ebb6d __invoking___ + 29
11 com.apple.CoreFoundation 0x912ebaa9 -[NSInvocation invoke] + 137
12 com.apple.RedRock 0x02355e61 -[RKInvoker _invokeTarget:] + 33
13 com.apple.CoreFoundation 0x912e8de1 -[NSObject performSelector:withObject:] + 65
14 com.apple.Foundation 0x98587e40 __NSThreadPerformPerform + 503
15 com.apple.CoreFoundation 0x912603df __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 15
16 com.apple.CoreFoundation 0x9125fd96 __CFRunLoopDoSources0 + 246
17 com.apple.CoreFoundation 0x91289c68 __CFRunLoopRun + 1112
18 com.apple.CoreFoundation 0x9128947c CFRunLoopRunSpecific + 332
19 com.apple.CoreFoundation 0x91289328 CFRunLoopRunInMode + 120
20 com.apple.HIToolbox 0x9796317f RunCurrentEventLoopInMode + 318
21 com.apple.HIToolbox 0x9796a4e7 ReceiveNextEventCommon + 381
22 com.apple.HIToolbox 0x9796a356 BlockUntilNextEventMatchingListInMode + 88
23 com.apple.AppKit 0x0292ba9c _DPSNextEvent + 678
24 com.apple.AppKit 0x0292b306 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 113
25 com.apple.AppKit 0x02927675 -[NSApplication run] + 911
26 com.apple.AppKit 0x02bbb261 NSApplicationMain + 1054
27 com.apple.iPhoto 0x0001159a 0x1000 + 66970
28 com.apple.iPhoto 0x00010a29 0x1000 + 64041
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x9735090a kevent + 10
1 libdispatch.dylib 0x91d86c58 _dispatch_mgr_invoke + 969
2 libdispatch.dylib 0x91d856a7 _dispatch_mgr_thread + 53
Thread 2:
0 libsystem_kernel.dylib 0x9734f83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x947e5e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x947e5f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x985c53f7 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9858b806 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9858b6da -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x01d57702 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x01d566b0 -[XTThread run:] + 416
8 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
9 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
11 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 3:
0 libsystem_kernel.dylib 0x9734dc22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9734d1f6 mach_msg + 70
2 com.apple.CoreFoundation 0x91280c7a __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x91289da4 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x9128947c CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x91289328 CFRunLoopRunInMode + 120
6 com.apple.Foundation 0x9853f4e3 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 273
7 com.apple.proxtcore 0x01d58aed -[XTRunLoopThread run:] + 509
8 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
9 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
11 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 4:
0 libsystem_kernel.dylib 0x9734dc22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9734d1f6 mach_msg + 70
2 com.apple.CoreFoundation 0x91280c7a __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x91289da4 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x9128947c CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x91289328 CFRunLoopRunInMode + 120
6 com.apple.Foundation 0x9853f4e3 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 273
7 com.apple.proxtcore 0x01d58aed -[XTRunLoopThread run:] + 509
8 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
9 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
11 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 5:
0 libsystem_kernel.dylib 0x9734f83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x947e5e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x947e5f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x985c53f7 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9858b806 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9858b6da -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x01d57702 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x01d566b0 -[XTThread run:] + 416
8 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
9 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
11 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 6:
0 libsystem_kernel.dylib 0x9734f83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x947e5e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x947e5f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x985c53f7 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9858b806 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9858b6da -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x01d57702 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x01d566b0 -[XTThread run:] + 416
8 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
9 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
11 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 7:
0 libsystem_kernel.dylib 0x9734f83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x947e5e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x947e5f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x985c53f7 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9858b806 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9858b6da -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x01d57702 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x01d566b0 -[XTThread run:] + 416
8 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
9 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
11 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 8:
0 libsystem_kernel.dylib 0x9734f83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x947e5e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x947e5f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x985c53f7 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9858b806 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9858b6da -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x01d57702 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x01d566b0 -[XTThread run:] + 416
8 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
9 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
11 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 9:
0 libsystem_kernel.dylib 0x9734dc22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9734d1f6 mach_msg + 70
2 com.apple.CoreFoundation 0x91280c7a __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x91289da4 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x9128947c CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x91289328 CFRunLoopRunInMode + 120
6 com.apple.Foundation 0x9853f4e3 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 273
7 com.apple.proxtcore 0x01d58aed -[XTRunLoopThread run:] + 509
8 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
9 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
11 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 10:
0 libsystem_kernel.dylib 0x9734f83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x947e5e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x947e5f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x985c53f7 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9858b806 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9858b6da -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x01d57702 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x01d566b0 -[XTThread run:] + 416
8 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
9 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
11 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 11:
0 libsystem_kernel.dylib 0x9734f83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x947e5e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x947e5f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x985c53f7 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9858b806 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9858b6da -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x01d57702 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x01d566b0 -[XTThread run:] + 416
8 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
9 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
11 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 12:
0 libsystem_kernel.dylib 0x9734f83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x947e5e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x947e5f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x985c53f7 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9858b806 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9858b6da -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x01d57702 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x01d566b0 -[XTThread run:] + 416
8 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
9 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
11 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 13:
0 libsystem_kernel.dylib 0x9734f83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x947e5e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x947e5f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x985c53f7 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9858b806 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9858b6da -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x01d57702 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x01d566b0 -[XTThread run:] + 416
8 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
9 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
11 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 14:
0 libsystem_kernel.dylib 0x9734f83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x947e5e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x947e5f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x985c53f7 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9858b806 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9858b6da -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x01d57702 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x01d566b0 -[XTThread run:] + 416
8 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
9 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
11 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 15:
0 libsystem_kernel.dylib 0x9734f83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x947e5e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x947e5f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x985c53f7 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9858b806 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9858b6da -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x01d57702 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x01d566b0 -[XTThread run:] + 416
8 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
9 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
11 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 16:
0 libsystem_kernel.dylib 0x9734f83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x947e5e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x947e5f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x985c53f7 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9858b806 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9858b6da -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x01d57702 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x01d566b0 -[XTThread run:] + 416
8 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
9 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
11 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 17:
0 libsystem_kernel.dylib 0x9734f83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x947e5e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x947e5f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x985c53f7 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9858b806 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9858b6da -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x01d57702 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x01d566b0 -[XTThread run:] + 416
8 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
9 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
11 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 18:
0 libsystem_kernel.dylib 0x9734f83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x947e5e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x947e5f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x985c53f7 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9858b806 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9858b6da -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x01d57702 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x01d566b0 -[XTThread run:] + 416
8 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
9 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
11 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 19:
0 libsystem_kernel.dylib 0x9734f83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x947e5e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x947e5f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x985c53f7 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9858b806 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9858b6da -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x01d57702 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x01d566b0 -[XTThread run:] + 416
8 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
9 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
11 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 20:
0 libsystem_kernel.dylib 0x9734f83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x947e5e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x947e5f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x985c53f7 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9858b806 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9858b6da -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x01d57702 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x01d566b0 -[XTThread run:] + 416
8 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
9 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
11 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 21:
0 libsystem_kernel.dylib 0x9734f83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x947e5e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x947e5f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x985c53f7 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9858b806 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9858b6da -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x01d57702 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x01d566b0 -[XTThread run:] + 416
8 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
9 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
11 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 22:
0 libsystem_kernel.dylib 0x9734f83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x947e5e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x947e5f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x985c53f7 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9858b806 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9858b6da -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x01d57702 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x01d566b0 -[XTThread run:] + 416
8 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
9 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
11 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 23:
0 libsystem_kernel.dylib 0x9734f83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x947e5e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x947e5f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x985c53f7 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9858b806 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9858b6da -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proxtcore 0x01d57702 -[XTMsgQueue waitForMessage] + 50
7 com.apple.proxtcore 0x01d566b0 -[XTThread run:] + 416
8 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
9 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
10 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
11 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 24:
0 libsystem_kernel.dylib 0x973505fa __fsync + 10
1 com.apple.iLifeSQLAccess 0x01e4892e unixSync + 62
2 com.apple.iLifeSQLAccess 0x01e4882e syncJournal + 382
3 com.apple.iLifeSQLAccess 0x01e4840d sqlite3PagerCommitPhaseOne + 1645
4 com.apple.iLifeSQLAccess 0x01e2f1d5 sqlite3BtreeCommitPhaseOne + 581
5 com.apple.iLifeSQLAccess 0x01e2e74d sqlite3VdbeHalt + 1885
6 com.apple.iLifeSQLAccess 0x01e25a2e sqlite3VdbeExec + 12414
7 com.apple.iLifeSQLAccess 0x01e2262c sqlite3_step + 2812
8 com.apple.iLifeSQLAccess 0x01e4b1fe -[HgKPreparedSql updateWithArgs:] + 174
9 com.apple.iLifeSQLAccess 0x01e707d3 -[HgKDatabaseManager commitAndBeginNewTransaction] + 291
10 com.apple.iLifeSQLAccess 0x01e7069a -[HgSqlCommitOperation main] + 42
11 com.apple.iLifeSQLAccess 0x01e70661 -[HgSqlCommitOperation run] + 33
12 com.apple.iLifeSQLAccess 0x01e650d2 -[RAOperationQueueImpl _runOperationFromList:sourceList:] + 114
13 com.apple.iLifeSQLAccess 0x01e49e0d -[RAOperationQueueImpl _workThread] + 285
14 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
15 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
16 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
17 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 25:
0 libsystem_kernel.dylib 0x973505fa __fsync + 10
1 com.apple.iLifeSQLAccess 0x01e4892e unixSync + 62
2 com.apple.iLifeSQLAccess 0x01e48895 syncJournal + 485
3 com.apple.iLifeSQLAccess 0x01e4840d sqlite3PagerCommitPhaseOne + 1645
4 com.apple.iLifeSQLAccess 0x01e2f1d5 sqlite3BtreeCommitPhaseOne + 581
5 com.apple.iLifeSQLAccess 0x01e2e74d sqlite3VdbeHalt + 1885
6 com.apple.iLifeSQLAccess 0x01e25a2e sqlite3VdbeExec + 12414
7 com.apple.iLifeSQLAccess 0x01e2262c sqlite3_step + 2812
8 com.apple.iLifeSQLAccess 0x01e4b1fe -[HgKPreparedSql updateWithArgs:] + 174
9 com.apple.iLifeSQLAccess 0x01e707d3 -[HgKDatabaseManager commitAndBeginNewTransaction] + 291
10 com.apple.iLifeSQLAccess 0x01e7069a -[HgSqlCommitOperation main] + 42
11 com.apple.iLifeSQLAccess 0x01e70661 -[HgSqlCommitOperation run] + 33
12 com.apple.iLifeSQLAccess 0x01e650d2 -[RAOperationQueueImpl _runOperationFromList:sourceList:] + 114
13 com.apple.iLifeSQLAccess 0x01e49e0d -[RAOperationQueueImpl _workThread] + 285
14 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
15 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
16 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
17 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 26:
0 libsystem_kernel.dylib 0x9734f83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x947e5e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x947e5f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x985c53f7 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9858b806 -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9858b6da -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.RedRock 0x02333ac1 -[RKAsyncImageRenderer _backgroundRenderThread:] + 177
7 com.apple.CoreFoundation 0x912f128a -[NSObject performSelector:] + 58
8 com.apple.proxtcore 0x01d61626 -[XTThreadSendOnlyDetached _detachedMessageHandler:] + 166
9 com.apple.CoreFoundation 0x912e8de1 -[NSObject performSelector:withObject:] + 65
10 com.apple.proxtcore 0x01d58cb5 -[XTSubscription postMessage:] + 181
11 com.apple.proxtcore 0x01d58406 -[XTDistributor distributeMessage:] + 726
12 com.apple.proxtcore 0x01d57f55 -[XTThread handleMessage:] + 1285
13 com.apple.proxtcore 0x01d566c6 -[XTThread run:] + 438
14 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
15 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
16 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
17 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 27:
0 libsystem_kernel.dylib 0x9735002e __workq_kernreturn + 10
1 libsystem_c.dylib 0x947e3ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x947e56fe start_wqthread + 30
Thread 28:
0 libsystem_kernel.dylib 0x9734f83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x947e5e21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x9479642c pthread_cond_wait$UNIX2003 + 71
3 com.apple.Foundation 0x98594c1c -[NSCondition wait] + 304
4 com.apple.iPhoto 0x0005c66a 0x1000 + 374378
5 com.apple.iPhoto 0x0005c5c2 0x1000 + 374210
6 com.apple.CoreFoundation 0x912ebb6d __invoking___ + 29
7 com.apple.CoreFoundation 0x912ebaa9 -[NSInvocation invoke] + 137
8 com.apple.RedRock 0x02355e61 -[RKInvoker _invokeTarget:] + 33
9 com.apple.RedRock 0x023676c4 -[RKInvoker _invokeTargetWithPool:] + 68
10 com.apple.CoreFoundation 0x912e8de1 -[NSObject performSelector:withObject:] + 65
11 com.apple.proxtcore 0x01d61626 -[XTThreadSendOnlyDetached _detachedMessageHandler:] + 166
12 com.apple.CoreFoundation 0x912e8de1 -[NSObject performSelector:withObject:] + 65
13 com.apple.proxtcore 0x01d58cb5 -[XTSubscription postMessage:] + 181
14 com.apple.proxtcore 0x01d58406 -[XTDistributor distributeMessage:] + 726
15 com.apple.proxtcore 0x01d57f55 -[XTThread handleMessage:] + 1285
16 com.apple.proxtcore 0x01d566c6 -[XTThread run:] + 438
17 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
18 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
19 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
20 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 29:
0 libsystem_c.dylib 0x947b9be1 memmove$VARIANT$sse3x + 35
1 com.apple.ImageIO.framework 0x94536a88 _CGImageSourceBindToPlugin + 300
2 com.apple.ImageIO.framework 0x9453694b CGImageSourceGetType + 55
3 com.apple.iPhoto 0x000b13b1 0x1000 + 721841
4 com.apple.iPhoto 0x003ed5cd 0x1000 + 4113869
5 com.apple.iPhoto 0x000b0d17 0x1000 + 720151
6 com.apple.iPhoto 0x0033e710 0x1000 + 3397392
7 com.apple.iPhoto 0x000b05c7 0x1000 + 718279
8 com.apple.iPhoto 0x001668b9 0x1000 + 1464505
9 com.apple.iLifeFaceRecognition 0x012a3f3d -[FaceRecognitionManager detectFacesInPhoto:userInfo:options:delegate:context:] + 141
10 com.apple.RedRock 0x023af7c5 -[RKFaceDetectionWorker detectFacesForMaster:aggressive:] + 1125
11 com.apple.iPhoto 0x009ea972 0x1000 + 10393970
12 com.apple.RedRock 0x023af218 -[RKFaceDetectionWorker performJob:] + 440
13 com.apple.CoreFoundation 0x912e8de1 -[NSObject performSelector:withObject:] + 65
14 com.apple.proxtcore 0x01d58cb5 -[XTSubscription postMessage:] + 181
15 com.apple.proxtcore 0x01d58406 -[XTDistributor distributeMessage:] + 726
16 com.apple.proxtcore 0x01d57f55 -[XTThread handleMessage:] + 1285
17 com.apple.proxtcore 0x01d566c6 -[XTThread run:] + 438
18 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
19 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
20 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
21 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 30:
0 libsystem_kernel.dylib 0x9734dc22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9734d1f6 mach_msg + 70
2 com.apple.iLifeSQLAccess 0x01e49f41 -[RALatchTrigger wait] + 81
3 com.apple.iLifeSQLAccess 0x01e49dc9 -[RAOperationQueueImpl _workThread] + 217
4 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
5 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
6 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
7 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 31:
0 libsystem_kernel.dylib 0x9734ee12 __accept + 10
1 com.apple.iPhoto 0x00438f20 0x1000 + 4423456
2 com.apple.iPhoto 0x004833d1 0x1000 + 4727761
3 com.apple.iPhoto 0x0048376e 0x1000 + 4728686
4 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
5 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 32:: com.apple.CFSocket.private
0 libsystem_kernel.dylib 0x9734fb42 __select + 10
1 com.apple.CoreFoundation 0x912d7ee5 __CFSocketManager + 1557
2 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
3 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 33:
0 libsystem_kernel.dylib 0x9735002e __workq_kernreturn + 10
1 libsystem_c.dylib 0x947e3ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x947e56fe start_wqthread + 30
Thread 34:: JavaScriptCore::BlockFree
0 libsystem_kernel.dylib 0x9734f83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x947e5e21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x947963e0 pthread_cond_timedwait$UNIX2003 + 70
3 com.apple.JavaScriptCore 0x99c4c9dc ***::ThreadCondition::timedWait(***::Mutex&, double) + 156
4 com.apple.JavaScriptCore 0x99e40f03 JSC::Heap::blockFreeingThreadMain() + 323
5 com.apple.JavaScriptCore 0x99e40f3f JSC::Heap::blockFreeingThreadStartFunc(void*) + 15
6 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
7 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 35:: CVDisplayLink
0 libsystem_kernel.dylib 0x9734f83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x947e5e21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x9479642c pthread_cond_wait$UNIX2003 + 71
3 com.apple.CoreVideo 0x92060529 CVDisplayLink::runIOThread() + 945
4 com.apple.CoreVideo 0x92060161 _ZL13startIOThreadPv + 160
5 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
6 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 36:
0 libsystem_kernel.dylib 0x9734f83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x947e5e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x947e5f7b pthread_cond_timedwait_relative_np + 47
3 com.apple.CoreServices.CarbonCore 0x914883ef TSWaitOnConditionTimedRelative + 178
4 com.apple.CoreServices.CarbonCore 0x91488165 TSWaitOnSemaphoreCommon + 490
5 com.apple.CoreServices.CarbonCore 0x91487f76 TSWaitOnSemaphoreRelative + 24
6 com.apple.QuickTimeComponents.component 0x9b4b5be6 0x9aec9000 + 6212582
7 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
8 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 37:
0 libsystem_kernel.dylib 0x9735002e __workq_kernreturn + 10
1 libsystem_c.dylib 0x947e3ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x947e56fe start_wqthread + 30
Thread 38:: com.apple.NSURLConnectionLoader
0 libsystem_kernel.dylib 0x9734dc22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9734d1f6 mach_msg + 70
2 com.apple.CoreFoundation 0x91280c7a __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x91289da4 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x9128947c CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x91289328 CFRunLoopRunInMode + 120
6 com.apple.Foundation 0x9859f0f8 +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 378
7 com.apple.Foundation 0x98592e59 -[NSThread main] + 45
8 com.apple.Foundation 0x98592e09 __NSThread__main__ + 1582
9 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
10 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 39:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x9734f83e __psynch_cvwait + 10
1 libsystem_c.dylib 0x947e5e78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9478d82a pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x9b5d7b7d 0x9aec9000 + 7400317
4 libsystem_c.dylib 0x947e1ed9 _pthread_start + 335
5 libsystem_c.dylib 0x947e56de thread_start + 34
Thread 40:
0 libsystem_kernel.dylib 0x9735002e __workq_kernreturn + 10
1 libsystem_c.dylib 0x947e3ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x947e56fe start_wqthread + 30
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00008c93 ebx: 0x16b25520 ecx: 0x00d55428 edx: 0x001414f0
edi: 0x00000000 esi: 0x00823e01 ebp: 0xbfffe138 esp: 0xbfffdfd0
ss: 0x00000023 efl: 0x00010282 eip: 0x00824501 cs: 0x0000001b
ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f
cr2: 0x00000000
Logical CPU: 0
Binary Images:
0x1000 - 0xd1afeb com.apple.iPhoto (9.2.1 - 9.2.1) <D139F133-4990-3B0E-8017-83D9D729E302> /Applications/iPhoto.app/Contents/MacOS/iPhoto
0xe83000 - 0xf63fe7 org.python.python (2.6.7 - 2.6.7) <61DBA92A-C39A-3A52-86F2-59CF9D310CB4> /System/Library/Frameworks/Python.framework/Versions/2.6/Python
0xfae000 - 0x114effb com.apple.geode (1.5 - 151.51) <28D29759-F356-3608-B9CF-3031F3299B1B> /Applications/iPhoto.app/Contents/Frameworks/Geode.framework/Versions/A/Geode
0x11ee000 - 0x11f0fff com.apple.iLifePhotoStreamConfiguration (2.2 - 2.2) <4FA61CE9-1718-3E07-9896-0023A2A49699> /Applications/iPhoto.app/Contents/Frameworks/iLifePhotoStreamConfiguration.fram ework/Versions/A/iLifePhotoStreamConfiguration
0x11f6000 - 0x1205fff com.apple.iLifeAssetManagement (2.0 - 2.33) <8346DE35-5F86-3338-9913-B035B3EE5435> /Applications/iPhoto.app/Contents/Frameworks/iLifeAssetManagement.framework/Ver sions/A/iLifeAssetManagement
0x1212000 - 0x123affb com.apple.iPhoto.Tessera (1.1 - 60.10) <7BA9184E-0A00-3083-8322-772ECBDD30C9> /Applications/iPhoto.app/Contents/Frameworks/Tessera.framework/Versions/A/Tesse ra
0x124b000 - 0x1272ffb com.apple.iPhoto.Tellus (1.3 - 60.10) <4AABB0BC-AC97-3EE4-BF0F-D8499DDB57C0> /Applications/iPhoto.app/Contents/Frameworks/Tellus.framework/Versions/A/Tellus
0x1287000 - 0x1291fff com.apple.iphoto.AccountConfigurationPlugin (1.2 - 1.2) <3B68F126-D783-3F86-AF04-A0F6A459BE67> /Applications/iPhoto.app/Contents/Frameworks/AccountConfigurationPlugin.framewo rk/Versions/A/AccountConfigurationPlugin
0x129c000 - 0x12b2ff3 com.apple.iLifeFaceRecognition (1.0 - 21.1) <6D28B7F2-7A33-3547-856F-EB19EF8C81F0> /Applications/iPhoto.app/Contents/Frameworks/iLifeFaceRecognition.framework/Ver sions/A/iLifeFaceRecognition
0x12c0000 - 0x12cefff com.apple.opengl (1.7.6 - 1.7.6) <5EF9685C-F8B2-3B22-B291-8012761E9AC8> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x12d6000 - 0x1592ff3 com.apple.security (7.0 - 55110) <2F4FCD65-2A30-3330-99DE-91FE1F78B9FB> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x1689000 - 0x16b5ffb com.apple.DiscRecordingUI (6.0.3 - 6030.4.1) <A80992AB-240C-359B-80B7-773FF6040205> /System/Library/Frameworks/DiscRecordingUI.framework/Versions/A/DiscRecordingUI
0x16ce000 - 0x16d0fff com.apple.ExceptionHandling (1.5 - 10) <7C514CC4-7951-31CA-AEB3-D4AF49F44AE7> /System/Library/Frameworks/ExceptionHandling.framework/Versions/A/ExceptionHand ling
0x16d6000 - 0x188aff3 libicucore.A.dylib (46.1.0 - compatibility 1.0.0) <6AD14A51-AEA8-3732-B07B-DEA37577E13A> /usr/lib/libicucore.A.dylib
0x1909000 - 0x1914fff com.apple.UpgradeChecker (9.2 - 9.2) <2040F6E1-7E77-3C64-8B2C-F3B9503C7402> /Applications/iPhoto.app/Contents/Frameworks/UpgradeChecker.framework/Versions/ A/UpgradeChecker
0x191c000 - 0x191cfff com.apple.iLifeSlideshow (2.3.0 - 847) <C4B7D4F3-D687-3AF6-9561-FE4C66F05BE2> /Applications/iPhoto.app/Contents/Frameworks/iLifeSlideshow.framework/Versions/ A/iLifeSlideshow
0x191f000 - 0x1b95ffb com.apple.iLifePageLayout (1.3 - 150.37) <F812CBEA-99AA-3B62-BEB8-FEC8FCA3A6ED> /Applications/iPhoto.app/Contents/Frameworks/iLifePageLayout.framework/Versions /A/iLifePageLayout
0x1c5e000 - 0x1cf9ff7 com.apple.MobileMe (11 - 1.0.3) <BCE66DE5-97D5-3E78-AC9C-17353AFA6A34> /Applications/iPhoto.app/Contents/Frameworks/MobileMe.framework/Versions/A/Mobi leMe
0x1d53000 - 0x1db3fff com.apple.proxtcore (1.3 - 140.57) <37B97974-E262-3CA8-AF41-2A522C849E82> /Applications/iPhoto.app/Contents/Frameworks/ProXTCore.framework/Versions/A/Pro XTCore
0x1e05000 - 0x1ee4ff3 com.apple.iLifeSQLAccess (1.6 - 30.12) <22409124-4ECA-3EEA-ADF5-7425D6FCD8E3> /Applications/iPhoto.app/Contents/Frameworks/iLifeSQLAccess.framework/Versions/ A/iLifeSQLAccess
0x1f12000 - 0x1f3efef com.apple.ProUtils (1.1 - -
Folders and topics are inexplicably deleted from my RoboHelp 9 project
A month ago, my company purchased the latest Adobe Technical Communication Suite and I started a new RoboHelp 9 project. To help keep track of my many topics, I created several folders and a few sub-folders in the HTML Files (Topics) folder within the Project Manager pod. The organization of these folders and topics mirrors my TOC. Once I nailed down the basic structure of my help system, I started using the TOC as my “hub” for working on the various topics – meaning that I open a particular topic by double-clicking it in the TOC.
Then something went awry early this week.
Sometimes when I open my project, the folders and sub-folders along with their many topics are missing from the Project Manager pod. The TOC also reflects these missing files with those dreaded red-X topic icons. And in Windows Explorer, no trace of the folders, sub-folders, and topics can be found
On a couple of occasions, I opened my project and most – but not all – of the folders and their accompanying topics were deleted from the Project Manager pod. The only topics that consistently “survive” are the ones that aren’t nested within a folder or sub-folder in the Project Manager’s HTML Files (Topics) folder.
I’ve been able to make some progress on my help system by periodically saving the entire project folder, and then using the latest backup as my starting point whenever this problem occurs. But ultimately I end up losing a fair amount of work.
I rooted around this forum for help and insight. I saw several suggestions concerning a similar problem with RH 8 where the solution was to delete the .xpj and .cpd files and then open the .hhp file. Unfortunately, this fix didn’t work for me.
I’m now working in a state of high anxiety, wondering whether my topic files will exist the next time I open my project. Any help with this problem would be greatly appreciated.
-KevinYes what Jeff is suggesting is trying a shorter path. Just copy the project from where it is to C:\MyProject and see if that fixes the problem.
As to deleting the CPD every time, some do, some don't. It used to lose some information but things were changed and now it is OK to delete it every time. Do not delete the XPJ file though, that will mess up your project. See Opening Projects on my site.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge -
How Can I Safely Delete a RoboHelp 9 Project?
I am learning/evaluating RoboHelp 9 using IconLogic's "Essentials of Adobe RoboHelp 9 HTML". This book has excellent step-by-step lessons and contains student data files to make it easier to learn. The student lessons were downloaded and unzipped into a folder called "RoboHelp9Data". Beneath this folder is a folder named "RoboHelpProjects". (Note there is no space in the folder name.) At some point, I inadvertently created a folder called "RoboHelp Projects". (Note the space in the folder name.) As lessons progressed, I learned (1.) it is best not to have pathnames with spaces as this can cause problems on some operating systems; and (2.) you should not delete any RoboHelp files via Windows Explorer. Rather, you should always delete them from within the RoboHelp application itself. (Let it be duly noted that the admonition in Item 2 came with no instructions on how to do that which it admonished!)
Because I now have two folders with similar names ("RoboHelpProjects" and RoboHelp Projects"), it is causing me problems. At first glance, it seems the simplest solution would be to remove and recreate the entire root folder, "RoboHelp9Data " via Windows Explorer. (I don't care about losing project data---I actually want to start over.) The thing that stops me from doing this is the admonition in item 2 above. So would RoboHelp still be unhappy if I were to remove the entire root project folder and everything it it (via Windows Explorer). It seems logical to me that if all traces of all project files were to disappear (including the files that contain references to the project), RoboHelp would not have anything to complain about! (I guess that all depends upon where and how the RoboHelp application stores data about each project, and sadly, I am ignorant of that knowledge.)
As I am unwilling to stand accused by the RoboHelp application of high crimes against project data, I decided to play it safe and delete my projects from within RoboHelp and then recreate them. It sounds reasonable, does it not? One would think that finding out how to delete a project from within RoboHelp would be simple enough. However, one would be wrong.
I have tried the obvious: (1.) Searched the index and TOC of my book for info on deleting a project---no help there; (2.) Looked for a "delete project" option in the Manager Pod "File" menu (also tried the right-click options)---no help there; and (3.) I searched the web and Adobe forums for "Delete RoboHelp 9 Project" with no success. I did find an article about removing unused project files (Tools > Reports > Unused Files), but nothing about deleting an entire project.
As a new RoboHelp user, what I need are some simple step-by-step instructions on how to safely delete a RoboHelp 9 project from within RoboHelp. This seems like it should be a short, simple, straightforward answer that is easy to find on the Web. What am I missing?Kevin is suggesting that you store the projects you create while working through his book in a folder called RoboHelpProjects. It is not where you have to store every project you ever create.That is for the purposes of his book.
RoboHelp initially defaults to My RoboHelp Projects but it's up to you whether you do. Generally on the forums we advise against that as it is part of your profile and can result in excessively long path names in a few cases. Generally where authors create file names that are so long they almost serve as the content.
Projects always have a root folder, call them Project 1 and Project 2 for this purpose. You can have those folders directly off your C drive (or other local partition) or within in a parent folder as above.
Now to what you can and cannot do. You can delete a whole project by selecting Project 1 or Project 2 in Windows Explorer. Obviously if you delete the parent folder you will delete all your projects within.
What you must not do is delete individual files within a project using Windows Explorer, for that you use RoboHelp's Project Manager. The exception is if you go to Tools > Reports there is a report Unused Files. Files listed there will have to be deleted using Windows Explorer for the very good reason they do not appear in Project Manager and, therefore, cannot be deleted that way.
If you think about it, it is similar to Word. There is no option to delete a document there other than using File > Open and right clicking. Not very intuitive.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge
Maybe you are looking for
-
Can no longer move a new tab into Pinned App section in FF17
After the update to FF17 I can no longer move a new tab into the Pin As App section without first pinning the tab. I liked how it worked before, where if you put it to the front or between 2 pinned tabs it would just pin itself and place it where you
-
PC Internet Activity to ADOBE Site
In the last couple weeks, we have noticed our PC's with ADOBE installed on them hamering a site called 66.119.205.8. We have done sniffer traces and it appears the traffic is Adobe Update traffic. My workstation showed up on the list with 568 request
-
Hello Can anyone help me with a problem I have placing an image. I scanned a black and white photo to my desktop, then tried to place that scanned image onto a new layer in my Illustrator CS4 page. Instead of the image appearing on the page, there is
-
How to restrict two employees from viewing each others' activities in a particular account?
Dear Experts, I have a scenario here and request your kind input to bring a solution to it. I have two sales org. in one company. One is SO1 and other one is SO2. I want to restrict the sales employee of SO1 and SO2. Both of them are working in the s
-
I phone 4 , gets calls and than does not get calls. I have to re-boot to get the phone to work. I have to keep checking to see if i am getting a signal.My sleep button is broke and I am useing the accessibility mode . Also I am using Metro P.C. as my