Preview causes Compressor 4 to hang

Title says it all.  If the Preview window is open while I use Compressor, navigating through the app is extremely slow.  Once I close the Preview window there is no issue.
Important to note that this does not effect compression run times but simply performance of the Compressor app itself. 
Anyone else seeing this?  I'm using 4.0.3 on the Mac Mini Server in my sig.  Same issue occurs on  MacBook Pro 2.26 GHz C2D.

I've had similar stability issues with the Preview window in Compressor - though it doesn't sound as bad as you describe. I always leave the Preview window off. I only open it if I have to check what the output will look like. Sorry this ins't much help - but you're not the only one.

Similar Messages

  • Copying in Preview causes app to crash

    All of a sudden copying in Preview causes the app to hang briefly then exit. Anyone else having this problem and any ideas on a workaround for copying .pdf text?

    It depends on how the exe deals with the arguments. Some do honor escape characters, some not.....
    Afaik, there is no difference regarding the System Exec in development environment vs. exe. But it is possible, that these are executed using different user rights?
    Norbert
    CEO: What exactly is stopping us from doing this?
    Expert: Geometry
    Marketing Manager: Just ignore it.

  • Some emails from a particular sender causing Outlook 2010 to hang, task manager shows memory use spikes

    Posting this to the Exchange forum because I'm hoping there's a server-side solution.
    SOME emails received from an external sender (gmail.com address, not sure the mail client) are causing Outlook 2010 to hang when trying to open the email.  Outlook becomes non-responsive when viewing the email through the preview pane or by double-clicking
    the email.  If I open Task Manager I see that the outlook.exe process memory use starts increasing very quickly.  As far as I know the only resolution is to end the task and re-open Outlook (and avoid that email).
    I've found several excellent threads on these same symptoms, but there seems to be a variety of causes.  I've tried a bunch of things so far:
     - Tried opening from another system on our network running Outlook 2010, same issue. 
     - Tried opening from OWA, opens fine.
     - Tried exporting the email to a PST, then opening from a completely different system outside of our network, but still running Outlook 2010, same issue.
     - Tried exporting the email to a PST then opening from a completely different system outside of our network, running Outlook 2013, email opens fine.
     - Tried setting Outlook to open all emails as PLAIN TEXT, opens fine.
    Systems are running the latest Outlook 2010 SP and patches, and running a variety of OS's.  Only common denominator seems to be Outlook 2010.
    I was hoping to find a way to convert incoming emails from this sender to open as Plain Text using a Hub Transport rule, but cannot find a way to do it.
    Unfortunately I have no control over the sender, so don't know what could be triggering the problem.  
    Can anyone advise on a possible solution?  Any way to someone convert emails from a particular sender to Plain Text automatically?

    Either you inform the sender to configure in sender's outlook to send only to you in plain text please check this
    http://office.microsoft.com/en-001/outlook-help/change-the-message-format-to-html-rich-text-or-plain-text-HA101992313.aspx
    Or
    Call a macro in your outlook example below. Please check
    this for details
    Dim msg As MailItem
    For Each msg In myNS.GetDefaultFolder(olFolderInbox).Items
       If msg.Unread = True And _
         msg.SenderName = "Linda Cooper" Then
    Item.BodyFormat = olFormatPlain
       Else
         ' Message doesn't meet criteria.
       End If
    Thanks,
    MAS
    Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

  • WPF UI running in seperate runspace - able to set/get controls via synchronized hash table, but referencing the control via the hash table from within an event handler causes both runspaces to hang.

    I am trying to build a proof of concept where a WPF form is hosted in a seperate runspace and updates are handled from the primary shell/runspace. I have had some success thanks to a great article by Boe Prox, but I am having an issue I wanted to open up
    to see if anyone had a suggestion.
    My goals are as follows:
    1.) Set control properties from the primary runspace (Completed)
    2.) Get control properties from the primary runspace (Completed)
    3.) Respond to WPF form events in the UI runspace from the primary runspace (Kind of broken).
    I have the ability to read/write values to the form, but I am having difficulty with events. Specifically, I can fire and handle events, but the minute I try to reference the $SyncHash from within the event it appears to cause a blocking condition hanging both
    runspaces. As a result, I am unable to update the form based on an event being fired by a control.
    In the example below, the form is loaded and the following steps occur:
    1.) Update-Combobox is called and it populates the combobox with a list of service names and selects the first item.
    2.) update-textbox is called and sets the Text property of the textbox.
    3.) The Text value of the textbox is read by the function read-textbox and output using write-host.
    4.) An event handle is registered for the SelectionChanged event for the combobox to call the update-textbox function used earlier.
    5.) If you change the selection on the combobox, the shell and UI hangs as soon as $SyncHash is referenced. I suspect this is causing some sort of blocking condition from multiple threads trying to access the synchronized nature of the hash table, but I am
    unsure as to why / how to work around it. If you comment out the line "$SyncHash.TXT_Output.Dispatcher.Invoke("Send",[action]{$SyncHash.TXT_Output.Text = $Value})" within update-textbox the event handler will execute/complete.
    $UI_JobScript =
    try{
    Function New-Form ([XML]$XAML_Form){
    $XML_Node_Reader=(New-Object System.Xml.XmlNodeReader $XAML_Form)
    [Windows.Markup.XamlReader]::Load($XML_Node_Reader)
    try{
    Add-Type –AssemblyName PresentationFramework
    Add-Type –AssemblyName PresentationCore
    Add-Type –AssemblyName WindowsBase
    catch{
    Throw "Unable to load the requisite Windows Presentation Foundation assemblies. Please verify that the .NET Framework 3.5 Service Pack 1 or later is installed on this system."
    $Form = New-Form -XAML_Form $SyncHash.XAML_Form
    $SyncHash.Form = $Form
    $SyncHash.CMB_Services = $SyncHash.Form.FindName("CMB_Services")
    $SyncHash.TXT_Output = $SyncHash.Form.FindName("TXT_Output")
    $SyncHash.Form.ShowDialog() | Out-Null
    $SyncHash.Error = $Error
    catch{
    write-host $_.Exception.Message
    #End UI_JobScript
    #Begin Main
    add-type -AssemblyName WindowsBase
    [XML]$XAML_Form = @"
    <Window xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml">
    <Window.Resources>
    <DataTemplate x:Key="DTMPL_Name">
    <TextBlock Text="{Binding Path=Name}" />
    </DataTemplate>
    </Window.Resources>
    <DockPanel LastChildFill="True">
    <StackPanel Orientation="Horizontal" DockPanel.Dock="Top">
    <Label Name="LBL_Services" Content="Services:" />
    <ComboBox Name="CMB_Services" ItemTemplate="{StaticResource DTMPL_Name}"/>
    </StackPanel>
    <TextBox Name="TXT_Output"/>
    </DockPanel>
    </Window>
    $SyncHash = [hashtable]::Synchronized(@{})
    $SyncHash.Add("XAML_Form",$XAML_Form)
    $SyncHash.Add("InitialScript", $InitialScript)
    $Normal = [System.Windows.Threading.DispatcherPriority]::Normal
    $UI_Runspace =[RunspaceFactory]::CreateRunspace()
    $UI_Runspace.ApartmentState = [System.Threading.ApartmentState]::STA
    $UI_Runspace.ThreadOptions = [System.Management.Automation.Runspaces.PSThreadOptions]::ReuseThread
    $UI_Runspace.Open()
    $UI_Runspace.SessionStateProxy.SetVariable("SyncHash",$SyncHash)
    $UI_Pipeline = [PowerShell]::Create()
    $UI_Pipeline.Runspace=$UI_Runspace
    $UI_Pipeline.AddScript($UI_JobScript) | out-Null
    $Job = $UI_Pipeline.BeginInvoke()
    $SyncHash.ServiceList = get-service | select name, status | Sort-Object -Property Name
    Function Update-Combobox{
    write-host "`nBegin Update-Combobox [$(get-date)]"
    $SyncHash.CMB_Services.Dispatcher.Invoke($Normal,[action]{$SyncHash.CMB_Services.ItemsSource = $SyncHash.ServiceList})
    $SyncHash.CMB_Services.Dispatcher.Invoke($Normal,[action]{$SyncHash.CMB_Services.SelectedIndex = 0})
    write-host "`End Update-Combobox [$(get-date)]"
    Function Update-Textbox([string]$Value){
    write-host "`nBegin Update-Textbox [$(get-date)]"
    $SyncHash.TXT_Output.Dispatcher.Invoke("Send",[action]{$SyncHash.TXT_Output.Text = $Value})
    write-host "End Update-Textbox [$(get-date)]"
    Function Read-Textbox(){
    write-host "`nBegin Read-Textbox [$(get-date)]"
    $SyncHash.TXT_Output.Dispatcher.Invoke($Normal,[action]{$Global:Return = $SyncHash.TXT_Output.Text})
    $Global:Return
    remove-variable -Name Return -scope Global
    write-host "End Read-Textbox [$(get-date)]"
    #Give the form some time to load in the other runspace
    $MaxWaitCycles = 5
    while (($SyncHash.Form.IsInitialized -eq $Null)-and ($MaxWaitCycles -gt 0)){
    Start-Sleep -Milliseconds 200
    $MaxWaitCycles--
    Update-ComboBox
    Update-Textbox -Value $("Initial Load: $(get-date)")
    Write-Host "Value Read From Textbox: $(Read-TextBox)"
    Register-ObjectEvent -InputObject $SyncHash.CMB_Services -EventName SelectionChanged -SourceIdentifier "CMB_Services.SelectionChanged" -action {Update-Textbox -Value $("From Selection Changed Event: $(get-date)")}

    Thanks again for the responses. This may not be possible, but I thought I would throw it out there. I appreciate your help in looking into this.
    To clarify the "Respond to control events in the main runspace"... I'm would like to have an event generated by a form object in the UI runspace (ex: combo box selectionchanged event) trigger a delegate within the main runspace and have that delegate in
    the main runspace update the form in the UI runspace.
    ex:
    1.) User changes selection on combo box generating form event
    2.) Event calls delegate (which I have gotten to work)
    3.) Delegate does some basic processing (works)
    4.) Delegate attempts to update form in UI runspace (hangs)
    As to the delegates / which runspace they are running in. I see the $synchash variable if I run get-var within a delegate, but I do not see the $Form variable so I am assuming that they are in the main runspace. Do you agree with that assumption?

  • I have an email account causes the machine to hang up after being in use for a day.  It only occurs on my Macbook Pro and only one particular account.  The problem account works fine on my iMac and Windows Machines.  Any ideas what is causing this?

    I have an email account causes the machine to hang up after being in use for a day.  It only occurs on my Macbook Pro and only one particular account.  The problem account works fine on my iMac and Windows Machines.  I have been to the local Genius bar and through trial and error we have determined that Mail is working ok but somehow the account is causing the problem.  I have used this account for years.  Any ideas what is causing this?

    No idea why, but one thing you may try if you have the time, is create a new user, and set up the problem mail account in the new user space. See if it causes your MBP to hang as well.  That will tell you if it is something wrong with your main User, or something wrong with MBP.
    Assuming this works, I'd nuke the problem account in your main user space, re-start, and reinititate the account and see if that helps.
    Depening on how many email accounts you have setup, it may be necessary to nuke the whole Mail folder in your User/Library....   Hard way to get it to work, but just my idea.

  • Bridge 2014.2 won't preview AE text presets - just hangs

    Mac 10.10.1.
    As the title of the post says, Bridge 2014.2 won't preview AE text presets - just hangs. All programs up to date.
    Thought maybe it was the presets, tried previewing the presets from CS6, nope. Bridge2014.2 hangs.
    Can't try CS6 Bridge as I can't install this via cloud subscription.
    This is a real pain in the butt.

    Version of Bridge? OS? Are you up to date? Mine works just fine on OSX 10.10.1 and Bridge 6.1.0.115

  • The action file print causes PS CS5 to hang, stop responding

    The action file print causes PS CS5 to hang, stop responding
    Its installed on a Win 7 64 bit PC i7 with 6G ram
    PS is version 12.0.4 64 bit
    The print dialouge box does come up eventualy around 10 mins later (some times).   While waiting PS is totaly dead and the task manager shows it as not responding
    Anyone got any ideas?

    I might suggest seeking out an updated printer driver to see if that will help.
    Is it possible you have a network path configured in there somewhere that's pointing to something no longer available on your network?
    -Noel

  • Enabling Drill Through causing Essbase Integration Server hang.

    During the automation process using olapicmd command and *.cbs we are enabling Drill Through which is causing Essbase Integration Server hang.
    We don't get any error message in log file. Plus sometime its run successful , also when we run this manually going to EIS console, it run fine.
    Thanks in advance
    -Piyush

    Hi Kishore,
    Thanks for your prompt reply......
    I have checked in before itself the Drill down option ......
    I am not able to understand whats the issue we are able to drill through in EIS till last level but after improting in OBIEE we are not able to drill through to last level, in the last level it showing no results....
    I am not able to find the solution any other suggestions ?
    Regards,
    Tarang Jain

  • Firefox regularly hangs after an unspecified period of use, and causes other programs to hang, and a forced system shutdown is necessary.

    The firefox browser hangs after an unspecified period of time. Anything from a few minutes after system startup, up to 5-6 hours of use or perhaps more. Attempting to use other programs including windows explorer while firefox is hanging causes those programs to hang also, making a forced shutdown necessary. Occaisionally I've noticed firefox will respond, perhaps after 10 or more minutes. There seems to be no hard disk activity while the program hangs. Memory usage of firefox on my system is usually upwards of 190,000.

    I have circumvented this mostly by running internet explorer, and using Firefox only for browsing when I need to make use of it's addons. In this way I've had the problem re-occur maybe once or twice in the past two weeks. It's not really a solution but it does seem to help, and I'm no longer sure the problem IS firefox but using it certainly exacerbates the problem.
    I've only just updated to firefox 6, so I am not entirely sure how that will go just yet.

  • Compressor 4 causing other programs to hang...

    I just used Compressor 4 to transcode 3 roughly 3.5 minute long 720p25 Quicktime None files to Quicktime ProRes 422.
    I must say, it was faster than I remember it being in the past (despite not neing 64-bit yet!!), but it made everything else on my computer (Safari, Mail, Echofon, iTunes) hang with beach balls until it was done.
    Surely that isn't right?!   Especially for a 2011 Quad 2.3 i7 MBP w/ 8GB RAM and on an SSD!!
    Anyone else having similar issues?

    compressor 3.5 uses qmaster to actually render transcodes and that definitely runs nice (bottom priority, no beach balls) i would assume that if you get beach balls maybe the new qmaster doesn't run as nice process, either that or there are bigger issues at hand.

  • Does previewing mpeg-2 files cause the Finder to hang in Leopard?

    In Tiger, previewing an mpeg-2 file in column view in the Finder causes a spinning beach ball for ages. Has this been fixed in Leopard?

    This is probably your Norton software doing its best to ruin your mac.
    I would start by trying to uninstall the Norton/symantec stuff. Then take any of the norton installer discs you have and burn them. I would also bury the ashes.
    Maybe a safe boot would work to try to start up so you can uninstall the norton.
    Barring that you may just have to start from scratch and reinstall everything (except the norton stuff).
    Then never never never buy anything from symantec again.
    Hope this helps.

  • Closing the Report Viewer causes the application to hang

    Hi,
    Since a few days we are experiencing some problems with the Crystal Reports viewer. When closing a report viewer in our application, the application hangs for a few minutes. The strange thing is, that it only seems to happen on Windows 7 and Windows 2008 R2 Server.
    Our application with the integrated Crystal Report Viewer is running on 2 application servers :
    - Windows 2008 Server, versie 6.0 Build 6002, Service Pack 2
    - Windows 2008 R2 Server versie 6.1, Build 7600
    Crystal Reports version installed on both servers : 12.01.0007.1144
    On the 2008 Server, the application works correctly.
    On the 2008 R2 server, the application hangs for about 5 minutes while closing the report preview window.
    Both server have exactly the same version of Crystal Reports and the same application version.
    I'm having the same issue on a Windows 7 x64 (6.1 Build 7600).
    I've installed all updates and hotfixes up to SP3 Fix Pack (12.3.3.812 / 12.3.2003.812) but I'm still having the same problem.
    We didn't have this problem until a few days ago, so I assume it has something to do with a windows update which only affects Windows 7 and Windows 2008 R2.
    Please advice us with a possible workaround, because our application is distributed to a few thousand users ...
    Some more debug info :
    This is the call of from the main thread when the application hangs :
         [Managed to Native Transition]     
    >     mscorlib.dll!System.__ComObject.ReleaseSelf() + 0x5 bytes     
         mscorlib.dll!System.Runtime.InteropServices.Marshal.ReleaseComObject(object o) + 0x8b bytes     
         CrystalDecisions.Shared.dll!CrystalDecisions.Shared.SharedUtils.ReleaseComObject(object obj = {CrystalDecisions.ReportAppServer.ClientDoc.ReportClientDocumentClass}) + 0x75 bytes     
         CrystalDecisions.CrystalReports.Engine.dll!CrystalDecisions.ReportAppServer.ISCDClientDocumentEvents_EventProvider.Dispose(bool bDisposeManaged = true) + 0x1a2 bytes     
         CrystalDecisions.CrystalReports.Engine.dll!CrystalDecisions.ReportAppServer.ISCDClientDocumentEvents_EventProvider.Dispose() + 0x32 bytes     
         CrystalDecisions.CrystalReports.Engine.dll!CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.DisconnectEventRelay() + 0xfc bytes     
         CrystalDecisions.CrystalReports.Engine.dll!CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.InternalClose(bool bSetupForNextReport = false, bool bAutoClose = true) + 0x10e bytes     
         CrystalDecisions.CrystalReports.Engine.dll!CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.Dispose(bool bDisposeManaged = true) + 0xad bytes     
         System.dll!System.ComponentModel.Component.Dispose() + 0x12 bytes     
         CrystalDecisions.CrystalReports.Engine.dll!CrystalDecisions.CrystalReports.Engine.ReportDocument.ClearCache(bool clearDocument = true) + 0x9d bytes     
         CrystalDecisions.CrystalReports.Engine.dll!CrystalDecisions.CrystalReports.Engine.ReportDocument.InternalClose(bool bSetupForNextReport = true) + 0x81 bytes     
         CrystalDecisions.CrystalReports.Engine.dll!CrystalDecisions.CrystalReports.Engine.ReportDocument.Close() + 0x3f bytes     
         SyDelSoftControlLibCrystalReports.dll!SyDelSoft.ControlLib.CrystalReports.cReportForm.Dispose(bool disposing = true) + 0x55 bytes     
         SDProjects.exe!SDProjects.GUI.ReportForm.Dispose(bool disposing) + 0x38 bytes     
    SharedUtils.ReleaseComObject
    Kind regards,
    Frederic Hoornaert

    CrystalReportsDisposeIssue.crpe.Diagnostics.0.log
    --> Form3 closed
    ..\..\src\print\datasource\datasrc2.cpp:535,Releasing subreport data sources,Start Time,"17:39:17"
    N/A:-1,Releasing subreport data sources,Elapsed Time,"1"
    ..\..\src\crpe\crpe.cpp:791,Closing engine,Start Time,"17:39:17"
    ..\..\src\crpe\crpe.cpp:833,Closing engine,Before close engine use count,"7"
    ..\..\src\crpe\crpe.cpp:858,Closing engine,After close engine use count,"6"
    N/A:-1,Closing engine,Elapsed Time,"2"
    ..\..\src\crpe\crpe.cpp:791,Closing engine,Start Time,"17:39:17"
    ..\..\src\crpe\crpe.cpp:833,Closing engine,Before close engine use count,"6"
    ..\..\src\crpe\crpe.cpp:858,Closing engine,After close engine use count,"5"
    N/A:-1,Closing engine,Elapsed Time,"2"
    --> Form2 closed
    ..\..\src\print\datasource\datasrc2.cpp:535,Releasing subreport data sources,Start Time,"17:39:52"
    N/A:-1,Releasing subreport data sources,Elapsed Time,"1"
    ..\..\src\crpe\crpe.cpp:791,Closing engine,Start Time,"17:39:52"
    ..\..\src\crpe\crpe.cpp:833,Closing engine,Before close engine use count,"4"
    ..\..\src\crpe\crpe.cpp:858,Closing engine,After close engine use count,"3"
    N/A:-1,Closing engine,Elapsed Time,"2"
    --> Form1 closed..\..\src\print\datasource\datasrc2.cpp:535,Releasing subreport data sources,Start Time,"17:40:29"
    N/A:-1,Releasing subreport data sources,Elapsed Time,"1"
    ..\..\src\crpe\crpe.cpp:791,Closing engine,Start Time,"17:40:29"
    ..\..\src\crpe\crpe.cpp:833,Closing engine,Before close engine use count,"2"
    ..\..\src\crpe\crpe.cpp:858,Closing engine,After close engine use count,"1"
    N/A:-1,Closing engine,Elapsed Time,"2"
    ..\..\src\crpe\crpe.cpp:791,Closing engine,Start Time,"17:40:29"
    ..\..\src\crpe\crpe.cpp:833,Closing engine,Before close engine use count,"1"
    ..\..\src\crpe\crpe.cpp:858,Closing engine,After close engine use count,"0"
    N/A:-1,Closing engine,Elapsed Time,"100017"
    CrystalReportsDisposeIssue.crpe.functions.0.log
    0xfb8     17:39:17.871          0     PESetUserSessionInfo               0     PEUserSessionInfoW:<StructSize:262><userName:><requestID:22>     IN          21     <==
    0xfb8     17:39:17.871     0     0     PESetUserSessionInfo               0     OUT     PEUserSessionInfoW:<StructSize:262><userName:><requestID:22>          21     <==
    0xfb8     17:39:17.874          3     PEClosePrintJob     report {657D0ECA-BC6A-4EC6-9476-02B77376E07C}.rpt          0     jobN:3     IN          22     <==
    0xfb8     17:39:17.874     36     3     PEClosePrintJob     report {657D0ECA-BC6A-4EC6-9476-02B77376E07C}.rpt          0     OUT     jobN:3          22     <==
    0xfb8     17:39:17.913          0     PECloseEngine               0     void     IN          22     <==
    0xfb8     17:39:17.913     3     0     PECloseEngine               0     OUT     void          22     <==
    0xfb8     17:39:17.923          0     PECloseEngine               0     void     IN          0     <==
    0xfb8     17:39:17.923     3     0     PECloseEngine               0     OUT     void          0     <==
    0xfb8     17:39:52.421          0     PESetUserSessionInfo               0     PEUserSessionInfoW:<StructSize:262><userName:><requestID:23>     IN          0     <==
    0xfb8     17:39:52.421     0     0     PESetUserSessionInfo               1032     OUT     PEUserSessionInfoW:<StructSize:262><userName:><requestID:23>          0     <==
    0xfb8     17:39:52.423          1     PEClosePrintJob     report {F2574C5C-00BC-4627-9A05-B8133D6E6F7D}.rpt          0     jobN:1     IN          0     <==
    0xfb8     17:39:52.423     15     1     PEClosePrintJob     report {F2574C5C-00BC-4627-9A05-B8133D6E6F7D}.rpt          0     OUT     jobN:1          0     <==
    0xfb8     17:39:52.441          0     PECloseEngine               0     void     IN          0     <==
    0xfb8     17:39:52.441     3     0     PECloseEngine               1032     OUT     void          0     <==
    0xfb8     17:40:29.281          0     PESetUserSessionInfo               0     PEUserSessionInfoW:<StructSize:262><userName:><requestID:24>     IN          0     <==
    0xfb8     17:40:29.281     0     0     PESetUserSessionInfo               1032     OUT     PEUserSessionInfoW:<StructSize:262><userName:><requestID:24>          0     <==
    0xfb8     17:40:29.283          2     PEClosePrintJob     report {C78FE11F-6465-478F-83AB-49D8F0C6D64A}.rpt          0     jobN:2     IN          0     <==
    0xfb8     17:40:29.283     24     2     PEClosePrintJob     report {C78FE11F-6465-478F-83AB-49D8F0C6D64A}.rpt          0     OUT     jobN:2          0     <==
    0xfb8     17:40:29.310          0     PECloseEngine               0     void     IN          0     <==
    0xfb8     17:40:29.310     2     0     PECloseEngine               1032     OUT     void          0     <==
    0x1568     17:40:29.315          0     PECloseEngine               0     void     IN          0     <==
    0x1568     17:40:29.315     100018     0     PECloseEngine               0     OUT     void          0     <==

  • Finder crashes with OS 10.6.8. With or without any apps running finder will hang repeatedly causing the iMac to hang also. I upgraded from 10.5.8 to 10.6.8 recently and finder was OK for 1 week. How do I submit a crash log?

    Folllowing an upgrade from 10.5.8 to 10.6.8  (Snow Leopard) Finder frequently hangs, causing any open apps and the iMac to hang. This will occur whether or not any 3rd party apps or Safari are open. About 50% of the time trying to empty the trash will cause a finder hang. There are no error messages to let me know what code such a hang may be. Repeated attempts to force quit the iMac always fail, so I have to hard crash using the power button. Multiple attempts are required to successfully restart via the login screen. I do not know whether any other apps, such as Safari or screen saver may be involved. I think a crash log would help, however I am not sure whether I should look in: useres/library/logs/DaiagnosticReports or : users/library/logs/CrashReporter, and whether I should attempt to open the latest in either in Console or Text edit and then post here. Also, is this the appropriate site to post a log in the hope that Apple may look at it? I have read through threads on Apple finder, and am stunned to find that after all these OS-X versions finder is still buggy and inferior to MS Explorer and Apple appears to be in denial. Maybe their efforts are in devices such as iPhones and iPads? Ths issue never occured in OS 10.5.8.

    Better is http://www.apple.com/feedback/macosx.html

  • Firmware Upgrade causes severe slowness and Hangs

    Has anyone else encountered this problem? I did do the firmware upgrade, and that caused slowness in responsiveness (followed immediately by that spinning wheel). In some cases, it completely hangs. At this time, I also tried to VNC into it, and it wasn't listening. It looks like GUI and network connectivity got hosed. This happens at least 10 times today.
    Any suggestions?

    spingineer,
    I haven't seen the firmware update (done 2x) alone cause the problems that you're mentioning. In fact, I didn't notice a thing after running it. I DID notice issues when I ran all the updates (machine fresh out of the box and then everything at once). You machine shouldn't be any slower. Make sure you have enough free space on your drive.
    The obvious, and often underused, diagnostic tool is to create a new user account and see if the issues persist there. If not, then look to what's running in your login items and your applications. You may just need to repair permissions, but sometimes it helps to verify or repair the disk.
    As to the network connectivity. I'd say it's basically a given that a lot of minis aren't good citizens.
    What I see is contention. It's like the machine thinks 'oh, someone else is using the connection so I'll back off a bit then try again', even if nothing else is on at all. It could be partially hardware, there are changes in the machines; but it might be something that can be solved w/ modifications to the stack. It's almost like a feedback loop. The more you use the connection the more it thinks it is competing w/ other machines for access and the slower it becomes. Try the usual, zap the pram, repair permissions, etc. There's a good link if you use search to a tutorial that may help you w/ some network connectivity issues on the mini. (moving out system configuration, promoting your primary connection to the top, using the assistant, rebooting and zapping the pram).
    As easy as it seems to look at the firmware as the source of the problems, I haven't seen that as the foundation issue for either of the difficulties you are experiencing with your machine.
    Hopefully a few simple resets and permission repairs etc will remedy the issue.
    Good Luck,
    -j

  • PMTU-D Black Hole Detection Missing?  Cause of some conn hangs.

    In looking through the kernel source, it appears that Apple has left out one of the most important parts of Path MTU Discovery (RFC1191) as suggested in RFC2923. Since Path MTU Discovery is enabled by default, this may cause some of you to have 15 minute hangs and ultimate termination of connections when large packets are sent to specific hosts.
    Other than DNS and Wireless network drops, MTU settings appear to be one of the single most problematic things going on with OS X right now.
    For those who are not familiar with MTU, here's a brief rundown.
    10/100 Ethernet networks support a base MTU of around 1514 bytes. This is the max number of bytes that a packet is able to be in order to get put on an Ethernet network (and be within spec). Gigabit Ethernet allows for larger, but we won't go into that.
    You're probably more used to hearing 1500, however, that is the MTU for IP (or the Ethernet payload) as the Ethernet header itself is 14 bytes.
    In that 1500 bytes, you have to fit your IP header, ICMP/TCP/UDP header, and any higher layer protocols and data, each layering on top of the next.
    |<--Ethernet (14 Bytes)--><--IP (20 Bytes)--><--TCP (20 Bytes)--><--Data (1460 Bytes)-->|
    So that is how things look on a local area network.
    Once the WAN comes into play, the Ethernet header is stripped off leaving only the IP packet and another header put in its place to get it over the next link. This process goes on and on and on until the packet finally reaches its destination.
    But here's the problem - what if there is ANOTHER layer between the Ethernet and IP stack?
    This is actually quite common and you're probably using it now. The protocol PPP over Ethernet (PPPoE) fits between the Ethernet header and the IP header and adds another 8 bytes to this packet size.
    So now we end up with:
    |<--Ethernet (14 Bytes)--><--PPPoE (8 Bytes)--><--IP (20 Bytes)--><--TCP (20 Bytes)--><--Data (1452 Bytes)-->|
    Notice that we now can't put as much data in this packet or we'll end up with a packet that is too big to fit on the Ethernet network.
    The PPPoE header will ultimately get taken off once the packet gets where it needs to go at your ISP, but there may be other 'tunnels' between you and your ultimate destination and continue to strip off space of how much data you can put into a packet.
    So how do you know how much data you can put into a packet when you don't own or know anything about the network between you and the destination?
    That's where Path MTU Discovery comes into play.
    It used to be that IP packets would be fragmented (split up) if a packet was too big to get put on the next network. This process of fragmentation causes overhead for both the router having to split up the packets and the receiving device that has to put them all back together again (and make sure they go in the right order).
    So in order to reduce this overhead and also ensure that you are always sending the largest packets possible from end to end, IP stacks started setting the 'Don't Fragment' bit in the IP header. This instructs routers to throw away the packet if it is too big when it gets there.
    When the packet gets thrown away due to it being too large, the router that throws it away also sends an ICMP packet (an IP diagnostics message) back to the sender telling it what the MTU is of the interface that couldn't take the packet. The sender can then re-calculate things based on that value and resend.
    This works great EXCEPT when there are firewalls in the way (or broken routers, which is less likely these days). Many firewalls will not allow these ICMP messages to go back to the sender. Therefore, your host never receives the message that it is supposed to reduce the size of the packet and keeps trying and trying for about 15 minutes until it finally dies.
    This is one reason why you may be seeing long hangs that ultimately end in termination of your connection.
    RFC2923 goes into some options to work past this issue.
    One way that this can be done, Windows Vista for instance does this, is for the system to keep an eye on how many max sized packets get retransmitted. After a certain number (lets say 5), the system assumes that it is not getting this ICMP notification and cuts the size of that packet in half so it can now get the data through - assuming that smaller packets are better than no packets getting sent.
    It may also (and does with Vista) temporarily disable the setting of the 'Don't Fragment' bit and allow the routers to just take care of things. So in Vista, you'll see the page stutter for a second, and then continue to load, where an OS X system will sit there and hang for 15 minutes.
    This is where OS X goes wrong. This behavior is called PMTU-D Black Hole Detection and does not appear to be in the IP stack for Leopard (and probably not previous releases).
    So what can you do.
    You have a few options, some of which I've already provided to a few folks (although without the mathematics so it's just a rough guess value).
    First, you can just disable PMTU-D. The command to do this is:
    sudo sysctl -w net.inet.tcp.pathmtudiscovery=0
    This is a 'quick fix' but does eliminate the benefits that PMTU-D provides.
    Second, you can calculate out what size MTU seems to work for you by working backwards and configure that on something within your control.
    If your home router supports it, that's a good place to reduce the MTU since it only comes into play when you're using your Internet connection and not when hosts within the same network talk to each other. So if you place the MTU of 1472 on your router and your host sends it a 1500 byte packet, it will send back the ICMP message telling you to reduce it down to 1472.
    If your router doesn't support it, you can reduce the MTU on your macs physical interface. This isn't always the best solution since you really should then reduce the MTU on each of your local systems or you could run into issues locally.
    The command to do this is:
    sudo ifconfig en1 mtu 1472
    To make this permanent for Ethernet, set it in the Network settings. For Airport, search the forums. I provided an update you can make to one of the preferences files manually to do this (don't remember what file right now).
    I have found a couple of sites (Washington Mutual's website for instance) that appear to have configuration issues internal to their network in which a device behind a firewall (possibly the web server, load balancer, or IPSec added) that may have an MTU less than 1500 set on it AND a firewall blocking ICMP packets from coming back. These sites will throw off your math since you can no longer assume a max size of 1500 for IP packets. In this specific case, you have to assume 1480.
    Third, you can adjust the MSS setting (Max Segment Size) in the kernel to a value that is 20 bytes smaller than what you would otherwise set the MTU to. This ensures that the TCP stack doesn't put more than that amount of data in any single packet (therefore, eliminating the MTU issue), however, this will not work for UDP.
    Finally, you can submit a bug report to let Apple know that PMTU-D Black Hole detection is something that we need.
    So what kind of impact does this have on performance?
    This will depend on what solution you choose, what the performance of your home router is, and the load on the various servers that have to potentially re-assemble the packets.
    That said, knocking things all the way down to 1400 bytes, I am able to still get at least 15 Mbps up and down stream over the Internet.
    If you have any questions on this post, please post and i'll do my best to respond. Hopefully this will help one more person resolve their performance issues with Leopard.

    Hi Karsten and thanks for the suggestion!
    I have exempted internal networks and can connect them via the VPN connection. I also got connectivity to the outside world with nat (outside,outside) and 'same-security-traffic permit intra-interface'.
    A question remains though. At the moment, all traffic gets out of the network through the 'outside' interface IP (.22). I'd rather use a dedicated address from the /29 on GigabitEthernet0/0. Is this possible to achieve that? To put it differently, I'd like to NAT the VPN range onto an address that is not the 'outside' interface, like I did in this statement, for instance:
    nat (v200,outside) source dynamic v200_private v200_public
    My other question is, whether the single NAT statement [nat (outside,outside) dynamic interface] is sufficient for VPN traffic and whether the original statement can be removed [nat (vpn,outside) source dynamic vpn_pool vpn_public].
    Thanks once again for the tips!
    R.

Maybe you are looking for