Entries folder crash problem

No one's answering my other question, so I have to try here again, more succinctly.
The issue I'm having, very simply, is that whenever I click on the "entries" page of one of my four "blog" pages, iWeb crashes; it does the same if I so much as ctrl-click on that same "entries" page.
This is a serious issue for me, as I have over 200 blog entries in this section of my site.
It also crashes whenever I try to publish, if I choose to publish the WHOLE site (and always when it's processing that same "entries" page).
Please, please help me out!

Modern web pages have dozens of elements, so I'm not surprised that a lot of items would be stored in the cache.
When checking for user.js, make sure to look in your main profile folder and not the companion temporary folder (where you found cache2). You can open your current Firefox profile folder using either
* "3-bar" menu button > "?" button > Troubleshooting Information
* (menu bar) Help > Troubleshooting Information
* type or paste about:support in the address bar and press Enter
In the first table on the page, click the "Show Folder" button to launch it in a new window.
If you are viewing files alphabetically in the Details view and you find a file named user that is of the type JavaScript or JScript, then that probably is user.js. You can adjust a Windows setting to show the file extensions that Windows normally hides from you. This article has the steps: http://windows.microsoft.com/en-us/windows/show-hide-file-name-extensions

Similar Messages

9.1.1 - OS 10.6.3 crash problems

Joined: 18 May 2009
Posts: 1
Posted: Sun May 02, 2010 6:23 pm Post subject: 9.1.1 - OS 10.6.3 crash problems
I've been experiencing crashing in 9.1.1 when I create a new instrument or audio track in an empty project (no 3rd party plugs) or when I try to click on any plugin preset browser in an existing project. Any ideas what might be happening - things were going smoothly until this started happening
here is a crash report -
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 libSystem.B.dylib 0x965da132 __kill + 10
1 libSystem.B.dylib 0x965da124 kill$UNIX2003 + 32
2 libSystem.B.dylib 0x9666c8e5 raise + 26
3 libSystem.B.dylib 0x96682931 __abort + 124
4 libSystem.B.dylib 0x966829ad abortreportnp + 0
5 com.apple.logic.pro 0x00405649 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 3974297
6 libSystem.B.dylib 0x965df42b _sigtramp + 43
7 ??? 0x0000000b 0 + 11
8 MAAssetSharing 0x00eea4a7 MADSManagerDumpToConsole + 1559
9 MAAssetSharing 0x00eeb5b3 MADSManagerGetManagerForIdentifier + 35
10 com.apple.logic.pro 0x0070d38d std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 7152093
11 com.apple.logic.pro 0x000aa235 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 454789
12 com.apple.logic.pro 0x0070648c std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 7123676
13 com.apple.logic.pro 0x007070fe std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 7126862
14 com.apple.Foundation 0x9078f970 __NSFireTimer + 141
15 com.apple.CoreFoundation 0x9423976b __CFRunLoopRun + 8059
16 com.apple.CoreFoundation 0x942370f4 CFRunLoopRunSpecific + 452
17 com.apple.CoreFoundation 0x94236f21 CFRunLoopRunInMode + 97
18 com.apple.HIToolbox 0x97fa20fc RunCurrentEventLoopInMode + 392
19 com.apple.HIToolbox 0x97fa1eb1 ReceiveNextEventCommon + 354
20 com.apple.HIToolbox 0x97fa1d36 BlockUntilNextEventMatchingListInMode + 81
21 com.apple.AppKit 0x96b39135 _DPSNextEvent + 847
22 com.apple.AppKit 0x96b38976 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156
23 com.apple.AppKit 0x96afabef -[NSApplication run] + 821
24 com.apple.prokit 0x00fcaab1 NSProApplicationMain + 326
25 com.apple.logic.pro 0x0002aa55 DummyConnection::DummyConnection() + 193
Thread 1: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x9659fb42 kevent + 10
1 libSystem.B.dylib 0x965a025c dispatch_mgrinvoke + 215
2 libSystem.B.dylib 0x9659f719 dispatch_queueinvoke + 163
3 libSystem.B.dylib 0x9659f4be dispatch_workerthread2 + 240
4 libSystem.B.dylib 0x9659ef41 pthreadwqthread + 390
5 libSystem.B.dylib 0x9659ed86 start_wqthread + 30
Thread 2:
0 libSystem.B.dylib 0x96598286 select$DARWIN_EXTSN + 10
1 com.apple.CoreFoundation 0x9427782d __CFSocketManager + 1085
2 libSystem.B.dylib 0x965a6a19 pthreadstart + 345
3 libSystem.B.dylib 0x965a689e thread_start + 34
Thread 3:
0 libSystem.B.dylib 0x9659ebd2 _workqkernreturn + 10
1 libSystem.B.dylib 0x9659f168 pthreadwqthread + 941
2 libSystem.B.dylib 0x9659ed86 start_wqthread + 30
Thread 4:
0 libSystem.B.dylib 0x965a7262 _semwaitsignal + 10
1 libSystem.B.dylib 0x965a700d pthread_condwait + 1430
2 libSystem.B.dylib 0x965a8bb8 pthreadcondwait$UNIX2003 + 73
3 ...le.music.apps.MAAudioEngine 0x02bba437 GetCurrentCoreAudioDeviceNameFromUserDefaults(signed char) + 18439
4 libSystem.B.dylib 0x965a6a19 pthreadstart + 345
5 libSystem.B.dylib 0x965a689e thread_start + 34
Thread 5:
0 libSystem.B.dylib 0x965792fa machmsgtrap + 10
1 libSystem.B.dylib 0x96579a67 mach_msg + 68
2 com.apple.audio.midi.CoreMIDI 0x012e0f31 XServerMachPort::ReceiveMessage(int&, void*, int&) + 155
3 com.apple.audio.midi.CoreMIDI 0x012ff8fe MIDIProcess::RunMIDIInThread() + 150
4 com.apple.audio.midi.CoreMIDI 0x012e2149 XThread::RunHelper(void*) + 17
5 com.apple.audio.midi.CoreMIDI 0x012e1b16 CAPThread::Entry(CAPThread*) + 96
6 libSystem.B.dylib 0x965a6a19 pthreadstart + 345
7 libSystem.B.dylib 0x965a689e thread_start + 34
Thread 6:
0 libSystem.B.dylib 0x9657935a semaphoretimedwait_signaltrap + 10
1 libSystem.B.dylib 0x965a6ea1 pthread_condwait + 1066
2 libSystem.B.dylib 0x965d5a28 pthreadcond_timedwait_relativenp + 47
3 ...ple.CoreServices.CarbonCore 0x93a44465 TSWaitOnConditionTimedRelative + 242
4 ...ple.CoreServices.CarbonCore 0x93a441a3 TSWaitOnSemaphoreCommon + 511
5 ...ple.CoreServices.CarbonCore 0x93a683eb TimerThread + 97
6 libSystem.B.dylib 0x965a6a19 pthreadstart + 345
7 libSystem.B.dylib 0x965a689e thread_start + 34
Thread 7:
0 libSystem.B.dylib 0x9659ebd2 _workqkernreturn + 10
1 libSystem.B.dylib 0x9659f168 pthreadwqthread + 941
2 libSystem.B.dylib 0x9659ed86 start_wqthread + 30
Thread 8:
0 libSystem.B.dylib 0x9659ebd2 _workqkernreturn + 10
1 libSystem.B.dylib 0x9659f168 pthreadwqthread + 941
2 libSystem.B.dylib 0x9659ed86 start_wqthread + 30
Thread 9:
0 libSystem.B.dylib 0x965a7262 _semwaitsignal + 10
1 libSystem.B.dylib 0x965d2e44 nanosleep$UNIX2003 + 188
2 libSystem.B.dylib 0x965d2d82 usleep$UNIX2003 + 61
3 com.apple.AppKit 0x96ca2885 -[NSUIHeartBeat _heartBeatThread:] + 2039
4 com.apple.Foundation 0x907618dc -[NSThread main] + 45
5 com.apple.Foundation 0x9076188c _NSThread__main_ + 1499
6 libSystem.B.dylib 0x965a6a19 pthreadstart + 345
7 libSystem.B.dylib 0x965a689e thread_start + 34
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x966828c1 ecx: 0xbfffd65c edx: 0x965da132
edi: 0x00ccb3bc esi: 0x49081840 ebp: 0xbfffd678 esp: 0xbfffd65c
ss: 0x0000001f efl: 0x00000286 eip: 0x965da132 cs: 0x00000007
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x70da76c0

roweski wrote:
Removing the old preference file was the first thing I tried with no luck.
I just fixed the problem by removing the 'application support/logic' folder. Logic behaved normally.
You mean the one in your user library? So you the culprit was one of your custom presets (that you have now lost)?
The strange thing is that I then dragged the old folder contents back into the newly created logic folder
Are you talking a project folder or the user appsupport folder?
and overwrote all the files so that the content was EXACTLY the same as before. Logic still works fine - bizarre...
Well, if deleting your user application support folder solved the problem, the 'faulty' file was in there. Too bad you now cannot narrow it down further by deleting perhaps subfolders or even individual files from that folder until it was resolved; that way you would have had one or a few specific files that were the cause. Now you won't know until it happens again and try it like this, I guess.
But, if it works it works.

Another crash problem with Adobe Premiere Elements 4

another crash question! burned a dvd of project, saw something i needed to change as i watched the dvd, tried to get back into project, but crashed time and time again. have tried any and all suggestions in the forum for other crash problems, but cannot fix. can anyone help? below is error message and my equipment. using Windows Vista. I want to go back to Windows XP, never had a problem. thanks to anyone who has an idea.
Problem event name:                   APPCRASH
Application name:                       Adobe Premiere Elements.exe
Application version:                     4.0.0.0
DEll XPS 420
Intel (R) core (TM)2
Quad CPU Q9450 @ 2.66GHz
4.0 GB
32 bit
Driver software: ACPIx86 based PC
Adapter ATI Radeon HD 3650

I'm not sure what's up at this point, if doing a Save As and deleting your render files doesn't fix your glitch (and assuming you've got adequate, freshly defragmented room on your drives for the program to work).
You can also try working through Adobe's troubleshooting steps:
http://kb2.adobe.com/cps/514/cpsid_51427.html
Renaming the presets folder can help. (The program will automatically make a new one when you next launch it):
Windows XP:
Documents and Settings/[username]/Application Data/ Adobe/Premiere Elements/8.0/MediaIO/Presets/OTHERS
Documents and Settings/[username]/Application Data/ Adobe/Premiere Elements/8.0/Settings/Custom
    Windows Vista:
Users/[Username]/AppData/Roaming/Adobe/Premiere Elements/8.0/SC/Presets

Crash Problems

I have been having crash problems on a regular basis since upgrading to Yosemite. It seems that if a site (URL) has not fully loaded, or if I am just opening Safari, and I try to move quickly to another site, the thing crashes. This has been persistent, and is very annoying. Every time it happens I send in the crash report, but nothing seems to be getting corrected. You need to work on this. I am really close to moving to FireFox.

Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
Step 1
For this step, the title of the Console window should be All Messages. If it isn't, select
          SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
          View ▹ Show Log List
from the menu bar at the top of the screen.
In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter the name of the crashed application or process. For example, if Safari crashed, you would enter "Safari" (without the quotes.)
Each message in the log begins with the date and time when it was entered. Select the messages from the time of the last crash, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
☞ The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
☞ Some private information, such as your name, may appear in the log. Anonymize before posting.
Step 2
In the Console window, select
          DIAGNOSTIC AND USAGE INFORMATION ▹ User Diagnostic Reports
(not Diagnostic and Usage Messages) from the log list on the left. There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of crash reports. The name of each report starts with the name of the process, and ends with ".crash". Select the most recent report related to the process in question. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.
I know the report is long, maybe several hundred lines. Please post all of it anyway.
If you don't see any reports listed, but you know there was a crash, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.

ITunes 7 crash problem work-around

Until Apple fixes the never-should've-been-released iTunes 7, this is what I've come up with as a work-around: Go back to iTunes 6.0.5
Simpler said then done.
1) First thing is remove that godforsaken iTunes 7 from your Applications folder.
2) Next thing you need to do is delete your iTunesX.pkg file from HD>Library>Receipts so that when you try to install 6.0.5 your computer doesn't block the installation because it thinks iTunes already is installed.
3) Third, go to your Music folder and create a new folder (call it "For when Apple fixes iTunes 7" or something like that); move the iTunes folder into this new folder, otherwise when you start up iTunes 6 it will tell you that all your music is formatted for iTunes 7 and the program won't even open.
4) Fourth, go here and download iTunes 6.0.5
http://www.apple.com/downloads/macosx/apple/itunes605.html
5) Install iTunes 6.0.5
6) Open iTunes 6.0.5
7) In iTunes, Click on File>Add to library... go to that iTunes folder that you stuck in that new folder called "For when Apples fixes iTunes 7" in step 3. Highlight all the albums you want and click Choose or Open or whatever it says
8) Depending on the volume, it will take a while to copy all the music files. It's a two-step process: first they appear in your iTunes library greyed out, then eventually they are fully copied and become live.
Good luck!
G5 iMac Mac OS X (10.4.8)

Somehow the audio output setting in audio midi setup got set to 96000Hz. I changed back to 44100Hz and this seems to have fixed my crashing problem.
I hope this helps some other frustrated peeps.
Normally, you only have to worry about this changing when 3rd party apps are installed, but it sure seems like either the iTunes 7 or Quicktime update were the culprits this time. Another symptom that this setting may be incorrect is that you get no sound at all from flash content.

Crash Problem with Adobe Photoshop CS3

I have been using photoshop and getting the same problem many times. Many times the software gets off during the work. I alwats used to save my work in the end but due to the crash problem my dats gets lost. I am trying to get it recoverbut i think its not posibble to get your lost data back.
If somebody have any best solution to this issue please let us know. Adobe must take care of this issue seriously.
Thanks
Team
Bizz Duniya

This is the InDesign forum. Photoshop is down the hall on the left.
Bob

After upgrade to Yosemite, drag and drop for files does not work, destination folder crashes.

After upgrading to Yosemite, dragging and dropping files from one location to the destination folder, causes the destination folder crash. However, copying the file and then moving it works fine.
I'm not sure where to report bugs, but I figured this would be the best option

http://www.apple.com/feedback/ Feedback
https://bugreport.apple.com/ BugReporter

How do I fix a FINDER crash problem in 10.6.8

I recently, in the last 10 days, started having a FINDER crash problem with my iMac 24" (iMac9,1) Intel Core 2 Duo 3.06 GHz computer.
I have 4 GB of ram installed, no external hard disks installed.
It seems to crash when I have five or more applications open, but it is not consistant.
When it freezes or crashes, I get the spinning ball. I open the Force Quit Window with comand, option, escape and it show Finder not responding.
I click on Finder and tell it to relaunch. It does nothing. At that point I cannot even go to the APPLE icon on the dock and do a shutdown or restart.
From that point on, I have to press and hold the START button to shut the computer down.
I have checked the hard disk integrity with Disk Utility after starting on the Snow Leopard 1.6 install disk. everything shows good.
I have repaired permissions using the same application. I then restart the computer and log back in.
I have used Onyx for Snow Leopard version 2.3.1 to do some maintenance routines.
I have checked the S.M.A.R.T. status of the hard drive and it passes.
I have verified that the Daily, Weekly, Monthly routines have been run. They have.
I have executed the Cleaning tab to include the following cache files:
System: Boot
               International Preferences
               QuickTime Components
               Audio Components
               Other Components
User Cache: Applications
                         Prefernces of System Panels
                         Java & Applets Java
                         Desktop Background
                         International Preferences
                         Dock Icons
                         ColorSync
                         QuickLook
                         Temporary Items
Internet Cache: Browser Cache
                            Download Cache
                            Browser History
                            Recent Searches
                            Web Page Previews
Fonts Cache: System and User
Logs Cache: Log Files
                        System Archive Logs
                        User Diagnostic Reports
                        System Diagnostic Reports
                        Mobile Devices CrashReporter
Misc. Cache: Recent Items
                        Recent conversion of Calculator
                        Obsolete Items
                        QuickTime Content Guide
Under Maintenance Items:
Rebuild:
               LaunchServices
               dyld's shared cache
Short of taking this computer, packing it up, and hauling it down to the Apple Store for the 'Genius' to poke around in it, I am at a brick
wall as to what to do next. (I am useing this same computer to enter this message).
Here's hoping someone on the forum will have an answer.
Douglas J. Parker
P.S. Does APPLE Technicians ever read these discussion questions and interject their 'Expert' knowledge?

/Library/Preferences is where you will find that file.
#2 - yes

I created a new profile to fix a crashing problem and now I can't get my bookmarks.

Creating the new profile has fixed my crashing problem and I copied the recommended files and folders from my old profile to my new one but I still can't get my bookmarks. What am I doing wrong?

These can't get your data back, but will help in the future.
These add-ons can be a great help by backing up and restoring Firefox
'''[https://addons.mozilla.org/en-US/firefox/addon/febe/ FEBE (Firefox Environment Backup Extension)]''' {web link}
FEBE allows you to quickly and easily backup your
Firefox extensions, history, passwords, and more.
In fact, it goes beyond just backing up -- It will actually rebuild
your saved files individually into installable .xpi files.
It will also make backup of files that you choose.
'''[https://addons.mozilla.org/en-US/firefox/addon/opie/ OPIE]''' {web link}
Import/Export extension preferences

Shared folder access problem in j2ee application

Hi,
We are using SAP Netweaver 04s JAVA system.
In our j2ee application we are trying to access shared resource(file), but ejb is giving exception. Our code is as follows:
File srcDir = new File("\machine_namefolder");
if(!srcDir.exists())
{throw new Exception("directory does not exist", srcSys);
It gives expection "FileNotFoundException".
The same j2ee application is working fine when deployed on IBM Websphere.
We trired to access same shared path from windows, it is also working.
Please help us. Thanks in advance.
--sagar

Hi,
Please follow Shared Folder acess problem in J2ee application.
-Vladimir

Safari Crash - Problem with doodle (planer) app - doodle web links cause safari to crash with a very strange message "Error - Please make sure Safari is not used in Private Modus" (translated from german) No Privat Modus buttom in ios 7 safari settings!

Safari Crash - Problem with doodle (planer) app - doodle web links cause safari to crash with a very strange message "Error - Please make sure Safari is not used in Private Modus" (translated from german) No Privat Modus buttom in ios 7 safari settings! Works fine with an older Safari Version. Web link, call doodle app. You could see the website in the backround working but safari crashes after clicking on the error window. Any suggestions?

Turn off Private Browsing.
Tap "Private" on Safari Screen to disable Private Browsing. When top of screen is white, Private Browsing is off.

Premiere Elements 4.0, Crash problems when add trasition features

Operate a VAIO VGN-AW11XU,which was purchased in Dec. 2008 and was loaded with Premiere Elements 4.0
This is the most powerful multimedia VAIo, with all features installed like 4GB memory,Intel Centrino 2 processor T9600 (2.8 GHz),VISTA Ultimate, NVDIA 9600GT and dedicated GDDR3 Video Memory of 512 Mb.
I keep on getting CRASH problems especially when I try to add transition to my video clips. The problem message details are :
Problem Event Name: APPCRASH
Application Name: Adobe Premiere Elements.exe
Application Version: 4.0.0.0
Application Timestamp: 46f98f81
Fault Module Name: StackHash_06a9
Fault Module Version: 6.0.6001.18000
Fault Module Timestamp: 4791a7a6
Exception Code: c0000374
Exception Offset: 000b015d
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1032
Additional Information 1: 06a9
Additional Information 2: bc3df167e4e07c2f973b80c7de9b1a5b
Additional Information 3: a44f
Additional Information 4: 2a1b05c4d7cdba5c95e750c734db17fa
I have the latest QuickTime installed.
The camcorder is the SONY Handycam HDR-SR12E which records on a 120GB hard disc.
The video clips which were recorded with above camcorder, are ( SD )MPEG-2PS
Your help will be highly appreciated.
Thank you
Ilias

Μακάρι να μπορούσα να μιλήσω πολύ πράσινο, Ηλία! Αλλά θα χρησιμοποιείται μόνο το Google μεταφραστή! Εάν λειτουργεί, όμως, θα σας στείλουμε μια απάντηση στα αγγλικά και στα ελληνικά.
I do not know about the SD recording format with that camcorder. I am sorry. But, if your Premiere Elements project is set up for AVCHD, you should be able to edit AVCHD with that computer.
I do recommend optimizing Vista, however, so that you will get the best performance. Here's how to do it:
Δεν ξέρω για την SD μορφή εγγραφής που με βιντεοκάμερα. Λυπάμαι. Αλλά, αν σας Premiere Elements έργο που έχει συσταθεί για AVCHD, θα πρέπει να μπορείτε να επεξεργαστείτε AVCHD με αυτό τον υπολογιστή.
Εγώ συνιστούμε να βελτιστοποιήσετε Vista, όμως, έτσι ώστε θα έχετε την καλύτερη απόδοση. Να πώς να το κάνουμε:
http://www.adobeforums.com/webx/.3bc448a7
Also, make sure your Vista is updated to Service Pack 1.
Επίσης, βεβαιωθείτε ότι η ενημέρωση να είναι Vista Service Pack 1.

How to solve crash problem of firefox?

How to solve crash problem of firefox?

Hi Jamalzoal,
Dose your computer have the most recent iTunes on it? When you connect the iPad 2 to your computer what happens? dose iTunes tell you the iPad need to be restored?
p.s. you post this question in the Apple Remote Desktop community. You would probable have gotten more an fast responses if you posted this in the iPad community.

Anyone else having crash problems with mountain lion and parallels 8.0?

Anyone else having crash problems running Mountain Lion and Parallels 8.0 ?

Works OK so far for me. Take you issues to their forums for more direct help. These forums do not provide suport for Parallels.

CS4 Crashing Problems - Questions

Just curious in regards to all of these "CS4 Crashing" problems.
1) Before updating to Snow leopard, did you people do due diligence by at the very least checking the S.M.A.R.T. status of your drives and do a Permission Repair first BEFORE updating?
2) Did you make a clone of your working perfectly Leopard disk, or at least do a current (minutes before) Time machine backup?
3) Did you check first which 3rd party extensions such as those by Unsanity (FontCard), YouControl(Font), Growl, etc. that will NOT play nice with Snow Leopard yet until they are updated (if ever?)... and pre-update delete them?
4) Did you check to make sure that all of your fonts have been disabled and those that are NOT specifically from Apple, are removed from the User Font folders... and NOT set to load at startup?
Now after all of that... did ya still "freely" and without a gun to your head, update to Snow Leopard... a brand spankin' new (dot.zero) OS release and expect absolutely NO bugs: small, large or just inconvenient for the time being?
And now your whining here?... and complaining to Apple?
Have any of you considered reverting to your clone of Leo 10.5.8 until certain issues (yours) have been fail-safely fixed?
For the record, I did a straight-up SL update on a 2.16 CoreDuo MBP, and a 2008 8-core MacPro with NO problems! Everything working fine in 32-bit and 64-bit (MacPro), including even FreeHand under Rosetta.
NOTE: check your fonts!!! Whenever something crashes here or at any of my clients unexpectedly, font and/or font cache corruption has been the main culprit, now for over 20 years(!)

DocPixel-BMW wrote:
Well on one hand, I was guilty of letting out a rant against all of the whiners... on the other I was trying to be a bit helpful.
Maybe it will cause someone to think before starting another "Adobe or Apple must die or fix this" thread. It grates on the nerves... considering most should "fix" their expectations, upgrade habits, and most of all, the area between their ears first... BEFORE posting.
Welcome to the common sense club. A club with very few members.

Entries folder crash problem

Similar Messages

Maybe you are looking for