Possible Cause for Ituens to crash on launch.

Just something I found while trying to figure out why my itunes wouldnt start.
If you have the Directx 9 SDK installed make sure its set to the retail version before launching. Just thought I would share the info.

The first step is to trash preferences. I suggest you download Compressor Repair from Digital Rebellion; make sure the Trash Preferences box is checked. It will do more than trash your preferences, like clearing out temporary files and getting Compressor and Qmaster back on the same page.
If running the DR app doesn't fix it, I would suspect a conflict with a third party product,
Good luck.
Russ

Similar Messages

  • A possible cause for freezes and crashes on your G5 PPC

    My G5, PPC, came with Tiger installed and ran great. I decided to upgrade to Leopard (not snow leopard) and at first it seemed to work well. After several days I noticed I have Permission errors that Disk Utility would not fix. (The only way to repair this was to insert the install disk and run Disk Utility from there: which means you have to reimport/install all the OS updates over again) Eventually the OS was crashing and freezing so I went to a local Apple repair store to ask why. Apparently Leopard is unstable on some G5 towers. I decided to reinstall Tiger and still had problems. After about 5 attempts at reinstalling the OS I realized I was using a disk from a G4 tower that my kids use, so I found the disk that come with my G5 and the install worked perfectly. So it appears that not all OS install disks are the same: At least my G5 doesn't think they are.

    My G5, PPC, came with Tiger installed and ran great. I decided to upgrade to Leopard (not snow leopard) and at first it seemed to work well.
    Here is where you should backup, reinitialize, and make sure you use retail 10.4 rather than any OEM DVD?
    After several days I noticed I have Permission errors that Disk Utility would not fix. (The only way to repair this was to insert the install disk and run Disk Utility from there: which means you have to reimport/install all the OS updates over again)
    Some real confusion. Permissions can and should be done while booted from your hard drive; never run from older version of OS X.
    Not all permission messages are errors.
    Bootable backups (clones).
    Invest in 3rd party repair programs.
    Eventually the OS was crashing and freezing so I went to a local Apple repair store to ask why. Apparently Leopard is unstable on some G5 towers.
    No, not really.
    But you do have to insure your hardware, your software, is also current.
    I decided to reinstall Tiger and still had problems. After about 5 attempts at reinstalling the OS I realized I was using a disk from a G4 tower that my kids use, so I found the disk that come with my G5 and the install worked perfectly.
    So it appears that not all OS install disks are the same:
    No secret there. NEVER use an OEM disc except your own; or, use retail full install versions is all. I guess you never came across that bit.
    Sorry you had to take so much time, but sounds like came away with some misconceptions.

  • Mac book pro hanging very often what will be the possible cause for it?

    hi my mac book pro is 3months old and nowadays its hanging very often like when iam surfing, and some times when i dont use it for 10 to 15min.
    can anybody suggest me what will be the possible cause for it.
    Thanks

    Start with this comprehensive troubleshooting article:
    https://discussions.apple.com/docs/DOC-3521
    Look at this one for possible solutions:
    https://discussions.apple.com/docs/DOC-3353
    Ciao.

  • What are possible causes for frequent loss of wireless mouse connectivity other than the batteries ?

    What are possible causes for frequent loss of wireless mouse connectivity other than the batteries ?

    Wi-Fi or another interference source. Try turning off the Wi-Fi and see if the problems continue. If that solves the problem, see if you can set your Wi-Fi to run in the 5 GHz range.
    Keyboard/Mouse – Troubleshooting Wireless
    WIFI AND BLUETOOTH FINALLY SOLVED, NO REALLY - YOSEMITE 10.10
    Bluetooth Wireless Problems
    Bluetooth devices become unresponsive

  • A possible cause for the Lion freezes: Spotlight indexing

    Does your Mac freeze mysteriously after upgrading to Lion?
    Mine had that problem, but after troubleshooting, I seem to have identified the culprit (at least for my MacBook) and, after deleting the offending file, I have since experienced no problem.  Here, I will share a case report with the hope that it will help others troubleshoot their computers experiencing the same problem.
    The Problem: Mac (running Lion 10.7 or 10.7.1) freezes sometime after logging on.  The freeze begins by an inability to get a response to clicks.  The cursor is still active, but after a click or two the cursor turns into a spinning disc.  After some time, the clock stops updating on the menu bar.
    Mine froze consistently after about 15-20 min after logging on.  It happened regardless of which application I was using, it froze even if I didn't do anything after logging on.  It required a reboot (control-command-power button on a MacBook) everytime.
    Was Spotlight indexing active right before the freeze happened?  When Spotlight indexing is active, the magnifying glass icon on the upper right corner of your display will show a blinking dot.  Mine was.
    A Possible Culprit: Spotlight may have encountered a corrupt file on the hard disk during indexing.
    What you can do:
    Before you do anything, it is recommended that you have backed up all your files.  Unfortunately, it is difficult to back up now because the Mac may freeze during the back up process.
    1. Check the errors related to Spotlight by opening Console, which is an utility app that you can find in the Applications>Utilities folder.  Do you see error messages for "mdworkers"?  It does not always show up before the freeze, but this may indicate some problems during Spotlight indexing.
    2. Confirm the problem by turning off Spotlight indexing.  You can do this in a number of ways, but I will list two ways below:
    a) Go to System Preferences and click on Spotlight icon.  Under the Privacy tab, click on "+" icon and add the "Users" folder (or any particular folder that you may suspect).  The indexing will not happen to files in that folder.  Also, turn off Time Machine and disconnect back up disks, if you use any.  Apparently Spotlight indexes within the Time Machine backups.  OR
    b) For experienced users: Open Terminal and type "sudo mdutil -i off" without the quotes.  (To turn it back on, type "sudo mdutil -i on /" without the quotes)
    3. Try using your computer with Spotlight turned off.  Does it still freeze?  If it does not, you have confirmed that the problem is with Spotlight indexing.
    4. Find the offending file that causes problem by turning Spotlight indexing back on...
    a) Remove the folder by highlighting and clicking on "-" button under the Privacy tab.  OR
    b) For experienced users: Type "sudo mdutil -i on /" without the quotes.
    5. ...and then repeating steps 2a, 3, and 4a.  Try isolating different folders until you can narrow down the problem.  This process may take a while.
    6. Once you narrowed down to a few folders, try QuickLook through the contents of the folder while the Console is open.  To use QuickLook, highlight a file in the Finder and hit a space bar on your keyboard.  It is helpful to set the Finder in a column view so you can use arrow keys to navigate through the folders.  Does Console show you an error when you QuickLook a file?  Can you double click and open that file?  If not, the file may be corrupt.  Trash that file and empty trash.
    7. Now turn Spotlight indexing back on (step 4) and use your computer for a while.  Does it still freeze?  If so, repeat the process and find other corrupt files.
    For me, it was a single corrupt image file in the Documents folder that caused the freezing problem.  I deleted it and the problem went away.  Since that file had been untouched for years, and I did not experience the same freezing problem in Snow Leopard, I suspect that Spotlight in Lion is somehow less permissive of corrupt files assuming that the file did not corrupt after the upgrade.
    Steps 4-7 is cumbersome and it takes a long time to troubleshoot.  If you know of a faster way to identify corrupt files, please share in this thread.  Also, I think Spotlight should alert the users when it encounters a corrupt file and give us a choice to delete it on the spot.  Please join me by sending a feedback to Apple about this.

    My G5, PPC, came with Tiger installed and ran great. I decided to upgrade to Leopard (not snow leopard) and at first it seemed to work well.
    Here is where you should backup, reinitialize, and make sure you use retail 10.4 rather than any OEM DVD?
    After several days I noticed I have Permission errors that Disk Utility would not fix. (The only way to repair this was to insert the install disk and run Disk Utility from there: which means you have to reimport/install all the OS updates over again)
    Some real confusion. Permissions can and should be done while booted from your hard drive; never run from older version of OS X.
    Not all permission messages are errors.
    Bootable backups (clones).
    Invest in 3rd party repair programs.
    Eventually the OS was crashing and freezing so I went to a local Apple repair store to ask why. Apparently Leopard is unstable on some G5 towers.
    No, not really.
    But you do have to insure your hardware, your software, is also current.
    I decided to reinstall Tiger and still had problems. After about 5 attempts at reinstalling the OS I realized I was using a disk from a G4 tower that my kids use, so I found the disk that come with my G5 and the install worked perfectly.
    So it appears that not all OS install disks are the same:
    No secret there. NEVER use an OEM disc except your own; or, use retail full install versions is all. I guess you never came across that bit.
    Sorry you had to take so much time, but sounds like came away with some misconceptions.

  • AIR for iOS app crashes on launch - only on iPad1

    Hello,
    Been working on an iPad book app in FlashBuilder 4.6. Early on there were some performance issues with iPad1/3 until learning about GPU rendermode and setting the StageQuality to low. These helped immensely.
    However, recently the app starting crashing on startup - only on iPad1. For example page 1 of the app which had worked weeks ago would now crash. After more research, it seemed that the static references to all the page classes that were put in the ViewController were the issue. They seemed to be overwhelming the memory. When I put only a static reference to page1 in the VC it worked. And then in page 1 were static references to page 2 or 3. Or whatever pages it might link to. Now, after reworking the 70 other pages to only static reference the pages they need, it is crashing again.
    My question is this, if I have page 1 with a static reference to page 2 and 3. And each of those have references...all down the line to say page 70, are all those in essence getting loaded into memory at startup?
    The bigger question is how best to manage the memory of an AIR app that will have ~ 120+ "pages" or views in MVC parlance? Ideally, I only want the dynamically created view in memory but don't think it's working.
    After doing some research was thinking about loading/unloading swfs that have references to needed classes via ApplicationDomain.
    One interesting thing noticed is this. When launching the app in the debugger, it traces out terminated and the app quits. However, when double clicking the iPad home button, it shows the app still running. Not sure why that is?
    Pardon the lengthy description.
    Any and all help would be appreciated.
    Thanks, MTG

    @Fahad,
    It happens when the actual game is being played. I'm using AIR 3.2 SDK in flash pro cs6, I started this project before 3.3 was officially released, tested this on an iPad 1 with iOS 5.1.1.
    I used hi res stats to monitor memory usage and the app consumes less than 8MB of memory.
    Thanks

  • InDesign 5.5 for pc repeatedly crashes on launch.

    Hi,
    This morning I launched InDesign as usual, but moments after the home screen appeared, I got an error message which said 'Adobe InDesign CS5.5 has stopped working.' The application then closed. This has happened repeatedly despite numerous attempts to rectify the problem.
    I have tried:
    -  Deleting the RecoveryData and DBSharing files from the InDesign Recovery Caches
    - Trashing the Preferences
    - Restarting
    - Clearing the SING datastore folder
    - Removing the SING component
    - Using Extensis Doctor to check and identify bad fonts (Bradley Gratis and Univox removed, to no avail).
    I am using Adobe CS 5.5 on a pc using Windows 7 Home Premium Edition. It's using a 64 bit operating system, has plenty of memory and is running generally well. I've had this issue with InDesign over the last few years but usually deleting the recovery data and trashing the prefs fixes it. I've never had it simply lock me out before. Apologies in advance - I am a first-time poster so forgive me if I have failed to include anything important. Here is a screen grab of the message. Thankyou.

    Dear Peter,
    Many thanks for your fast reply and your suggestions.
    I tried my other user account with no luck, and then System Restore. It logged two Windows updates from last week, including one 'critical' one. (I have noticed an increased rate of issues and InDesign problems immediately after the bigger updates, but never to this scale.)
    There was also two Microsoft Visual C++ updates logged.
    In the end, out of sheer frustration coupled with time constraint, I did a complete reinstall of Creative Suite. Fortunately so far, all seems to be running smoothly, although I am curious to know what caused the trouble in the first place!
    Many thanks once again for your help, and best wishes,
    Ali

  • Slow network connection possibly causing a slave to crash.

    We are using Berkeley DB XML 2.4.16 (Patch level 1) in combination with Berkeley DB 4.7.25 (Patch level 3). These are Java processes.
    We have a 4 node replication group with a master and a slave in the US, a slave in the UK and a slave in HK. We are using the built in replication manager. The acknowledgement policy is set to none. The HK slave OS is Red Hat Enterprise Linux ES release 3 (Taroon Update 8).
    The slave in HK is on a fairly slow network connection to the master in the US.
    The amount of traffic generated by the master can become fairly busy at times and this seemingly causes the HK slave to become fairly unstable. It would routinely crash (SIGSEGV) with the following back trace caught with gdb and a debug build of Berkeley DB XML/Berkeley DB. The location of the crash is very consistent. The UK slave also suffers this problem, but to a lesser degree (I suspect the faster network link to the UK to be a factor here).
    #5 <signal handler called>
    #6 0xb74fb2f8 in intfree () from /lib/tls/libc.so.6
    #7 0xb74fa278 in free () from /lib/tls/libc.so.6
    #8 0x6b7eee53 in __os_free (env=0x0, ptr=0x6ba335c0) at ../os/os_alloc.c:405
    #9 0x6b751375 in message_loop (env=0x6ba1acc0) at ../repmgr/repmgr_msg.c:49
    #10 0x6b7512a4 in __repmgr_msg_thread (args=0x6ba1acc0) at ../repmgr/repmgr_msg.c:29
    #11 0xb75c9dd8 in start_thread () from /lib/tls/libpthread.so.0
    #12 0xb7565d1a in clone () from /lib/tls/libc.so.6
    We had been adjusting the rep_set_limit environment parameter to see if it would help. First to 5MB, then to 1MB with little or no improvement.
    In an attempt to gather more information I had activated verbose replication logging on the HK slave which has had the side effect of fixing the problem.
    Does this sound like something that could be addressed with the rep_set_request parameter?
    I am no master on tuning these replication settings so some guidance would be appreciated.
    Thanks,
    Neil

    OK,
    I was able to reproduce the crash once again with verbose replication logging at the master, I know the verbose logging at the slave would be better but as we discussed that in fact fixes the problem, probably due the additional logging is throttling the replication mechanics a little.
    Here is the back-trace…
    #5 <signal handler called>
    #6 0xb74fb2f8 in intfree () from /lib/tls/libc.so.6
    #7 0xb74fa278 in free () from /lib/tls/libc.so.6
    #8 0x6b7d3e53 in __os_free (env=0x0, ptr=0x6b9de2b0) at ../os/os_alloc.c:405
    #9 0x6b736375 in message_loop (env=0x6b941da0) at ../repmgr/repmgr_msg.c:49
    #10 0x6b7362a4 in __repmgr_msg_thread (args=0x6b941da0) at ../repmgr/repmgr_msg.c:29
    #11 0xb75c9dd8 in start_thread () from /lib/tls/libpthread.so.0
    #12 0xb7565d1a in clone () from /lib/tls/libc.so.6
    Here is control info…
    print msg->control
    $1 = {data = 0x6b9de2f0, size = 36, ulen = 0, dlen = 0, doff = 0, app_data = 0x0, flags = 0}
    x/36xb msg->control.data
    0x6b9de2f0: 0x00 0x00 0x00 0x05 0x00 0x00 0x00 0x0e
    0x6b9de2f8: 0x00 0x00 0x00 0xf6 0x00 0x37 0x1a 0xd7
    0x6b9de300: 0x00 0x00 0x00 0x0b 0x00 0x00 0x00 0x01
    0x6b9de308: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
    0x6b9de310: 0x00 0x00 0x00 0x64
    The HK site was a bit behind when I started the tests, I didn't have the slave instance up over the weekend, I don't now if this really effects the results as I believe the HK has a hard time keeping up when there is a large volume of replication traffic in the normal case, hence the resulting crash is the same…
    Before the crash, the slave was synchronizing with the master and it was sending out what I would guess normal "nobuf" messages. This is quickly followed by a large amount of "nobuf resend" messages. This continues for a bit intermixed with " MASTER: wrote only 53 bytes to site XXX.XX.XX.XX:58010" (The number of bytes are random). In the end it starts logging the following several times along with the "nobuf resend" messages..
    MASTER: msg to site XXX.XX.XX.XX:58010 to be queued
    MASTER: block msg thread, await queue space
    MASTER: will await drain
    MASTER: drain returned 0 (0,0)
    If you would like to take a look at the actual log, I will need a way to filter any sensitive information (which could prove to be difficult) or attempt to reproduce it with another pair rigged to be something generic and hope it exhibits the same behavior.

  • Possible cause for Faces failures (migration from an older version)

    I've had no luck with Faces recognizing faces in images.
    I think that the issue is with how the images got to iPhoto.
    I imported 2000+ images from my iBook (iPhoto 04). Of those, Faces failed in ~>95% of the images. Today, I took two junky photos with Photobooth, including a dark and distant shot. Faces recognized that there was a face in the image, although it hadn't learned the face, yet (I know, that takes time).
    I believe the issue might have to do with the fact that I imported images from a distant version (i.e. coming from iPhoto 4 instead of iPhoto 07 or 08, or whatever).
    Or, possibly that I migrated from another machine as opposed to upgrading iPhoto on the same machine?
    Hopefully this line of reasoning will isolate the problem's cause.
    Please reply if you are having success or not, as well how your photos got into iPhoto '09 (i.e. Migration from another computer and type, prior iPhoto version, etc.)
    I'll start...
    I migrated my images from iPhoto 4 from an iBook (PPC) and have had very little, if any, success with Faces recognizing faces in images.
    Thanks!

    I just imported (from my Treo) three images that were exactly the same as the three successes from Photobooth.
    Being from different sources they cannot be the same. Maybe the face in the photo was the same but the rest of the file, i.e. the metadata is different. Some image sources write metadata differently and that can cause issue. It's probable that iPhoto is expecting the metadata to adhere strictly to the EXIF/ITPC standards and some of the sources don't in writing the metadata to the file.
    Report the problem to iPhoto via http://www.apple.com/feedback/iphoto.html and give the details of the photos as you've done here. That will help them better understand the issue and get a fix out.

  • Possible cause for unhandled Win32 exception?

    Hi,
    Using SDK 7.0.5, I'm calling AVDocOpenFromASFileWithParams on an AVDocOpenParamsRec that specifies a sourceDoc.  Suppose the sourceDoc has only recently been opened and may still be in the process of loading.  Is it possible that this could result in an unhandled Win32 exception in acrobat.exe?  I'm running version 8.1.5.
    Thanks,
    Daniel Sheiner

    Our code is completely inside DURING/HANDLER blocks.  I've spent the morning sweeping through for any fragments of code that weren't.  I did find a few, but after adding DURING/HANDLER blocks around them, the problem persists.

  • Adobe flash media live encoder 3.2 for the mac crashes on launch every time

    I have a mack book air and the program crashes every time when trying to launch. I also tried version 3.1 with the same issue. Any help?

    Since its FMLE issue please post on this forum: http://forums.adobe.com/community/flash/flash_media_live_encoder?view=discussions

  • Possible solution for Empty Trash crashing

    iPhoto continues to crash on me when emptying trash. I would think Apple could have fixed this by now, but I found something that works MOST of the time. After sending pics to trash, I open trash, move the scaling slider to smallest possible image, and then empty trash. Doesn't always work on the first try, but results are better than constantly restarting and emptying trash from normal views.

    Replying to my own post? OK, I fixed my connectivity problem and did not need to uninstall iTunes. Originally I'd installed via System Update and had the aforementioned problem. So...I then downloaded iTunes directly from Apple and ran the installer...over top of my existing 8.2.1. When I did this I noticed that "custom" install includes two components. There's iTunes and there is mobile device somethingorother. By default they were both checked but I don't remember if that was the case with the install via System Update. It may have been but I hadn't chosen "custom." So...voila...now my iTouch connects and I didn't even have to restart the computer, let alone uninstall iTunes. Your mileage may vary but I'd suggest this reinstall as an easy first step if your Mac won't recognize your iTouch after installing iTunes from System Update.

  • Possible causes for memory leak in Java and Tomcat

    I would like to enquire what are the typical mistakes done by programmers that will cause memory leak in Java and Tomcat.

    Please refer the below site. It will give more points about the memory leak and how to rectify it.
    http://www.experts-exchange.com/Software/Server_Software/Application_Servers/Q_20981562.html?cid=336

  • Possible causes for extremely slow (10 min.) startup?

    I just powered on this morning, after having been powered down and unplugged all night (8 hrs), and I got the gray apple screen for ten minutes before OSX loaded.  Not sure what was taking it so long to cycle through, but I'm wondering if this is normal operation after having been powered down?  If it's not normal operation, can you help me identify an issue that might need addressing?
    Prior to powering down last night, the computer had been on or sleeping continuously for the past two or three days.

    Thanks. I haven't tried rebooting yet to check the startup speed, but I did what you said and there were quite a few disk permissions that needed to be repaired (pasted below). Any idea how/why these disk permissions were altered? 
    Verifying permissions for “Macintosh HD”
    Group differs on “Library/Java”; should be 0; group is 80.
    Permissions differ on “Library/Java”; should be drwxr-xr-x ; they are drwxrwxr-x .
    User differs on “usr/share/collabd/webauthd”; should be 94; user is 221.
    Group differs on “usr/share/collabd/webauthd”; should be 94; group is 221.
    User differs on “usr/share/collabd/webauthd/locales”; should be 94; user is 221.
    Group differs on “usr/share/collabd/webauthd/locales”; should be 94; group is 221.
    Permissions differ on “usr/share/devicemgr/frontend/admin/zh_TW.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
    Permissions differ on “usr/share/devicemgr/frontend/admin/zh_CN.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
    Permissions differ on “usr/share/devicemgr/frontend/admin/ko.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
    Permissions differ on “usr/share/devicemgr/frontend/admin/nl.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
    Permissions differ on “usr/share/devicemgr/frontend/admin/it.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
    Permissions differ on “usr/share/devicemgr/frontend/admin/es.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
    Permissions differ on “usr/share/devicemgr/frontend/admin/fr.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
    Permissions differ on “usr/share/devicemgr/frontend/admin/de.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
    Permissions differ on “usr/share/devicemgr/frontend/admin/ja.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
    User differs on “Applications/.DS_Store”; should be 0; user is 501.
    Group differs on “Applications/.DS_Store”; should be 80; group is 20.
    Permissions differ on “Applications/.DS_Store”; should be -rw-rw-r-- ; they are -rwx------ .
    Group differs on “Library/Preferences/com.apple.alf.plist”; should be 80; group is 0.
    Permissions verification complete

  • Possible Causes for Windows 7 64bit unable to connect to meetings?

    I have one user on a Windows 7 64bit laptop who cannot connect to meetings.  He gets the login screen, enters name as Guest, and hits Enter Room.  Connects to troubleshooting screen and small "Adobe Connect" window pops up but that is all the further it will go.  No meedting room comes up, and meeting host does not get a request to allow user into meeting room.  This happens in IE9, Firefox, and Chrome browsers.  Wondering if there could be some kind of security setting that might be blocking him?  Or any other suggestions.

    Hi there,
    I have similar problem as Larry3323, and here's my system:
    -. Windows 7 64-bit,
    -. Adobe Connect Version: 8.2.20
    -. Flash Player Version: WIN 11.5.502.110
    -. Browser: Google Chrome and Firefox
    My login problem can be easily solved by following your suggestion, that is by putting "/?launcher=false" after the meeting URL. However, when I had logged in and tried to/clicked Share My Screen, new window labelled Adobe Connect (I believe it is the Adobe Connect Add-in's window) pops up but nothing shows in there -- just a blank white page.
    On the previous window, however, it shows this page (please see the pic that I attached below). Please let me know whether this is a common issue of Adobe Connect with Windows 7 64-bit, or whether this is something else. Also, please let me know if there is a way to fix this
    Thanks,

Maybe you are looking for