"Group" causing crash?

Hello,
I'm editing four sequences in a project, ranging from 2 minutes to 10 minutes. DVCPRO HD 720p 24p.
I had two sections of a wav grouped together, and out of nowhere, I moved them in the timeline slighly, and it crashed, giving me this:
Premiere Pro has encountered an error.
[..\..\Src\Sequence\PersistentGroupContainer.cpp-234]
Later I tried deleting them, and that crashed too! Finally, I ungrouped them, and now everything seems fine.
Has anyone else had this problem? Is the "group" function buggy? Should I stop using it? It's so handy!
Premiere Pro CS3 v3.2
Win XP SP2
Athlon X2 4200
2 GB DDR400
GeForce 8600GT
250GB system/320GB media hdd

You still out there looking at things? If so I have an update. The issue hasn't stopped, even though it did seemingly die down for awhile, however, it is now back with a vengeance.
I am able to force it to happen by killing the svchost process that is hosting GPSVC. If I run gpupdate /force, then logout/login it does get GPSVC running again. Furthermore, if I simply start svchost again via the Task Manager GPSVC starts running again.
When I access the server remotely with KVM it acts just like it does as if I'm logging into it via Citrix/RDP which for Admin IDs gives an error saying "Failed to connect to a windows service. Windows could not connect to the Group Policy Client service...",
however, normal user accounts just get a message when logging into the server "The Group Policy Client Service Failed the Logon. Access is denied."
I haven't opened a case with Microsoft yet, but we about ready to because of the increase in these errors.
If you have any further suggestions that would be great, otherwise I'll provide an update once I get word back from Microsoft.
**EDIT -- apparently I mistook the the server's SCM's actions as my own. I was able to successfully crash the GPSVC service by killing the hosting svchost process, however, after I crashed it and let it sit crashed for awhile when I attempted
to restart either by starting a svchost task, or running gpupdate /force it failed. Either that, or there is a timing issue where if we don't restart the svchost process, or run gpupdate /force quickly enough it won't be able to recover without a reboot.

Similar Messages

Windows xp, minidump, applemtm.sys caused crash

hi, my mbp just crashed in windows xp.
remained minidump said, applemtm.sys caused crash...
^^ i know this info is too little figure out the problem...
but, is there anyone faced like this one?
-------- minidump -----
ATTEMPTEDSWITCH_FROMDPC (b8)
A wait operation, attach process, or yield was attempted from a DPC routine.
This is an illegal operation and the stack track will lead to the offending
code and original DPC routine.
Arguments:
Arg1: 00000000, Original thread which is the cause of the failure
Arg2: 00000000, New thread
Arg3: 00000000, Stack address of the original thread
Arg4: 00000000
Debugging Details:
*** Kernel symbols are WRONG. Please fix symbols to do analysis.
* Your debugger is not using the correct symbols *
* In order for this command to work properly, your symbol path *
* must point to .pdb files that have full type information. *
* Certain .pdb files (such as the public OS symbols) do not *
* contain the required information. Contact the group that *
* provided you with these symbols if you need this command to *
* work. *
* Type referenced: nt!_KPRCB *
* Your debugger is not using the correct symbols *
* In order for this command to work properly, your symbol path *
* must point to .pdb files that have full type information. *
* Certain .pdb files (such as the public OS symbols) do not *
* contain the required information. Contact the group that *
* provided you with these symbols if you need this command to *
* work. *
* Type referenced: nt!KPRCB *
* Your debugger is not using the correct symbols *
* In order for this command to work properly, your symbol path *
* must point to .pdb files that have full type information. *
* Certain .pdb files (such as the public OS symbols) do not *
* contain the required information. Contact the group that *
* provided you with these symbols if you need this command to *
* work. *
* Type referenced: nt!_KPRCB *
* Your debugger is not using the correct symbols *
* In order for this command to work properly, your symbol path *
* must point to .pdb files that have full type information. *
* Certain .pdb files (such as the public OS symbols) do not *
* contain the required information. Contact the group that *
* provided you with these symbols if you need this command to *
* work. *
* Type referenced: nt!KPRCB *
* Your debugger is not using the correct symbols *
* In order for this command to work properly, your symbol path *
* must point to .pdb files that have full type information. *
* Certain .pdb files (such as the public OS symbols) do not *
* contain the required information. Contact the group that *
* provided you with these symbols if you need this command to *
* work. *
* Type referenced: nt!_KPRCB *
* Your debugger is not using the correct symbols *
* In order for this command to work properly, your symbol path *
* must point to .pdb files that have full type information. *
* Certain .pdb files (such as the public OS symbols) do not *
* contain the required information. Contact the group that *
* provided you with these symbols if you need this command to *
* work. *
* Type referenced: nt!_KPRCB *
* Your debugger is not using the correct symbols *
* In order for this command to work properly, your symbol path *
* must point to .pdb files that have full type information. *
* Certain .pdb files (such as the public OS symbols) do not *
* contain the required information. Contact the group that *
* provided you with these symbols if you need this command to *
* work. *
* Type referenced: nt!_KPRCB *
* Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: *
* using the NT_SYMBOLPATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
* Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: *
* using the NT_SYMBOLPATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
FAULTING_MODULE: 804d9000 nt
DEBUGFLR_IMAGETIMESTAMP: 47685ec5
CUSTOMERCRASHCOUNT: 1
DEFAULTBUCKETID: WRONG_SYMBOLS
BUGCHECK_STR: 0xB8
LASTCONTROLTRANSFER: from 80547c4b to 804fbf0e
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
bacd3c8c 80547c4b 000000b8 ffffffff 00000202 nt+0x22f0e
bacd3ce4 b7e06569 00000000 00000000 00000000 nt+0x6ec4b
bacd3d10 b7e4be4a 8a1711d8 00000000 8a451e08 Wdf01000+0x15569
bacd3d2c b7fcb53b 8a171290 75dc0430 8a23fbc8 Wdf01000+0x5ae4a
bacd3d4c b7fcb651 75bae3b8 8a00de70 bacd3da8 applemtm+0x53b
bacd3d5c b7e261b2 760ef150 75dfc680 bacd3d80 applemtm+0x651
bacd3da8 b7e26253 b7e57a08 8a203978 89f10ea8 Wdf01000+0x351b2
bacd3dc0 b7dfd5d3 8a00df97 8a203978 00000000 Wdf01000+0x35253
bacd3ddc b7dfd68d 01f10ea8 8962e450 bacd3e08 Wdf01000+0xc5d3
bacd3dec 804f280d 8a46c5a8 8a00de70 89f10ea8 Wdf01000+0xc68d
bacd3e08 804f36b0 8a46c5a8 8a00de70 8962e450 nt+0x1980d
bacd3e38 b99210d5 8a00de70 88da4980 8a2d3028 nt+0x1a6b0
bacd3ea0 b9921d47 895bd170 00000000 8a2d37d8 USBPORT+0xa0d5
bacd3ed0 b9922944 026e6f44 8a2d30e0 8a2d30e0 USBPORT+0xad47
bacd3f08 b992413a 8a2d3028 80548abc 8a2d3230 USBPORT+0xb944
bacd3f34 b993224b 8a2d3028 80548abc 8a2d3028 USBPORT+0xd13a
bacd3f70 b99323c2 8a2d3028 00000001 8a34a834 USBPORT+0x1b24b
bacd3f8c ba6b8d54 8a2d364c 6b755044 00000000 USBPORT+0x1b3c2
bacd3fbc 8a34adb2 8a34a310 b993225c bacd3fd0 sptd+0x11d54
bacd3fc0 8a34a310 b993225c bacd3fd0 80547e6f 0x8a34adb2
bacd3fc4 b993225c bacd3fd0 80547e6f 8a2d364c 0x8a34a310
bacd3fc8 bacd3fd0 80547e6f 8a2d364c 8a2d3028 USBPORT+0x1b25c
bacd3fcc 80547e6f 8a2d364c 8a2d3028 00000000 0xbacd3fd0
bacd3fd0 8a2d364c 8a2d3028 00000000 00000000 nt+0x6ee6f
bacd3fd4 8a2d3028 00000000 00000000 b401ff4a 0x8a2d364c
bacd3fd8 00000000 00000000 b401ff4a 6803fe95 0x8a2d3028
STACK_COMMAND: kb
FOLLOWUP_IP:
applemtm+53b
b7fcb53b ?? ???
SYMBOLSTACKINDEX: 4
SYMBOL_NAME: applemtm+53b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: applemtm
IMAGE_NAME: applemtm.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------

My MBP crashed with exactly the same dump. The crashes occurred during a StandBy operation (My MBP crashed regularly but not reproducably while trying to stand by/sleep).
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\vas\Desktop\Mini070508-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srvc:symbolshttp://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\i386
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpspsp2rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sat Jul 5 22:53:49.999 2008 (GMT-7)
System Uptime: 0 days 22:33:47.814
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck B8, {0, 0, 0, 0}
* WARNING: Unable to verify timestamp for applemtm.sys
* ERROR: Module load completed but symbols could not be loaded for applemtm.sys
Probably caused by : applemtm.sys ( applemtm+53b )
Followup: MachineOwner
1: kd> !analyze -v
* Bugcheck Analysis *
ATTEMPTEDSWITCH_FROMDPC (b8)
A wait operation, attach process, or yield was attempted from a DPC routine.
This is an illegal operation and the stack track will lead to the offending
code and original DPC routine.
Arguments:
Arg1: 00000000, Original thread which is the cause of the failure
Arg2: 00000000, New thread
Arg3: 00000000, Stack address of the original thread
Arg4: 00000000
Debugging Details:
CUSTOMERCRASHCOUNT: 1
DEFAULTBUCKETID: DRIVER_FAULT
BUGCHECK_STR: 0xB8
PROCESS_NAME: System
LASTCONTROLTRANSFER: from 80544c3b to 804f9c12
STACK_TEXT:
bace7ccc 80544c3b 000000b8 ffffffff 00000202 nt!KeBugCheck+0x14
bace7cdc 8054498b bace7d24 88d3b418 bab40120 nt!ScPatchFxe+0x46
bace7cf0 80502b17 88d3b488 88d3b418 804fad6c nt!KiSwapContext+0x2f
bace7cfc 804fad6c 00000000 00000000 8a19a4b0 nt!KiSwapThread+0x6b
bace7d24 b7022569 00000000 00000000 00000000 nt!KeWaitForSingleObject+0x1c2
bace7d50 b7067e4a 8a0c2a30 00000000 8a37efb0 Wdf01000!FxWaitLockInternal::AcquireLock+0x3a
bace7d6c b939853b 8a0c2ae8 75e65b78 8a19a480 Wdf01000!imp_WdfWaitLockAcquire+0xc9
WARNING: Stack unwind information not available. Following frames may be wrong.
bace7d8c b9398651 75c81210 89eee008 bace7de8 applemtm+0x53b
bace7d9c b70421b2 764c7c80 7652beb8 bace7dc0 applemtm+0x651
bace7de8 b7042253 b7073a08 89ad4140 89b38378 Wdf01000!FxRequestBase::CompleteSubmittedNoContext+0x63
bace7e00 b70195d3 89eee12f 89ad4140 00000000 Wdf01000!FxRequestBase::CompleteSubmitted+0x97
bace7e1c b701968d 01b38378 88a9ed80 bace7e48 Wdf01000!FxIoTarget::RequestCompletionRoutine+0x195
bace7e2c 804f053f 8a053350 89eee008 89b38378 Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x35
bace7e48 804f13e2 8a053350 89eee008 88a9ed80 nt!IopUnloadSafeCompletion+0x1d
bace7e78 b9843ee5 89eee008 892f5ee0 8a25c028 nt!IopfCompleteRequest+0xa2
bace7ee0 b9844b57 89bdc4a8 00000000 8a25c7d8 USBPORT!USBPORT_CompleteTransfer+0x373
bace7f10 b9845754 026e6f44 8a25c0e0 8a25c0e0 USBPORT!USBPORT_DoneTransfer+0x137
bace7f48 b9846f6a 8a25c028 80545aac 8a25c230 USBPORT!USBPORT_FlushDoneTransferList+0x16c
bace7f74 b9854fb0 8a25c028 80545aac 8a25c028 USBPORT!USBPORT_DpcWorker+0x224
bace7fb0 b9855128 8a25c028 00000001 89edc578 USBPORT!USBPORT_IsrDpcWorker+0x37e
bace7fcc 80544e5f 8a25c64c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
bace7ff4 805449cb b3f6362c 00000000 00000000 nt!KiRetireDpcList+0x61
bace7ff8 b3f6362c 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2b
805449cb 00000000 00000009 0081850f bb830000 0xb3f6362c
STACK_COMMAND: kb
FOLLOWUP_IP:
applemtm+53b
b939853b ?? ???
SYMBOLSTACKINDEX: 7
SYMBOL_NAME: applemtm+53b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: applemtm
IMAGE_NAME: applemtm.sys
DEBUGFLR_IMAGETIMESTAMP: 47685ec5
FAILUREBUCKETID: 0xB8_applemtm+53b
BUCKET_ID: 0xB8_applemtm+53b
Followup: MachineOwner
Message was edited by: tourist604

Photoshop CS4 and graphic cards. Can cause crashing?

Since upgrading to CS4 I seem to have increased crashing.
Here are my system specs.
Mac 2 x 2.66 GHz Dual-Core Intel Xeon
9 GB of Ram
250 GB internal dedicated scratch disc
NVDIA GeForce 7300 GT with 256 VRAM
After having endless techs look at my machine and upgrading everything. I am beginning to suspect the graphics card.
With OpenGL can a underperforming video card cause crashing in photoshop especially with massive file sizes ( multilayered CMYK poster sized files the can exceed 7 GB)?

Did you install the 11.0.1 update?
Is your OS up to date with patches?
Have you tried disabling OpenGL in preferences to avoid using the GPU/Graphics card?

AutoVue viewer caused crash while viewing .XSLX documents.

We use AutoVue Desktop Deployment Viewer incorporated in our application (using JNI). When viewing XLSX (Microsoft Excel) documents on Windows 8.1 x64 system it caused crash of application. It's reproducible only on Windows 8 (8.1 or Server2012) systems. If we set compatibility mode (Windows 7) then problem isn't reproducible.

I would recommend you log a ticket with customer support

CC 2014 (18.1.0) | Text Field editing causing crashes (Windows)

Greetings;
I've noticed lately that when saving files from CC 2014 to a CS6 format - and having those files edited on Mac, in either CS6 or CC - when re-opening those files text fields have been causing crashes on the Windows client. When that same file is opened and text fields are edited on the Mac client, a prompt will just appear stating "Cannot Edit text" - yet it still allows it.
This has caused multiple issues for our teams as it has created files we're starting to refer to as "mine fields" - as working with the .ai file is like playing Russian roulette with text fields, you never know which one is going to crash the file.
I would love to work with a team member from Adobe to help find a resolution to the problem, and I'm willing to provide any additional details that might aid in that process.
Thanks!

Hello Pureweb,
Please upload the crashdumps on some file sharing website say Dropbox and share the link with us by sending a mail to "[email protected]". We will analyze the dump and will suggest you the workaround appropriately.
In parallel, please check that you do not have any 3rd Party plugins installed in it. Please try to remove them one-by-one and see which one causes the crashes or do reverse i.e. remove all the 3rd party plugins. Or Uninstall Ai and check at following location:
C:\Program Files\Adobe\Adobe Illustrator CC 2014
Please verify that nothing is left at above location on uninstalling Ai. Then try a fresh install and see if Ai works.
Also, verify that you have the updated Wacom drivers on your system. This might be an issue with the 3rd party program as well. One of the user who was having a similar issue reported on the Ai forum that one of the 3rd party Stahl's ImageWorx DTG RIP - a program for printing to a Direct To Garment printer was causing the issue. So, you may check if the similar thing is not happening in your case.
Regards,
Dhirendra

Barn doors transition causes crash

Dear Community,
Applied barn doors transition to a project in CS4. Stored that project in 2010.
Opened the project in CS6 CC - and barn doors caused crashes - so I cleaned off the old and applied replacement barn door transitions in CS6 CC.
Once the wipe is applied - its fairly stable - sometime crashes sometimes doesn't.
If I apply a broder colour to the wipe - all ok.
If I then apply a border thickness - crash every time.
System;
Premiere Pro CS6 - 6.0.3 (001 (MC: 264587)) through cloud membership
Updated and current
Win 7 Pro - SP1 - 64 Bit
Source footage SONY EX3 - .mp4 and still image .png's
No error messages - just crash and need to restart PP CS6
Try to apply colour and border to a barn door transition causes the error
This worked before on the smae project when created in CS4
Not running other software at the time
NewBlueFX modules installed but not applied to this area of sequence
i7 - 3.20GHz, 16GB RAM, SSD OS drive, 4 x drive RAID on LSI RAID card, - No I/O hardware
I am using Are you using Mercury Playback Engine Acceleration and CUDA
Problem occurs during normal edit - as soon as I start to adjust the barn doors wipe - I don't get to compression
Thanks
Dave

Doies it help anyone that I just received this from the email address; [email protected];
Hello,
You have received this email because the content you posted below has been rejected by our moderators.
Re: Barn doors transition causes crash
posted Jun 5, 2013 5:15 PM
Since the original report earlier today - I now just have to put the timeline scrubber over the barn doors transition and PP CS6 closes without an error message and without saving. The unfortunate part here is there doesn't seem to be any record or log of the crashes to be able to disseminate whats going wrong.
Barn doors worked in CS4 - and the only change in this project is the re-opening in CS6 CC."
Question; Did I put something in there that was defammatory, rude, obnoxious, incorrect or un-helpful?
If anyone here believes I did, I sincerely apologise for the need of moderators to have intervened... and for causing any offence.

Photoshop Elements 10 Group Shot Crashes

Photoshop Elements 10 - Group Shot Crashes after I select the option from the menu. I am using Windows XP. Is there a workaround or is there a way to fix this?

This problem is related to your other problems and so resetting the preferences and deleting the preferences files "might" resolve itself.

Photoshop CC Content - Aware Move Tool causes crash

Does anyone have any ideas why this is happening? Content Aware Move tool causes crash every time so far with tiff and jpegs and its getting frustrating!
I have Windows 8.1 Pro with 8GB RAM
NVIDIA GeForce GT 650M Graphics
Photoshop CC 64 bit

Thanks for the reply JJMack - I have to be honest, i'm not exactly sure what i'm looking for here!
Source
Adobe Photoshop CC 2014
Summary
Stopped working
Date
06/04/2015 09:45
Status
Report sent
Description
Faulting Application Path: C:\Program Files\Adobe\Adobe Photoshop CC 2014\Photoshop.exe
Problem signature
Problem Event Name: APPCRASH
Application Name: Photoshop.exe
Application Version: 15.2.2.310
Application Timestamp: 5480338c
Fault Module Name: FaceDetection.dll
Fault Module Version: 2.2.6.32411
Fault Module Timestamp: 52e12400
Exception Code: c0000005
Exception Offset: 000000000001704d
OS Version: 6.3.9600.2.0.0.256.48
Locale ID: 2057
Additional Information 1: e87c
Additional Information 2: e87c816cbb2acbf5e54624fc2b1f98cc
Additional Information 3: 1879
Additional Information 4: 1879b998534215d47b0a850e45784427
Extra information about the problem
Bucket ID: 2dac81db98a57fddf5997edfd40ba6eb (85993531415)

HT5704 Hi, Two recent updates for my iPhone have caused crashes (down the white lead via iTunes).I have "fixed" but not sure of the cause?

Hi,
Two recent updates for my iPhone have caused crashes (down the white lead) via iTunes.
I have "fixed" but I don't know the cause?
Each time the update does n't complete.
The download does n't happen.
The computer & internet connection are good.
It is as if the Apple server does n't complete?
The phone stays in recovery mode, until you reset and rebuild in iTunes.
All software is up to date, but I can't find the cause
ANY IDEAS?
Regards,
P.
<Email Edited by Host>

No error messages.
It just fails to complete the download, so recovery mode is the next step.
This can be over a period of eight hours or more!
I have so many (original) Apple USB leads that I would n't know if I have been using the same one (if it was faulty).
Does this sound like a "common" problem?

Why Does 3D Reposse cause crashes and work so slow?

Why Does 3D Reposse cause crashes and work so slow? I get the pinwheel of death when I use this feature. It works at a snails pace. I liked the 3D Type effects in iIllustrator. Why couldn't Adobe have added all the Reposse features to Illustrator instead of craming all these new features into Photoshop?
They're worthless if the program needs an hour to process every selection.

What are your OS specs, your Video Card and your Preferences > Performance settings?
Why Does 3D Reposse cause crashes and work so slow?
My guess would be because it has to create a whole bunch of polygons and your computer-set-up may be insufficient for the task.

Firefox causes crash when using Youtube explorer does not have the same effect

firefox causes crash when using Youtube explorer does not have the same effect

Troubleshooting extensions and themes
* https://support.mozilla.com/en-US/kb/Troubleshooting%20extensions%20and%20themes
Check and tell if its working.

Access violation (0xC0000005) cause crash

Access violation (0xC0000005) cause crash. The crash report is as blow. It may be caused by the function IMAQ FillHole. How this function crash?
Who knows why? Thank you!
#Date: 2014年8月12日 14:21:51
#OSName: Windows 7 Ultimate
#OSVers: 6.1
#OSBuild: 7600
#AppName:
#Version: 12.0 32-bit
#AppKind: AppLib
#AppModDate: 08/12/2014 06:17 GMT
#LabVIEW Base Address: 0x30000000
<LVExec>
{"a":[
"vi": "D\\VISION_SYSTEM\\build\\MyProgram.exe\\IMAQ FillHole",
"ctx": "主应用程序实例",
"type": "subVI"
"vi": "D\\VISION_SYSTEM\\build\\MyProgram.exe\\ccd2表面2二值化.vi",
"ctx": "主应用程序实例",
"type": "subVI"
</LVExec>
<DEBUG_OUTPUT>
2014/8/12 16:48:15.894
Crash 0x0: Crash caught by NIER
File Unknown(0) : Crash 0x0: Crash caught by NIER
minidump id: 6e35643f-8ff2-49e6-bbde-98bac2ffa48a
ExceptionCode: 0xC0000005$N
</DEBUG_OUTPUT>
0x307277B4 - lvrt <unknown> + 0
0x30727B38 - lvrt <unknown> + 0
0x7C37FDB4 - MSVCR71 <unknown> + 0
0x77CA5A74 - ntdll <unknown> + 0
0x77C8B3C8 - ntdll <unknown> + 0
0x00000000 - <unknown> <unknown> + 0
Solved!
Go to Solution.
Attachments:
ccd2表面2二值化.vi ‏21 KB

Hi,
please stick with your original thread! Don't create double posts!
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Smart group causes Mail to crash

I created a smart group that immediately caused Mail (3.6 (936)) to crash (apparently).
Since, I have been unable to launch Mail normally - it starts with the smart group in question selected, and then crashes, I need to force quit it.
I have tried to launch Mail with shift pressed down. It starts, and works, up to the moment I select this smart group. I can modify it, and perform delete command, but this is never executed, Mail crashes... Any suggestions?

hmibrooklyn I tried and failed to get Mail to crash by following what you described. Until someone else has anything more constructive to add I suggest the following, in no particular order. Try each suggestion and determine if any one of them keeps Mail from crashing.
Try copying the text from Pages, but instead of pasting it select Paste and Match Style from Mail's Edit menu before formatting it as a numbered list.
Before composing the message select Make Plain Text from Mail's Format menu.
If you have more than one Mail account, perform the same action using a different Mail account.
Open Font Book - it's in your Applications folder. Select All Fonts from the Collections column, then select any of the fonts in the adjoining column, then Select All from the Edit menu. Then, select Validate Fonts from the File menu.
The end result ought to resemble the following screenshot. If it does not, report any errors it encounters.
Create a new, temporary User account to determine if the problem exists while using it instead of your usual one: Isolating an issue by using another user account
You will have to configure a Mail account for the temporary User account, but you can use the settings from the existing Mail account.
Delete the temporary User account when you are finished with it.
That's all I can think of for now.

Unknown Group - Causes Finder Crash - How do I change group?

Many directories and files on my system after installing Leopard have an "Unknown" group and when I open a "Get Info" window on them and click the "Add" button the beachball appears and Finder crashes.
MacFixit stated "This problem appears to be due to a bad group setting. You can alleviate the issue by putting afflicted users back into the "Staff" group (GID 20) via the following Terminal command:
sudo dscl . append /Groups/staff GroupMembership username
(where "username" is replaced by the afflicted user's name)."
However, this did not solve my problem. Said files and directories still have "uknown" groups and Finder still crashes when I click the "Add" button in the Get Info window.
How to fix?

McToast wrote:
In Tiger, a group with the same name as your username would be created and the UID and GID would match. However, Leopard doesn't seem to be doing that anymore.
No, now it has reverted to the behaviour of 10.2 and before. All normal user accounts were made members of the "staff" group by default. admin users were also made members of the "admin" group, plus a couple of others. There are a lot more in Leopard. Trust me, you will have far fewer problems if you make your primary group 20. Your 'id' output should ideally look like
macbook:~ michaelc$ id
uid=501(michaelc) gid=20(staff) groups=20(staff),98(lpadmin),81(appserveradm),
103(com.apple.sharepoint.group.3),102(com.apple.sharepoint.group.2),
101(com.apple.sharepoint.group.1),104(com.apple.sharepoint.group.4),
79(_appserverusr),80(admin)
(I put some new lines in there to stop the excessively long line).
I don't know what those sharepoint groups are, either, in case you're wondering

Subclips/Markers Causing Crash

Hello,
I have a strange event happening. I've captured a few tapes (NTSC DV, Anamorphic 16:9 48Khz) onto a Lacie external and used the 'DV stop start detect' to create markers and after labeling the markers create subclips out of them. This all works fine, BUT, after I save the file, quit the application, and go back into it again the application crashes about half way through the opening of the project file.
When I go into autosave and locate the file saved right before I create the subclips and do DV/Stop Start Detect, it opens no problem. The one right after the subclips are added crashes. I added the subclips twice just to make sure that was what was causing the problem.
Suggestions? Keep in mind that most of the video files are from a QuickStream DV device.
Thank you for any assitance.
PowerMac G5 2.7 GHz Mac OS X (10.4.3) 3GB RAM, 1TB Lacie external, FCP 5.0.4

Do you know if there is an application out there that will scan for bad quicktime files? I looked through all of them and they open normally in QuickTime, but there must be something that FinalCut doesn't like.
I'm afraid I'm not aware of any such program (though if you find one, let me know
From your description, I'll agree that your issue is very likely to be an issue with a corrupted media file. I'm afraid I can't suggest any speedy solution or workflow - you'll have to comb thru the media in the project one-by-one. (that is, re-import [not recapture] clips in smaller groups, since you're got 1000 clips. Wow.)

"Group" causing crash?

Similar Messages

Maybe you are looking for