Acrobat 9.0 Pro crashes when trying to edit fields

Acrobat 9.0 Professional crashes when I try to edit or add text fields. I am running Windows Vista. All other functions of Acrobat work.

There was an update this last week, taking the current version to 9.3.2. The early versions often have little bugs like you describe, so an update is the first thing to try. If you download the updates from Adobe.com (the downloads>updates page), be sure to download all of them and then install them in order. If you use the updates under help, you can usually update the lowest number one they show and return for any further updates.

Similar Messages

App crashes when trying to edit specific page

I need to edit a specific page of my site and I cannot open it as the app crashes when trying to. Does this happen often? It is my wife's business site and she is a novice so we are wondering if we should move to a more stable platform. There is nothing fancy on the page. We bought into iLife specifically because it was easy for her to manage and are interested to know if others see the same thing.

Your Public Profile indicates you're running Mac OS X (10.4.10) — if that's the case, you should upgrade to 10.4.11 via  menu > Software Update... then update your Public Profile and try editing your site again.
+"A lot of problems can be solved simply by..."+ Read more in the "Fix iWeb" section here:
http://www.iwebformusicians.com/WebMusic/iWebTips.html
But before trying such suggestions, read this:
_iWeb: Backing up your Domain file_
If still no luck, post some details of the crash and perhaps someone can help.
crankbait wrote:
It is my wife's business site...
iWeb is designed for personal sites and is a minor part of Apple's software repertoire. I suggest you consider web-design apps from companies dedicated to their product. Weebly is free and web-based — so you can update the site from any Mac or PC. It also offers e-commerce features:
http://blog.weebly.com/2/post/2009/05/announcing-weebly-e-commerce-features.html
Web-design apps for business sites tend to integrate SEO (Search Engine Optimization) — Sandvox Pro is an example:
http://www.karelia.com/sandvox/getyour_site_noticed_andb.html

HP OJ Pro 8600 Pro crashes when trying to login to print Google Calendar

I get a hard reboot crash when I try to login with the correct password using the Google Calendar App. If I use the incorrect password it handles that gracefully.
HP OfficeJet Pro 8600 Pro, brand new out of box
I have not hooked the printer up to the computer as of yet. But I utilize Windows 7 64 bit.

I will need to get some more information from you first in order to help out. This printer is set up wirelessly, Correct? What make and model is the router that are you using? Or, is this a hot spot setup? Are you able to access other Apps on the front panel successfully? Can you access HP apps successfully? Have you received any error messages on the front panel of the printer?
I am a former employee of HP...
How do I give Kudos?| How do I mark a post as Solved?

Premiere Pro crashing when trying to open a project

I get this message when trying to open any of my projects:
Here are my specs for my computer:
I do not have a graphics card at this time, I am running on the onboard graphics on my motherboard which is the Gigabyte Z87X-HD3 ...
I am fully updated with latest drivers, adobe cloud, and program updates.
N.B. I did not have this problem until installing Premiere Pro CC 2014, prior versions worked absolutely fine on the same machine which is puzzling to me.

GIGABYTE - Motherboard - Socket 1150 - GA-Z87X-HD3 (rev. 1.1) indicates an Intel graphics chip
Since Windows update is not always accurate, have you checked Gigabyte and/or Intel for a newer driver?

Acrobat Pro 8.1.12 and Acrobat Reader 9.0 crashing when trying to print

The subject line says it all, but I upgraded my MacBook Pro to Leopard 10.5.5 and now when I select File | Print I get the spinning beach ball than Acrobat crashes. Now oddly, if I use Acrobat Reader 7.0.9, it prints perfectly. But have Acrobat Pro 8.1.12 crash every time the File | Print is selected is a major problem. And no, not even the dialog box comes up first, Acrobat just goes down.
Has anyone else seen this? I saw in the forum others were have problems creating PDF's, something I haven't done yet.

Try the following: (I have no idea if it will help but might be worth a shot.
Its possible That you need to update the driver shown in Printer Utility.
Locate Adobe PDF 8.0 (what evr the latest version is.
Now delete from Printer Utilities List, and quit Printer Utility.
Now open Acrobat 8.1.2 and go to help menu.
Now choose reapir or Replace.
uncheck PDFViewer and check Adobe PDF
Now click okay to repair.
If you have acrobat 9. all previous acrobat versions will work with the Adobe PDF 9.0 Driver just fine. It just will not try to use new features added since 9.0.
Also, It possible that your Print Driver for your printer has been updated with the new Sysytem Upgrade.
If so remove the printer listed from the Printer Utility List.
the click on add printer. look for the driver for your printer listed choose make default then quit.
Try Acrobat 8 again and then go to set up menu see if you can find your printer listed. is so choose and save as default.

Acrobat 9 pro crashes when trying to distribute

win xp sp3
acrobat 9 pro
new-ish to acrobat
I have an interactive form, created in acrobat 9 pro. Every time I try to distribute it (forms > distribute form > manually collect responses in my email inbox > save a local copy and manualy send it later > finish) it crashes & I get an error message: "AppName: acrobat.exe, AppVer: 9.5.2.295, ModName: acrobat.dll, ModVer: 9.5.2.295, Offset: 00604f17"
The really odd thing here is that it only does this if I try to save it over the network. If I open the form from/save to a local drive e.g. the desktop or a thumb drive it works fine.
Anyone got any idea what's going on & what to do about it?
TIA

There was an update this last week, taking the current version to 9.3.2. The early versions often have little bugs like you describe, so an update is the first thing to try. If you download the updates from Adobe.com (the downloads>updates page), be sure to download all of them and then install them in order. If you use the updates under help, you can usually update the lowest number one they show and return for any further updates.

DVD Studio Pro Crashes when trying to import file

Hey all,
Hope you can help me because this is driving me crazy!
Whenever I try to import .ac3/.m2v files to DVDSP, the program crashes. The strange thing is that it is happening only when I try it on one particular file. I seem to be able to import anything else but the audio/video files I really need! I've tried re-compressing, and re-naming the file, I've also tried importing the file on a different computer, but nothing seems to work.   I haven't tried reinstalling since it seems to work with other files and I've tried it on separate computers.
I'm using Final Cut 7 with Snow Leopard
Here's the first part of the report:
Process:         DVD Studio Pro [1315]
Path:            /Applications/DVD Studio Pro.app/Contents/MacOS/DVD Studio Pro
Identifier:      com.apple.dvdstudiopro
Version:         4.2.2 (431.40)
Build Info:      DSP-4315400~54
Code Type:       X86 (Native)
Parent Process: launchd [105]
Date/Time:       2012-08-10 07:45:07.946 -0400
OS Version:      Mac OS X 10.6.8 (10K549)
Report Version: 6
Interval Since Last Report:          18354646 sec
Crashes Since Last Report:           58
Per-App Interval Since Last Report: 5731 sec
Per-App Crashes Since Last Report:   7
Anonymous UUID:                      5565D110-70D4-4F1B-BF1A-072C2D138FF3
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000261
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0   com.apple.QuickTime                0x9a8d1dd8 PrivateQTGetMoviePlayabilityState_priv + 62
1   com.apple.QuickTime                0x9a8d1d8a QTGetMoviePlayabilityState_priv + 33
2   ...ickTimeComponents.component     0x9448dac8 internalDoAction + 9849
3   ...ickTimeComponents.component     0x9447cde9 _MCIdle + 61
4   ...ple.CoreServices.CarbonCore     0x99f72dcc CallComponentFunctionCommonWithStorage(char**, ComponentParameters*, long (*)(), unsigned long) + 54
5   ...ickTimeComponents.component     0x944786a0 _MCComponentDispatch + 111
6   ...ple.CoreServices.CarbonCore     0x99f6b51f CallComponentDispatch + 29
7   com.apple.QuickTime                0x9a8d1d3e MCIdle + 37
8   com.apple.QuickTime                0x9a8cfc25 QTOMovieObject::SendCommand(unsigned long, void const*) + 899
9   com.apple.QuickTime                0x9a8b337a DispatchQTMsg(void const*, unsigned long, unsigned long, unsigned long, QTOGenericObject*) + 240
10 com.apple.QuickTime                0x9a8b31de QTObjectTokenPriv::SendMessageToObject(QTMessagePriv*, unsigned long) + 178
11 com.apple.QuickTime                0x9a8b2745 QTObjectTokenPriv::DispatchMessage(QTMessagePriv*, void const*, __CFAllocator const*, unsigned long, unsigned long, ComponentMsgParam*, unsigned long, unsigned long) + 1249
12 com.apple.QuickTime                0x9a8cf894 QTSendToObject + 98
13 com.apple.QTKit                    0x90b811e6 QTObjectTokenExecuteCommand + 83
14 com.apple.QTKit                    0x90b62b51 -[QTMovie_QuickTime idle] + 303
15 com.apple.QTKit                    0x90b065ec +[QTMovie_QuickTime idleAllMovies:] + 308
16 com.apple.Foundation               0x93458484 __NSFireTimer + 141
17 com.apple.CoreFoundation           0x91eada3b __CFRunLoopRun + 8059
18 com.apple.CoreFoundation           0x91eab3c4 CFRunLoopRunSpecific + 452
19 com.apple.CoreFoundation           0x91eab1f1 CFRunLoopRunInMode + 97
20 com.apple.HIToolbox                0x90e2fe04 RunCurrentEventLoopInMode + 392
21 com.apple.HIToolbox                0x90e2fbb9 ReceiveNextEventCommon + 354
22 com.apple.HIToolbox                0x90e2fa3e BlockUntilNextEventMatchingListInMode + 81
23 com.apple.AppKit                   0x962bf595 _DPSNextEvent + 847
24 com.apple.AppKit                   0x962bedd6 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156
25 com.apple.AppKit                   0x965381c9 -[NSApplication _realDoModalLoop:peek:] + 720
26 com.apple.AppKit                   0x96537945 -[NSApplication runModalForWindow:] + 273
27 com.apple.AppKit                   0x967cbad3 -[NSSavePanel runModal] + 420
28 com.apple.dspinterface             0x00047c4f -[DSPXProjectBinModule importAsset:] + 500
29 com.apple.AppKit                   0x962fda26 -[NSApplication sendAction:to:from:] + 112
30 com.apple.prokit                   0x0047e414 -[NSProApplication sendAction:to:from:] + 127
31 com.apple.AppKit                   0x963dd255 -[NSControl sendAction:to:] + 108
32 com.apple.AppKit                   0x963d8d02 -[NSCell _sendActionFrom:] + 169
33 com.apple.AppKit                   0x963d7ff9 -[NSCell trackMouse:inRect:ofView:untilMouseUp:] + 1808
34 com.apple.AppKit                   0x9642d6ed -[NSButtonCell trackMouse:inRect:ofView:untilMouseUp:] + 524
35 com.apple.prokit                   0x004c321e -[NSProButtonCell trackMouse:inRect:ofView:untilMouseUp:] + 539
36 com.apple.AppKit                   0x963d6a4f -[NSControl mouseDown:] + 812
37 com.apple.AppKit                   0x963d4a58 -[NSWindow sendEvent:] + 5549
38 com.apple.prokit                   0x004a69f0 -[NSProWindow sendEvent:] + 264
39 com.apple.dspinterface             0x000afc63 -[DSPXDocumentWindowClass sendEvent:] + 777
40 com.apple.AppKit                   0x962ed60b -[NSApplication sendEvent:] + 6431
41 com.apple.prokit                   0x00481040 -[NSProApplication sendEvent:] + 1901
42 com.apple.AppKit                   0x96281253 -[NSApplication run] + 917
43 com.apple.prokit                   0x004813f6 NSProApplicationMain + 326
44 com.apple.dvdstudiopro             0x0000354d 0x1000 + 9549
45 com.apple.dvdstudiopro             0x00002cf6 0x1000 + 7414
Thread 1: Dispatch queue: com.apple.libdispatch-manager
0   libSystem.B.dylib                  0x9062c382 kevent + 10
1   libSystem.B.dylib                  0x9062ca9c _dispatch_mgr_invoke + 215
2   libSystem.B.dylib                  0x9062bf59 _dispatch_queue_invoke + 163
3   libSystem.B.dylib                  0x9062bcfe _dispatch_worker_thread2 + 240
4   libSystem.B.dylib                  0x9062b781 _pthread_wqthread + 390
5   libSystem.B.dylib                  0x9062b5c6 start_wqthread + 30

In FCP, export the file in 4 different chunks.
In Compressor, convert each chunk to ac3/m2v.
Import each chunk into DVDSP.
Do they ALL cause problems or is it only one chunk?
If only one chunk, there is something wonky with the video in that segment.
Divide it up and go through the same process until you identify the offending source video. Once identified you have a couple of options -
1. Cut it out and try to stich the material around the hole.
2. Try using Digital Rebellion's ProMediaTools to see if it can fix the problem.
3. If the original media was in a different format, go back to the original media, reconvert it and replace the bad segment.
x

Combining PDF Form causes fields to disappar, Acrobat to crash when trying to edit combined PDF

I have a 10 page PDF form that I can edit normally. I combine it using the Combine Files wizard. The resulting PDF has several fields disappear upon saving, and causes Acrobat to crash every time if I try to edit the form. I can combine the original PDF form with no other document, and the error still occurs. I have several similarly named fields, such as Name#1 and Name#2, and it seems that all those fields disappear after going through the Combine Files process. I can open the resulting PDF, and fill in the remaining fields, but attempting to edit the form causes Acrobat to crash each and every time.
I have used this process before, with no problems, but it fails every time on this form.
This is the error in the Event Viewer: Faulting application Acrobat.exe, version 10.0.0.396, time stamp 0x4cc5ebc0, faulting module AcroForm.api, version 10.0.0.396, time stamp 0x4cc5f5cc, exception code 0xc0000005, fault offset 0x0012d905
This is using Acrobat X Standard and Pro on XP Pro and Vista.
If I open the original PDF, and insert a new PDF as new pages, that works fine.
I updated Acrobat to the latest patch, problem remains. I don't know how to resolve this.

Did a little more testing and this is what I found. If I use the "Insert from file" feature to combine a cover sheet plus 3 AcroForms (inserting each file one by one), eveyrthing appears to work. However, if I use the "Combine via Acrobat" feature I run into the issue of fields disappearing once combined.
I shoudl also add that perhaps the issue had something to do with the fact that I initally produced the cover page pdf via Photoshop "save as PDF". Perhaps that contirbutted to the structure issue despite it being a PDF...maybe under the hood things are structured differently. Who knows.
Just FYI for others: What appears to be working is using the "Insert from file" option vs "Combing via Acrobat". Also, if you are including a non-AcroForm PDF, be sure it a traditional vs. saving as a PDF from Photoshop.
Alot of this may be a fluke, but it seems to fix my issue - for now.

Quicktime Pro crashes when trying to save file

I just quicktime pro, and so far it keeps crashing on me when I try to save a video file. Here are the steps:
1. Open a video file (m4v)
2. Overlay text on the first few seconds of the video
3. Save video
4. CRASH!
I'm not sure if this helps, but I got the following debug dump. Not sure if it's helpful.
Please help! I have the latest version of QT Pro.
Dump:
The thread 'Win32 Thread' (0x1204) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0xf18) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x17f8) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1680) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1784) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x103c) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0xe44) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1004) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0xcb8) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0xab8) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0x9b0) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0x14a4) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0x478) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0x1104) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0x1368) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0x17a4) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0x11a4) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0xdcc) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0x9c0) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0x168c) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0x13ec) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0xb3c) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0xce0) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0x17ac) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0x11f0) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0x1584) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0x1290) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0xbf0) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0xac0) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0x1478) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0x1668) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0xf30) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0x11ac) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0xac4) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0x10a8) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0x1704) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0x1484) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0x904) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0x4b4) has exited with code -1073740791 (0xc0000409).
The thread 'Win32 Thread' (0x136c) has exited with code -1073740791 (0xc0000409).
The program '[3852] QuickTimePlayer.exe: Native' has exited with code -1073740791 (0xc0000409).

Drat ... so much for subtlety ...
Right, let's scrape all the QuickTime files out and reinstall from scratch.
First, let's download and save a "standalone" QuickTime installer to your hard drive (don't run the install on line, and don't start the install just yet). Get the version that doesn't mention iTunes:
http://www.apple.com/quicktime/download/
Next, we'll make sure we've got your *Pro Key* secured. (Uninstalling QuickTime will remove the Pro Key, and we'll have to reenter it in the Register Tab after reinstalling QuickTime.)
Head into your QuickTime, preferences and take a note of precisely how the Key *and the name in the "Registered to" field* appear. (I've been known to take and print out a screenshot of the Register tab, in order to be quite sure of the precise details of both those things.) Don't tell us what your Key is.
Now, head into your "Uninstall a program" and uninstall QuickTime.
After the uninstall completes, we'll clean up any leftover QuickTime program files on the PC. How we do that will depend on whether you've got a 32-bit or 64-bit version of 7.
*With a 32-bit 7*
(1) Open Local Disk (C:) in Computer or whichever disk programs are installed on.
(2) Open the Program Files folder.
(3) Right-click the QuickTime folder (if it still exists there) and select Delete and choose Yes when asked to confirm the deletion.
(4) Delete the QuickTime and QuicktimeVR files located in the C:\Windows\system32 folder (if they still exist there). Click Continue if Windows needs confirmation or permission to continue.
(5) Right-click on the Recycle Bin and on the shortcut menu, click Empty Recycle Bin.
(6) Restart your computer.
*With a 64-bit 7*
1) Open Local Disk (C:) in Computer or whichever disk programs are installed on.
(2) Open the Program Files (x86) folder.
(3) Right-click the QuickTime folder (if it still exists there) and select Delete and choose Yes when asked to confirm the deletion.
(4) Delete the QuickTime and QuicktimeVR files located in the C:\Windows\sysWOW64 folder (if they still exist there). Click Continue if Windows needs confirmation or permission to continue.
(5) Right-click on the Recycle Bin and on the shortcut menu, click Empty Recycle Bin.
(6) Restart your computer.
After the PC restarts, don't open any applications. Disconnect from the internet and/or your network, and switch off all your security software (firewall, antivirus, antispyware).
Reinstall QuickTime by doubleclicking the QuickTimeInstaller.exe you downloaded earlier.
Reenable all security software prior to prior to reconnecting to your network and/or the internet.
Now launch QuickTime. Go into your QuickTime preferences, and reenter your name and Key *precisely as they were prior to the uninstall.* Click apply. You should see "QuickTime 7 Pro" appear in the Tab.
... now let's try giving the export another shot. Any better luck this time?

HT4740 How can I avoid or solve the problem of Final Cut Pro crashes when trying to Show Events Library?

When I try to Show Events Library in Final Cut Pro, it crashes each time. Please tell me how do I work around this problem?

Try creating a new (temporary) folder and putting all your events in there - then launch FCP X.
If you can open the Browser, then it's possible one or more of the clips in one of your events is corrupt. Close the app and move the events back into their original places one by one (re-starting FCP X each time). This will help you find the event which has the corrupt file in it.
If isolating the events has no effect, I suggest you trash your preferences.
Unexplained faults like this can often be fixed by clearing out FCP X's preferences (for some reason, they get knotted up from time to time).
Download Digital Rebellion's Preference Manager (free, simple to use, and perfectly safe, both to download and use).
http://www.digitalrebellion.com/prefman/
With Preference Manager, you can backup the Prefs when FCP X (or any of the Apple Professional Applications) are working normally. Then when either of the applications are acting strangely, Trash the Preferences, then Restore from your backups (just a mouse-click).
If you trash the prefs and don't restore them, you will need to manually restore all your FCP X settings again, so it's a great idea to backup Preferences from time to time when FCP X is working well, then your backups are up to date.
Doesn't fix every problem, but it fixes a lot.
Andy

Premiere pro crashes when trying to pan or zoom in a clip on timeline.

I have tried multiple computers and reinstalling. Win7 64bit, premiere pro 8.20 (65). Choosing a photo->effects->scaling and then the program crashes. Eventlog indicates that the problem is with C:\windows\SYSTEM32\MSVCR110.dll (I wont post the event here because its in danish). Anyone got a clue?

What is the pixel size of the photos?
Try updating or rolling back your video driver.
Try disabling GPU acceleration.

Quiktime Pro crashing when trying to run updates - windows XP PRO

I have previously purchased QuickTime PRO & MPEG2 and now every time the QUICKTIME update wants to run . . . it crashes the update, causing QuickTime to crash.
And if it is done through the webbrowser it will also crash FireFox & IExplorer 7.
It happens every time I visit a web page and requires the new update to take effect and since quicktime update runs in auto it causes the crashing of any browser.
The "culprit" error has to do with QuickTime.cpl (Shell32.dll and Control_Run.DLL)
Does anyone run into this problem and if so, have you found a solution?
The update is from QT 7.4 to 7.4.1 (the latest one).
Thanks all
Z

Same here...AND....when I try to change video settings when EXPORTING to .AVI as an example...just closes the program. Annoying! ANY HELP?!?!

QT 7 Pro crashes when trying to export

I just installed QT 7 Pro (win-xp). It crashes whenever I try to export. I'm a long time user of QT 6 Pro and never had a problem. I soon I select the "export" dropdown menu the application crashes and the windows error reporter.
AppName: quicktimeplayer.exe AppVer: 7.0.3.25 ModName: avcodec.dll
ModVer: 0.0.0.0 Offset: 000cb360

no answer... i ended up rebuilding my system. Sorry for the long delay in responding.

My macbook pro crashes when trying to connect to a router, my macbook pro crashes when trying to connect to a router, my macbook pro crashes when trying to connect to a router

my laptop has always connected to routers without a problem, but with one particular router, when it connects to it, the computer crashes. Also, when I turn on the computer within the range of the router, the computer will not start.

It just crashed again with nothing running but the apple website an itunes.

After upgrading to ios5.1 photo app crashes when trying to edit "cropping"photos. I've shut it down and also tried a reboot.

Does anyone else experience this problem?
When I try to edit photos in the photo app and in the camera app
I try to crop them and the system will randomly crash. Giving me
either a circle ticking logo on a black screen or the system will
reboot completely with a black screen, Apple logo, and then
back to the lock screen.

I have a PC running Windows Vista so what I had to do was in iTunes make sure that all my photos were SYNC'd with my pictures directory. After that when I was sure that I had all the photos that were on my iPhone in my windows pictures directories then I deleted all my pictures off of my iPhone. In order to do this once you plug your iPhone into your computer via the 30 pin dock connector cable, and after the computer recognizes your iPhone, a window will pop up in Windows that shows your device. iOs will allow you to open up a file folder that contains your photos.
Note: there may be several file folders depending on the library size of your pictures and if you have photo stream enabled. In my case I had four folders and these folders or a combination of numbers and letters. These folder names are randomly generated through iOS but just be aware that these folders contain your photos and videos. I know that one folder was just my photo stream because I did not have very many pictures, and two folders had my entire photo library and camera roll in them and another folder had just my videos in it.
The process is pretty simple: once I open these folders, I highlighted all my pictures and deleted them. Once they were deleted off the phone then I went into the iTunes "summary" page for my iPhone. I then went to the "photos" tab and I made sure that the box was checked to sync my photos. In my case I don't have my entire photo library on my phone so I have selected folders button checked. Then I just SYNC'd my phone again. It didn't take too long for iTunes to transfer all my photos back to my phone. After this process was complete I checked all my photos and tried to crop them and had no problems. I also did some screen captures on my phone by pressing the sleep/wake button and the home button at the same time. Again I tried to crop photos and had no problem.
So what I believe with the expert advice from Adam Christiansen of the Mac cast podcast was that I had a corrupt photo file or corrupt metadata from a photo file. So what this was doing was causing a system crash and reboot in iOS. I was able to verify this in my diagnostic files on my iPhone in the settings / general / about / diagnostics and usage / diagnostics and usage data TABS.
I HOPE THIS HELPS YOU AS IT ALLEVIATED MY PROBLEM. I HAVEN'T HAD ANYMORE PROBLEMS WITH THIS ISSUE AND WHAT I'VE DESCRIBED ABOVE IS A WAY TO DO IT WITHOUT RESTORING YOUR ENTIRE IPHONE. IF YOU STILL HAVE PROBLEMS AFTER DOING THIS THEN YOU HAVE ANOTHER PROBLEM WHICH PROBABLY REQUIRES THAT YOU DO DO A COMPLETE RESTORE OF YOUR IPHONE. BUT BEFORE YOU DO THE RESTORE MAKE SURE THAT YOU BACKUP YOUR IPHONE AND I WOULD SUGGEST DOING THAT TO YOUR COMPUTER AND NOT TO ICLOUD; MY REASON FOR THIS IS THOUGH ICLOUD IS A WAY TO DO IT IT JUST TAKES MORE TIME TO RESTORE FROM A BACKUP VIA ICLOUD AS OPPOSED TO A TETHERED BACKUP VIA THE 30 PIN DOCK CONNECTOR CABLE TO YOUR COMPUTER.

Acrobat 9.0 Pro crashes when trying to edit fields

Similar Messages

Maybe you are looking for