Classic Chrome in Lightroom 5.7.1
I have the lightroom stand alone version 5.7.1 installed, but i still cannot see the classic chrome simulation for fuji raf files from the x-t1 with firmware 3.00. any hints?
If its not there it means that Adobe has not created any additional profiles for your camera model, you should at least be seeing Adobe Standard. That would be the standard profile specific to your camera model.
Adobe began adding "Camera Matching color profiles in LR 5.4, ACR 8.4 see a quote from the release notes. You should at least see the ones mentioned, I do not know if "Classic Chrome" was included.
"Added Camera Matching color profiles (PROVIA/STANDARD, Velvia/VIVID, ASTIA/SOFT, MONOCHROME, etc.) for the following Fujifilm cameras:
Fujifilm X-A1
Fujifilm X-E1
Fujifilm X-E2
Fujifilm X-M1
Fujifilm X-S1
Fujifilm X-T1
Fujifilm X-Pro1
Fujifilm X10
Fujifilm X20
Fujifilm XF1
Fujifilm XQ1
Fujifilm X100
Fujifilm X100S
Similar Messages
-
Convert Fujifilm Classic Chrome camera calibration for X-T1 to X-E2?
I have an X-E2 that has the Classic Chrome calibration profile with the new Fuji 3.0.0 firmware.
However, Lightroom 5.7 doesn't recognize that change, even though it does activate for the X-T1.
Is there a way to extract or convert the X-T1's profile and adapt or rename it to work with the X-E2 when working with RAW RAF files, rather than with the in-camera JPGs?
Alternately, is Adobe planning on enabling the Classic Chrome profile for the X-E2 since it has that profile in the new firmware?
Thanks.The latest version of LR which is 5.7.1 was released Dec 15th with functionality finalized sometime before then. The X-E2 firmware that includes Classic Chrome was released Dec 18th. These camera-match profiles that simulate Fuji shooting modes, while not supplied as external .dcp files like other Adobe camera-match profiles, are still created by Adobe and coded into the software, and there's no way LR could duplicate something that Fuji released several days later.
The good news, or at least hope for LR users, is that Adobe's Camera Raw 8.8 plug-in for Photoshop does include the Classic Chrome profile as a selection for the X-E2, so Adobe has figured out how to do it:
The bad news is that there hasn't been a LR 5.8 to match the ACR 8.8 plug-in.
I believe this is because Adobe never intended to have even an ACR 8.8 but released it so people with the new E-M5 Mark II could work with their camera's raw files. Getting a plug-in release ready is much easier than an entire LR program so I doubt Adobe will release a LR 5.8 and will go straight to LR 6, unless LR 6 is delayed for several more months. From what I'd guess, there isn't a LR 5.x team that is independent of the LR 6 team, so if Adobe stopped work on LR 6 to push out a LR 5.8, that would delay LR 6 even further into the future, and there may be some hard date, like an international photography conference, somewhere, that Adobe wants to announce LR 6 at so they can't afford to delay it longer than it already has been.
Photoshop is paid for on a monthly basis, now, so announcements about what's new aren't as important as LR, which is still available as a standalone upgrade, so adding new features will generate more revenue for Adobe and the time to announce those new features will generate more buzz at some times of year than others. -
Lightroom and Fuji preset issue
I've updated the firmware on my Fuji X-E2 and have the option of using the Classic Chrome preset. However when I import the files into Lightroom I'm not given the option of using Classic Chrome with the RAW file.
I am running Lightroom 5.7.1 on a Mac and under the Camera Calibration panel in the Develop Module I can access:
Camera Provia
Camera Velvia
Camera Astia
Camera Pro Neg Hi
Camera Pro neg Std
Camera Monochrome (Y, R and G)
I have version 8.7.1 of Adobe Camera Raw installed.
Can anyone please tell me why I can't see the Classic Chrome option (I believe it was introduced in Lightroom 5.7) and how to sort it?
Many thanks.Classic Chrome wasn't available for your camera in LR 5.7 and ACR 8.7, either, right, so it's not the case that it disappeared with the x.7.1 update, it's just that Adobe hasn't added it yet for the X-E2, yet.
See the following discussion:
Lightoom with X-E2 and Classic Chrome - Fuji X Series Camera Forum - Fujifilm X-Pro1 X-T1 X-E2 X-M1 X-A1 X100T X30 -
Lightroom 4.3 installed and working. Tried to download and install 4.4. Keep getting message that a problemoccurred while extracting some files. Check for available space and wride priveleges. The setup64 fails to unzip. I have tried this a few times and once got it to unload but then instalation stopped "error in setup". I have tried with virus off, rebooting and closing chrome and lightroom.
The machine is a 64 bit with Windows 7. Have in past updated 4.2 to 4.3
Any other suggestions?I have tried the same -- i have lightroom 4.3 in Win 7 64 bit working just fine.
When i tried to install Lightroom_4_LS11_win_4_4.exe -- as administrator -- it gives same error message as original poster. There is no such thing as direct update option in lightroom 4.3, it looks like one need to download this executable -- it will expand Install Lightroom 4.exe and other files -- and that will install the program, but Lightroom_4_LS11_win_4_4.exe fails to create installation files.
did anyone come across the same problem and resolved? -
LR 5.7 - different capabilities depending on license type?
I'm using LR on a standalone (not CC) license. After running the update to LR v 5.7, I'd like to get access to the Fujifilm Classic Chrome film simulation for the Fuji X-T1 camera model. I already asked this question in the US Fuji X camera user forum, and there are mixed reports: Some users claim they have access to this film simulation when opening a RAW file that originates from the initial (black) Fuji X-T1 camera - I have the same camera, but my LR installation doesn't grant me this access.
Are there two different LR v. 5.7 versions out there with different functionalities, or did I make a mistake (I tried to call up the film simulation simulation via Camera Calibration/Profile) when calling up the profile?I see the profiles, including Classic Chrome, in LR 5.7 with a RAF from an X-T1 I downloaded from the internet.
I am on the CC Photographer's Plan, so this doesn't verify if the serial-number version has them, and I don't feel like uninstalling this and installing the serial-number version to check. I can say that these are internal to LR and ACR only, because unlike other extra Camera-xxxx profiles, these do not have corresponding .dcp files on disk, so it could be that they are in the CC version, only. One bit of evidence that they should be in the non-CC version is that they ARE there in the CS6-ACR 8.7 plug-in, which isn't CC:
Here is the entry for the LR Blog back when these profiles were first introduced that doesn't say anything about them being CC-only:
Lightroom 5.4 now available
One situation where the profiles wouldn't exist is if you are viewing a non-raw (a JPG instead of a RAF) photo, because these profiles are only available for raw files.
If none of this makes sense, can we see a screenshot of your camera profile list in LR 5.7? -
Click TOC topic. Topic page loads in TOC frame.
I've been testing a simple help application. When I select a topic from the table of contents (TOC), the corresponding topic loads in the TOC section. My observations follow:
Created using Rh 10
Problem occurs on client running XP Professional SP3, Chrome (latest version - 23.0.1271.97)
Problem does not occur on same client when using IE8.
I haven't been able to duplicate the problem elsewhere (i.e., on other systems)
Any ideas?
Thank you,
-bruce.Sounds like you're running into the classic Chrome "Security Fix" issue - see grainge.org (google "chrome") to see workarounds
-
Click-2-run configuration failed
I was downloading an Adobe Flash Player update and it downloaded a bunch of other junk (something like Optimizer Pro Plus). Now my Microsoft Office programs won't open. I get a "click-2-run configuration failed" message.
Maurine1 wrote:
I was downloading an Adobe Flash Player update and it downloaded a bunch of other junk (something like Optimizer Pro Plus). Now my Microsoft Office programs won't open. I get a "click-2-run configuration failed" message.
Whatever you downloaded wasn't Flash Player, and it DIDN'T come from Adobe.
The ONLY things that are EVER bundled with any freeware downloads from Adobe are:
McAfee Security Scan
Norton Security Scan
Google Chrome & Toolbar
Lightroom 5 (Mac only)
You were tricked into downloading an illegal fake with malware. You need to uninstall whatever it was that you downloaded and run a thorough system scan to remove the other junk it put on. -
RAW nikon files have huge Chroma Noise in Lightroom
How come when you process Nikon D3 NEF files in Lightroom it brings out Chroma noise and almost covers up all the luminance noise when importing the file without applying any preset?
When I open the same file in Adobe photoshop CS3 or in Capture NX2, the file contains almost no Chroma noise, but is dominated with luminance noise. I prefer luminance noise over chroma noise since it is forgivable on prints.
Luminance noise is that grainy tiny colorless black dots, and Chroma noise is that large rainbow color big dots. They are especially visible in grayish or dark areas.
Anyone know why this is happening to me in Lightroom 2?
Thanks"Lee Jay - 10:42am Aug 15, 08 PST (#21 of 26)
but when I try that image in noiseninja I get a result close to the capture result - far better than Lightroom.
Does NoiseNinja process raw images?"
Apparently Lee it does. I have pasted below a reply from Bibble to a similar discussion in another forum. So technically it is possible, but LR and Aperture choose not to implement raw plugins at this time.
"There are many things that are better done in the full raw image processing pipeline that can't be done as well after the conversion....Noise being just one example. It has nothing to do with being a tiff or not, thats just another inconvenience.
All the plugins that I just pointed you too work within the confines of the raw pipeline. They don't require additional steps, the don't need intermediate files, they are non destructive, and generally they will give better results then plugins or external editors run after the conversion.
For the moment, AFAIK, Bibble is the only program that allows such plugins, and they offer great quality , flexibility and workflow.
Eric" -
Connect your classic printers with Google Cloud Print like in chrome
be able to do this or similar in firefox
If your printer is Cloud Ready, follow your manufacturer's provided instructions or see setting up your Cloud Ready printer.
To connect your classic printer, enable the Google Cloud Print connector on any (non-Chrome OS) computer that is already connected to your printer and able to print. You'll need Google Chrome to be installed on the computer. If you're using Windows XP, make sure you also have the Windows XP Service Pack 3 (SP3) installed.
Once Google Chrome is installed, follow the steps below to enable the Google Cloud Print connector in Google Chrome.
Log in to your user account on the Windows, Mac, or Linux computer.
Open Google Chrome.
Click the Chrome menu Chrome menu on the browser toolbar.
Select Settings.
Click the Show advanced settings link.
Scroll down to the “Google Cloud Print” section. Click Manage.
The next screen will show a list of devices already registered with Google Cloud Print, and new devices available on the network.
In the "Classic printers" section, click Add printers.
You'll see a confirmation that Google Cloud Print has been enabled. Click Manage your printers to learn more.
The printer is now associated with your Google Account and connected to Google Cloud Print. You can print to this printer using Google Cloud Print whenever you’re signed in with the same Google Account.On your Windows PC?
Does Google Cloud Print create a Windows printer device? If so, it should appear in the drop-down of available printers in the Print dialog. If not, you may need an add-on for this.
On your Android device?
The older add-on I saw (for Firefox/Android) may not work any more: recent reviews are very negative: https://addons.mozilla.org/mobile/addon/cloud-printer/ -
Fuji X-Trans Sensor - Fuji X-E1 Chroma Smearing and Crop Problems with Lightroom 4.4RC
Like others, I found that Lightroom 4.3 caused chroma smearing on my Fuji X-E1 files. I compared 90 shots I did today processed with Fuji SilkyPix RAW converted and LR 4.4RC. It appeared to me that the chroma smearing problem is solved. I did not see the chroma smearing, even at 3:1 zoom. The .tiff files from SilkyPix and the .dng files from LR, appeared practically identical which was not the case with LR 4.3.
There was some discussion of purple fringing with the X-E1 and the Fuji 18-55 on this forum. I did not see this in my backlit shots today. I believe that the problem can be greatly reduced or eliminated by avoiding over exposure in the camera. I have found when faced with very bright skies and darker foregrounds that I get better results by metering the sky, and then over exposing only 1 to 1-1/2 stops. If I cannot do this, I get good results by properly exposing the subject. If both the sky and the subject are over exposed, the fringing appears around the subject.
I was also happy to see that my files are no longer coming into Lightroom cropped.
It looks like I will be able to use Lightroom for my Fuji files with the 4.4RC.The results of my experiments are different than what is being said, here, and different than I expected.
My DNG Conversion options are as listed, above, and did not include setting Custom with Linear as a conversion option, but merely setting ACR 6.6+ as the compatibility. If there is some way to set Linear along with ACR 6.6 compatibility I’d like to know how.
My guess would be that either Adobe is making a linear DNG in this specialized case of X-Trans, to make things compatible with older ACRs that have no idea how to decode X-Trans--which is the promise of converting to DNG, OR Adobe is modifying the X-Trans data to have it be more like normal Bayer layout of still one-color-per-pixel so not demosaicking, exactly, just re-mosaicking.
Anyone can repeat my experiments:
Here is the DNG Converter 7.3 for Windows: http://www.adobe.com/support/downloads/detail.jsp?ftpID=5519
Here is the DNG Converter 7.4RC for Windows: http://labs.adobe.com/downloads/cameraraw7-4.html
Here is an X-Pro1 ISO 200 RAF file: http://movies.dpreview.com.s3.amazonaws.com/fujifilm_xpro1/DSCF2008.RAF.zip -
Lightroom Mobile Full Screen using Chrome or Safari
Is is possible to view photos in full screen mode using Chrome or Safari on an iPad and/or iPhone 6+? If so, how?
I think the short answer right now is "no", but there may be other browsers like Firefox or Opera that can on iOS.
Mobile Safari doesn't support fullscreen yet. One trick that works on my phone is rotating from portrait to landscape mode. I don't think this will work as well on iPad but the rotate trick might improve things. I was hoping that Chrome would work since there is a fullscreen option on Android, but it looks like they don't have the same support on iOS yet. If the browser does support fullscreen, tapping on an image in the slideshow mode should show a fullscreen button next to play/pause -- that's what I see in Android.
Thanks for bringing this up though -- I think there might some room for improvement here so we'll update this thread if the situation improves. -
Ditto the above
Here are the two images (one is of the shirt, one is of the fabric). I can get higher resolution images if needed. What do you think?
http://www.yourfilelink.com/get.php?fid=768239
http://www.yourfilelink.com/get.php?fid=768241
I don't mind it taking a long time, as long as the results are repeatable as I want to be able to do this with 20 fabrics or so and I want it to look as real as possible. I am a novice at Photoshop, would you recommend I pay someone to accomplish this? How long do you think it would take? Is it something I could learn because I plan on doing 20 of them and maybe more? -
Troubleshoot installation problems in Photoshop Lightroom on Windows Vista
This document can help you to resolve system errors that occur while you use Adobe Photoshop Lightroom on Windows Vista. System errors can manifest in many different ways, including (but not limited to) the following:
A blank or flickering dialog box
A frozen cursor or screen
A blue screen
An unexpected restart
An error message such as:
"Setup is unable to load the installation script file."
"Unable to create a directory under C:\Windows\System. Please check write-access to the directory."
"Uninstalling: C:\Program Files\Adobe\Adobe Photoshop Lightroom refers to a location that is unavailable. It could be on a hard drive on this computer, or on a network. Check to make sure that the disk is properly inserted, or that you are connected to the Internet or your network, and then try again. If it still cannot be located, the information might have been moved to a different location."
Note: If you attempt to install Photoshop Lightroom to a drive that doesn't have the minimum required space available, the installation will fail. You must then completely reinstall to another location that has sufficient free space.
Many different factors can cause system errors, including conflicts among device drivers, applications, operating system settings, hardware, and corrupt elements in specific files. Although a system error may occur only when you work with Photoshop Lightroom, Photoshop Lightroom may not necessarily be the cause; it may be the only application that uses enough memory or processor cycles to expose the problem.
To benefit most from this document, perform the tasks in order. Keep track of the tasks that you perform and the results of each, including errors and other problems. Adobe Technical Support can use this information to better assist you if you need to call.
You must be logged on as an administrator to perform some of the procedures in this document.
Important: Some of the procedures in this document may initiate a User Access Control dialog that asks for your permission to continue. Read the details in the dialog to determine if you want to continue. If you choose to cancel the dialog, then you will not be able to continue with that troubleshooting step.
The steps in this document that refer to the Control Panel are in reference to the Classic view. For information on switching the Control Panel to the Classic view and many other common OS procedures, see Common Microsoft Windows Vista procedures (TechNote kb401275)
Some of these procedures require you to locate hidden files and hidden folders. Some procedures require you to locate files by their full file names, which include extensions (for example, example_filename.ini). By default, Windows Explorer doesn't show hidden files, hidden folders, and file name extensions that it recognizes.
To show hidden files, hidden folders, and all file name extensions in Windows Explorer:
In Windows Explorer, choose Organize > Folder And Search Options.
Click the View tab in the Folder Options dialog box.
In Advanced Settings, select Show Hidden Files And Folders.
Deselect Hide Extensions For Known File Types.
Click OK.
Note: The procedures in this document are based on the default interface of Windows Vista. If the interface is customized, some procedures may vary. For example, a commonly encountered difference is the navigation to Control Panel from the Start menu: You may navigate Start > Settings > Control Panel instead of Start > Control Panel. Additionally, the procedures in this document assume you are using the Classic View of the Control Panel: To view the Control Panel in the Classic View, click Switch To Classic View on the Control Panel navigation bar on the left side of the window.
Beginning troubleshooting
The tasks in this section can help you resolve the most common system errors. Before performing any of these tasks, back up all personal files (for example, Photoshop Lightroom files you created). Always restart the computer after a system error occurs to refresh system memory. Continuing to work without restarting the computer may compound the problem.
1.Make sure that the system meets the minimum requirements for PhotoshopLightroom.
Photoshop Lightroom may not run correctly on a system that doesn't meet the following requirements:
Intel Pentium 4 or equivalent processor
Microsoft Windows XP, Windows Vista, Windows 7
768 MB of RAM (1 GB recommended)
1 GB of available hard-disk space
CD-ROM drive
In addition to these requirements, a video card that supports 24-bit (16 million) or more colors, and a resolution of 1024 x 768 or higher, is recommended.
* Photoshop Lightroom 1.0 will install and run on Windows Vista but Adobe cannot guarantee the quality of the software experience until Adobe fully certifies Photoshop Lightroom for use on Windows Vista.
To check basic system information, such as processor speed and how much RAM is installed, choose Start > Control Panel > System.
2. Delete previously installed application files, especially if you had the public beta version of Photoshop Lightroom installed.
To delete files from a previous Adobe Photoshop Lightroom installation attempt:
Choose Start > Control Panels > Add or Remove Programs.
Select Adobe Photoshop Lightroom and choose to remove it.
Close the Add Or Remove Programs window and the Control Panel.
Open Windows Explorer.
If the Lightroom.exe file is still in the Program Files\Adobe\Adobe Photoshop Lightroom folder, delete it.
If the Lightroom Preferences.agprefs file is still in the Documents and Settings/[username]/Application Data/Adobe/Lightroom/Preferences folder, delete it.
Empty the Recycle Bin.
Try to reinstall. If you cannot, continue with the next two sections in this step:
Move all the folders under the Users/[username]/AppData/Roaming/Adobe/Lightroom folder into a new folder on the desktop; name the folder Lightroom Presets. These are the presets that were installed with the application and that you created.
Move all the folders under the Users/[username]/Pictures/Lightroom/Lightroom Previews.lrdata folder into a new folder on the desktop; name the folder Lightroom Previews. If you have a large number of images, you can move this folder back to its original location before you open Photoshop Lightroom, once it's installed. Or you can delete this folders to re-create it when Photoshop Lightroom opens. If there are further problems with Photoshop Lightroom after it's installed, it might be due to corruption in the previews, in which case you need to delete this folder and re-create it.
Try to reinstall.Important: Do not delete the Lightroom Database.lrdb file!
If there are further problems with Photoshop Lightroom after it's installed, these issues may be due to corruption in the preset files you created, in which case you need to remove them and re-create them, or test each preset individually.
Note: If you can reinstall, and if this is not the first time you opened Photoshop Lightroom, then Photoshop Lightroom will look for a library database file. If it does not find a library in the expected location, it will prompt you to create a new library, locate the library, or exit. Exit will close the dialog box, and Photoshop Lightroom will not open. Although you can tell Photoshop Lightroom to locate your library, it's best to put it back in the default location and then open the application.
If you can reinstall, close Photoshop Lightroom and then copy any presets you created from the Lightroom presets on the desktop back into the Users/[username]/AppData/Roaming/Adobe/Lightroom folder.
If you cannot reinstall, then move the Lightroom Database.lrdb file from the Users/[username]/Pictures/Lightroom folder into a new folder called Lightroom Database File and save this file on the desktop. This is your database, if you previously had Photoshop Lightroom installed.
Reinstall Photoshop Lightroom. If you cannot reinstall, continue with the next task in this document.
3. Log in as Administrator before installingPhotoshopLightroom.
In Windows Vista, you must be logged in with local (that is, machine) Administrator rights to install Photoshop Lightroom. If you don't have administrator rights, contact your system administrator for assistance.
4. Check the CD and CD-ROM drive.
Dust or dirt on a CD can interfere with an installation and prevent the CD-ROM drive from recognizing the CD. Examine the Photoshop Lightroom CD for dirt, dust, or fingerprints. Gently wipe the bottom of the CD from the center outward with a soft, lint-free cloth.
Verify that the CD-ROM drive can read other CDs. If it can't, examine the CD caddy or loading tray for dirt, and clean it with a lint-free cloth. If it still can't read other CDs, contact the CD-ROM drive manufacturer or the computer manufacturer.
5. Install current Windows service packs and other updates.
Updates to the Windows operating system improve its performance and compatibility with applications. You can obtain Windows service packs and other updates from the Microsoft website at www.windowsupdate.com. For assistance installing service packs and other updates, contact Microsoft technical support.
Important: Before you install a system update, check the system requirements for Photoshop Lightroom (and any third-party software or hardware you may use with Photoshop Lightroom ) to ensure compatibility. If the update isn't listed, then contact Adobe or the manufacturer of your third-party software or hardware.
6. InstallPhotoshopLightroomfrom the desktop and use the default installation folder.
Some system components such as device drivers and virus protection utilities can conflict with the Photoshop Lightroom installer and result in an incomplete or failed installation, or they can cause problems when you install to a folder or when you use a path to the default installation folder that contains a special character, such as #. To prevent these conflicts, install Photoshop Lightroom from the desktop, and use the default folder name and path.
If Photoshop Lightroom autoplay displays, click Cancel when you are requested to Select the Language.
Copy the Adobe Photoshop Lightroom folder from the Photoshop Lightroom CD-ROM to the desktop.
Open the Adobe Photoshop Lightroom folder on the desktop.
Double-click the Adobe Photoshop Lightroom.msi file, and follow the on-screen instructions.
7.Re-create thePhotoshopLightroompreferences file.
Re-create the Photoshop Lightroom preferences file to eliminate problems that a damaged preferences file might cause:
Quit Photoshop Lightroom.
Rename the Lightroom Preferences.agprefs file (for example, to Lightroom Preferences.old) in the Users/[username]/AppData/Roaming/Adobe/Lightroom/Preferences folder.
Start Photoshop Lightroom. Photoshop Lightroom creates a new preferences file.
If the problem continues, the preferences file isn't the cause. To restore custom settings, delete the new preferences file and restore the original name of the previous preferences file.
8.Install and run Photoshop Lightroom while no other applications are running.
Some applications may interfere with installing or running Photoshop Lightroom. Virus protection programs are meant to stop viruses from installing on your computer. Before installing or starting Photoshop Lightroom, disable other applications, including virus protection programs and startup items (items that start automatically with Windows).
To disable startup items and non Microsoft services:
Quit all applications.
Choose Start, type msconfig in the Search text box, and press Enter.
Write down all unselected items under the Startup and Services tabs.
Click the General tab, and choose Selective Startup.
Click the Startup tab and select Disable All.
Click the Services tab and select Hide All Microsoft Services.
Select Disable All then re-select FLEXnet Licensing Service. If you are unsure whether an item is essential, then leave it deselected (disabled).
Click Apply, and restart Windows for the changes to take effect.
Note: Upon restart, you'll be notified that the System Configuration utility has made changes to the way that Windows starts up. Click OK. When the System Configuration utility appears, click Cancel.
Right-click icons in the Notification Area and close or disable any startup items that are still active.
9. Install Photoshop Lightroom to a different hard disk after disabling startup items and installing from the hard disk.
Hard disk problems can prevent Photoshop Lightroom from installing correctly. By installing Photoshop Lightroom to a different physical hard disk, you can verify if the original hard disk is preventing installation. First, completely remove Photoshop Lightroom from the hard disk.
To install Photoshop Lightroom to a different hard disk after disabling startup items:
Follow the steps in task 8 above to disable startup items.
If Photoshop Lightroom autoplay displays, click Cancel when you are requested to Select the Language.
Copy the Adobe Photoshop Lightroom folder from the Photoshop Lightroom CD-ROM to the desktop.
Open the Adobe Photoshop Lightroom folder on the desktop.
Double-click the Adobe Photoshop Lightroom.msi file, and follow the on-screen instructions.
Click Change and select a different hard disk in the Change Current Destination Folder window. Click OK, and then follow the on-screen instructions.
Intermediate troubleshooting
If the tasks in the previous section don't solve the problem, try the following intermediate troubleshooting tasks.
10. Install and run Photoshop Lightroom in a new user account.
Create a new user account that has the same permissions as the account that you use when the problem occurs. If the problem doesn't recur, the original user account may be damaged. For instructions on creating a new user account, see To add a new user to the computer in Windows Help or contact your system administrator.
11. Optimize handling of temporary files by Windows Vista.
Windows and applications store working data in temporary (.tmp) files that they create on the hard disk. Excessive or outdated temporary files can interfere with performance of Windows or applications.
Delete temporary files by using the Disk Cleanup utility included with Windows or by using the following instructions. Make sure that at least 1 GB of free space is available on the hard disk to which temporary files are written. To start Disk Cleanup, choose Start > All Programs > Accessories > System Tools > Disk Cleanup. For information about Disk Cleanup, see Windows Help.
To manually delete temporary files:
Note: Windows deletes temporary files when Windows and applications close normally. However, when Windows or an application crashes, temporary files can accumulate on the hard disk. Windows may prevent you from deleting some temporary files as they may be in use. Delete as many temporary files as you possibly can, without deleting the files that are in use.
Quit all applications.
Choose Start and type %tmp% in the Search text box and press Enter.
Delete the contents of this folder.
Note the drive letter where this directory is located.
To ensure that at least 1 GB of free space is available on the hard disk to which temporary files are written:
Choose Start > My Computer.
Select the drive noted in step 4. Right click and select Properties.
Confirm the drive has at least 1 GB of free space.
12. Repair and defragment hard disks.
System errors can occur if hard disks contain damaged sectors or fragmented files. Repair and defragment hard disks, either by using the Error-checking tool and Disk Defragmenter utility included with Windows or by using a third-party disk utility. You should run such utilities on each hard disk or partition. More information about the Error-checking tool and Disk Defragmenter appears below; for more information about a third-party disk utility, refer to the documentation for the utility.
The Error-checking tool repairs bad sectors, lost allocation units and file fragments, cross-linked files, and invalid file names. To access the Error-checking tool, choose Start > Computer, right-click the desired hard disk, and choose Properties from the menu. In the Local Disk Properties dialog box, click the Tools tab, and then click Check Now in the Error-checking area.
Note: To prevent Disk Defragmenter from moving files to bad sectors of a disk, run the Error-checking tool before running Disk Defragmenter.
Disk Defragmenter rearranges the files and free space on your computer so that files are stored in contiguous units and free space is consolidated in one contiguous block. To access the Disk Defragmenter utility, choose Start > All Programs > Accessories > System Tools > Disk Defragmenter.
13. Scan the system for viruses.
Use current anti-virus software to check the system for viruses. Virus infections can damage software and cause system errors. For more information, see the documentation for the anti-virus software.
14. Try to install Photoshop Lightroomon a different computer.
Try to install Photoshop Lightroom on a different computer to determine if the problem is unique to your computer. If the problem is unique to your computer, contact the computer manufacturer; if the problem occurs on multiple computers, contact Adobe Technical Support.
Advanced Troubleshooting
If the tasks in the previous section don't resolve the problem, you may be able to resolve the problem by reinstalling Windows Vista and Photoshop Lightroom, reformatting your hard disk and reinstalling Windows Vista and Photoshop Lightroom, or by determining if hardware is conflicting with Photoshop Lightroom.
Disclaimer: Adobe doesn't support hardware and provides these procedures as a courtesy only. For further assistance, contact the hardware manufacturer or an authorized reseller. If you troubleshoot hardware problems yourself, you may void the warranty for your computer.
Note: Before you remove or rearrange hardware, turn off and disconnect power to the computer and any peripheral devices.
15. Log in using the built-in Administrator account.
The built-in Administrator account has a higher access level to the system than a normal local administrator account. By default the built-in Administrator account is disabled. For information about enabling and logging in to the built-in Administrator account, contact your system administrator. You can also refer to this support document on the Microsoft support website: http://support.microsoft.com/kb/926183/en-us?spid=11737&sid=73.
16. Reformat the hard disk, and reinstall only Windows Vista and Photoshop Lightroom.
Reformat the hard disk, and then install only Windows Vista and Photoshop Lightroom from the original installation media. Reformatting a disk erases all files it contains, so be sure to back up all personal files first. Also make sure that you have all application and system disks.
For instructions on performing a clean installation of Windows Vista, see document 918884, "How to install Windows Vista" on the Microsoft website at http://support.microsoft.com.
Note: Don't install additional software or hardware until you're sure that the problem is resolved. Don't back up the hard disk and restore Windows and Photoshop Lightroom instead of reinstalling them. If the problem is caused by an application or Windows, and either one is restored instead of reinstalled, the problem may recur.
After you reformat the hard disk and reinstall Windows and Photoshop Lightroom, try to re-create the problem:
If the problem no longer occurs, then install other applications one at a time and try to re-create the problem after each installation. If the problem occurs after an installation, then the recently installed application may be the cause.
If the problem occurs when only Windows and Photoshop Lightroom are installed, then the cause may be hardware-related, and you should contact the hardware manufacturer or an authorized reseller for assistance.
17. Check for problems with RAM modules.
Ensure that the RAM modules are installed properly and are not the cause of your problem. Do one or both of the following:
Change the order of the installed modules.
Remove all but the minimum number of modules needed to run Windows and [product], and test to see if the problem persists. If it does, replace the modules you removed and remove the others, testing again to see if the problem recurs. If it doesn't, then one or more of the removed modules are the cause. For assistance, contact the RAM manufacturer.You've tried Help>Updates from within photoshop cs6?
Or this 8.3 updater
http://swupdl.adobe.com/updates/oobe/aam20/win/PhotoshopCameraRaw7-7.0/8.3.52/setup.zip
If that doesn't work, you can install camera raw 8.3 by following the directions on the following page
Adobe Camera Raw Help | Camera Raw/DNG Converter 8.4 on Mac OS 10.6, Windows XP, and Vista -
Chrome, other apps crashing on launch
I have a 21.5" iMac mid 2010, running OS X 10.9.3, Processor 3.06 GHz Intel Core i3, Memory: 12 GB 1333 MHz DDR3, Graphics: ATI Radeon HD 4670 256 MB, Disk: 500 GB SATA Disk.
This computer is primarily used by the teenagers in the house. It has three user accounts, plus the Other account, which is unused. I am the administrator.
The boys have been complaining about the computer running slowly, and it has, at times, shut down and rebooted on its own. So, it has not been a finely tuned system for awhile.
For a number of days, Chrome will launch to the Google page, but crash as soon as navigating to another site. After doing this for a couple of days, other programs are also doing the same thing (League of Legends, Civilization V, maybe more, according to my son.)
Some possible factors
Mavericks updated itself on June 15, 2014.
We had a thunderstorm that knocked out our electricity for a number of hours. The computer was on when that happened.
What I have tried:
Uninstalling and reinstalling Chrome.
Downloaded and ran Clean my Mac
Installed AVG and checked for viruses
Started Mac holding Ctrl R and checking disk for errors (no errors found).
When started in Safe Mode, Chrome works without crashing. The other programs (League of Legends, Civilization V) do not run in safe mode.
I have used the program EtreCheck to gather information about my system. Also, I have included the details from the crash window, below the EtreCheck info:
EtreCheck version: 1.9.12 (48)
Report generated June 22, 2014 at 10:22:06 PM CDT
Hardware Information:
iMac (21.5-inch, Mid 2010) (Verified)
iMac - model: iMac11,2
1 3.06 GHz Intel Core i3 CPU: 2 cores
12 GB RAM
Video Information:
ATI Radeon HD 4670 - VRAM: 256 MB
iMac 1920 x 1080
System Software:
OS X 10.9.3 (13D65) - Uptime: 0 days 0:10:59
Disk Information:
ST3500418AS disk0 : (500.11 GB)
EFI (disk0s1) <not mounted>: 209.7 MB
Macintosh HD (disk0s2) / [Startup]: 499.25 GB (102.69 GB free)
Recovery HD (disk0s3) <not mounted>: 650 MB
HL-DT-STDVDRW GA32N
USB Information:
Apple Internal Memory Card Reader
Apple Inc. BRCM2046 Hub
Apple Inc. Bluetooth USB Host Controller
Logitech USB Receiver
Apple Inc. Built-in iSight
Apple Computer, Inc. IR Receiver
Configuration files:
/etc/sysctl.conf - Exists
Gatekeeper:
Mac App Store and identified developers
Kernel Extensions:
[loaded] com.Cycling74.driver.Soundflower (1.6.6 - SDK 10.6) Support
Startup Items:
PenTabletDriver: Path: /Library/StartupItems/PenTabletDriver
Launch Daemons:
[loaded] com.adobe.fpsaud.plist Support
[running] com.autodesk.backburner_manager.plist Support
[running] com.autodesk.backburner_server.plist Support
[loaded] com.autodesk.backburner_start.plist Support
[running] com.avg.Antivirus.infosd.plist Support
[running] com.avg.Antivirus.services.plist Support
[loaded] com.google.keystone.daemon.plist Support
Launch Agents:
[not loaded] com.adobe.AAM.Updater-1.0.plist Support
[running] com.adobe.AdobeCreativeCloud.plist Support
[running] com.avg.Antivirus.gui.plist Support
[loaded] com.google.keystone.agent.plist Support
User Launch Agents:
[failed] com.apple.CSConfigDotMacCert-[...]@me.com-SharedServices.Agent.plist
User Login Items:
iTunesHelper
Alfred
Internet Plug-ins:
o1dbrowserplugin: Version: 5.4.2.18903 Support
Unity Web Player: Version: UnityPlayer version 4.3.5f1 - SDK 10.6 Support
Default Browser: Version: 537 - SDK 10.9
OfficeLiveBrowserPlugin: Version: 12.3.2 Support
AdobeAAMDetect: Version: AdobeAAMDetect 2.0.0.0 - SDK 10.7 Support
FlashPlayer-10.6: Version: 14.0.0.125 - SDK 10.6 Support
Silverlight: Version: 4.0.60531.0 Support
Flash Player: Version: 14.0.0.125 - SDK 10.6 Support
QuickTime Plugin: Version: 7.7.3
googletalkbrowserplugin: Version: 5.4.2.18903 Support
iPhotoPhotocast: Version: 7.0
JavaAppletPlugin: Version: 14.9.0 - SDK 10.7 Check version
Audio Plug-ins:
BluetoothAudioPlugIn: Version: 1.0 - SDK 10.9
AirPlay: Version: 2.0 - SDK 10.9
AppleAVBAudio: Version: 203.2 - SDK 10.9
iSightAudio: Version: 7.7.3 - SDK 10.9
iTunes Plug-ins:
Quartz Composer Visualizer: Version: 1.4 - SDK 10.9
User Internet Plug-ins:
Picasa: Version: 1.0 Support
3rd Party Preference Panes:
Flash Player Support
Time Machine:
Time Machine not configured!
Top Processes by CPU:
1% WindowServer
0% fontd
0% Creative Cloud
0% AVG
0% aosnotifyd
Top Processes by Memory:
184 MB avgd
135 MB mds_stores
135 MB com.apple.IconServicesAgent
123 MB Finder
111 MB com.apple.WebKit.WebContent
Virtual Memory Information:
8.09 GB Free RAM
2.53 GB Active RAM
614 MB Inactive RAM
800 MB Wired RAM
282 MB Page-ins
0 B Page-outs
From the error window, when Chrome crashes:
Process: Google Chrome [720]
Path: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
Identifier: com.google.Chrome
Version: 35.0.1916.153 (1916.153)
Code Type: X86 (Native)
Parent Process: launchd [231]
Responsible: Google Chrome [720]
User ID: 501
Date/Time: 2014-06-22 23:05:54.312 -0500
OS Version: Mac OS X 10.9.3 (13D65)
Report Version: 11
Anonymous UUID: 38C1557D-626E-58D0-AEDC-4CBBAE0456C3
Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000006
VM Regions Near 0x6:
--> __PAGEZERO 0000000000000000-0000000000001000 [ 4K] ---/--- SM=NUL /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
VM_ALLOCATE 0000000000001000-00000000000cd000 [ 816K] ---/--- SM=NUL
Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread
0 com.apple.QuickTimeComponents.component 0x9b27068b 0x9ab73000 + 7329419
1 com.apple.CoreServices.CarbonCore 0x997cec9f CallComponentDispatch + 29
2 com.apple.CoreServices.CarbonCore 0x9986cabc CallComponentOpen + 43
3 com.apple.CoreServices.CarbonCore 0x997ce83b OpenAComponent + 465
4 com.apple.CoreServices.CarbonCore 0x997ce9b5 OpenADefaultComponent + 128
5 com.apple.CMIOQTUnits 0x0c44e965 0xc427000 + 162149
6 com.apple.CMIOQTUnits 0x0c4514bf 0xc427000 + 173247
7 com.apple.CMIOQTUnits 0x0c4518e6 0xc427000 + 174310
8 com.apple.CMIOQTUnits 0x0c42ece7 0xc427000 + 31975
9 com.apple.CMIOQTUnits 0x0c44bd7a 0xc427000 + 150906
10 com.apple.QTKit 0x94becfba +[QTCaptureVDIGDevice _refreshDevices] + 470
11 com.apple.QTKit 0x94becc61 +[QTCaptureVDIGDevice devicesWithIOType:] + 106
12 com.apple.QTKit 0x94b3fd77 +[QTCaptureDevice devicesWithIOType:] + 200
13 com.apple.QTKit 0x94b2c922 +[QTCaptureDevice inputDevices] + 41
14 com.apple.QTKit 0x94b2c867 +[QTCaptureDevice inputDevicesWithMediaType:] + 36
15 com.google.Chrome.framework 0x016e5db0 0xd4000 + 23141808
16 com.google.Chrome.framework 0x008e2559 0xd4000 + 8447321
17 com.google.Chrome.framework 0x016e5c11 0xd4000 + 23141393
18 libobjc.A.dylib 0x9a3d21c7 +[NSObject performSelector:withObject:] + 70
19 com.apple.Foundation 0x95e044b2 __NSThreadPerformPerform + 318
20 com.apple.CoreFoundation 0x961c0b6f __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 15
21 com.apple.CoreFoundation 0x961b1a35 __CFRunLoopDoSources0 + 437
22 com.apple.CoreFoundation 0x961b106e __CFRunLoopRun + 1022
23 com.apple.CoreFoundation 0x961b09fa CFRunLoopRunSpecific + 394
24 com.apple.CoreFoundation 0x961b085b CFRunLoopRunInMode + 123
25 com.apple.HIToolbox 0x97ec3b5d RunCurrentEventLoopInMode + 259
26 com.apple.HIToolbox 0x97ec38e2 ReceiveNextEventCommon + 526
27 com.apple.HIToolbox 0x97ec36bd _BlockUntilNextEventMatchingListInModeWithFilter + 92
28 com.apple.AppKit 0x9116b369 _DPSNextEvent + 1602
29 com.apple.AppKit 0x9116a890 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 119
30 com.apple.AppKit 0x9115d17c -[NSApplication run] + 727
31 com.google.Chrome.framework 0x008a662b 0xd4000 + 8201771
32 com.google.Chrome.framework 0x008a5ebc 0xd4000 + 8199868
33 com.google.Chrome.framework 0x008e8a31 0xd4000 + 8473137
34 com.google.Chrome.framework 0x008fe6e1 0xd4000 + 8562401
35 com.google.Chrome.framework 0x0022afe4 0xd4000 + 1404900
36 com.google.Chrome.framework 0x02d6f0d0 0xd4000 + 46772432
37 com.google.Chrome.framework 0x02d71253 0xd4000 + 46781011
38 com.google.Chrome.framework 0x02d6b0de 0xd4000 + 46756062
39 com.google.Chrome.framework 0x008720a3 0xd4000 + 7987363
40 com.google.Chrome.framework 0x00872aee 0xd4000 + 7989998
41 com.google.Chrome.framework 0x00871f12 0xd4000 + 7986962
42 com.google.Chrome.framework 0x000d7045 ChromeMain + 53
43 com.google.Chrome 0x000cdf78 main + 24
44 com.google.Chrome 0x000cdf55 0xcd000 + 3925
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x94b23992 kevent64 + 10
1 libdispatch.dylib 0x92cc3899 _dispatch_mgr_invoke + 238
2 libdispatch.dylib 0x92cc3532 _dispatch_mgr_thread + 52
Thread 2:: NetworkConfigWatcher
0 libsystem_kernel.dylib 0x94b1df7a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x94b1d16c mach_msg + 68
2 com.apple.CoreFoundation 0x961b1c09 __CFRunLoopServiceMachPort + 169
3 com.apple.CoreFoundation 0x961b11e1 __CFRunLoopRun + 1393
4 com.apple.CoreFoundation 0x961b09fa CFRunLoopRunSpecific + 394
5 com.apple.CoreFoundation 0x961b085b CFRunLoopRunInMode + 123
6 com.apple.Foundation 0x95e0a2f9 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 277
7 com.google.Chrome.framework 0x008a645f 0xd4000 + 8201311
8 com.google.Chrome.framework 0x008a5ebc 0xd4000 + 8199868
9 com.google.Chrome.framework 0x008e8a31 0xd4000 + 8473137
10 com.google.Chrome.framework 0x008fe6e1 0xd4000 + 8562401
11 com.google.Chrome.framework 0x008e87ba 0xd4000 + 8472506
12 com.google.Chrome.framework 0x00915191 0xd4000 + 8655249
13 com.google.Chrome.framework 0x00915270 0xd4000 + 8655472
14 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
15 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
16 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
17 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 3:: DnsConfigService
0 libsystem_kernel.dylib 0x94b23976 kevent + 10
1 com.google.Chrome.framework 0x009287bb 0xd4000 + 8734651
2 com.google.Chrome.framework 0x00926489 0xd4000 + 8725641
3 com.google.Chrome.framework 0x008a50b4 0xd4000 + 8196276
4 com.google.Chrome.framework 0x008e8a31 0xd4000 + 8473137
5 com.google.Chrome.framework 0x008fe6e1 0xd4000 + 8562401
6 com.google.Chrome.framework 0x008e87ba 0xd4000 + 8472506
7 com.google.Chrome.framework 0x00915191 0xd4000 + 8655249
8 com.google.Chrome.framework 0x00915270 0xd4000 + 8655472
9 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
10 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
11 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
12 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 4:: WorkerPool/23051
0 libsystem_kernel.dylib 0x94b227ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x9972ed8a _pthread_cond_wait + 837
2 libsystem_pthread.dylib 0x9972f042 pthread_cond_timedwait_relative_np + 47
3 com.google.Chrome.framework 0x0090ba85 0xd4000 + 8616581
4 com.google.Chrome.framework 0x00917cc1 0xd4000 + 8666305
5 com.google.Chrome.framework 0x0091821d 0xd4000 + 8667677
6 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
7 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
8 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
9 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 5:: CrShutdownDetector
0 libsystem_kernel.dylib 0x94b23dba __read + 10
1 com.google.Chrome.framework 0x0022c533 0xd4000 + 1410355
2 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
3 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
4 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
5 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 6:: Chrome_DBThread
0 libsystem_kernel.dylib 0x94b227ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x9972ed1d _pthread_cond_wait + 728
2 libsystem_pthread.dylib 0x99730bd9 pthread_cond_wait$UNIX2003 + 71
3 com.google.Chrome.framework 0x0090ba08 0xd4000 + 8616456
4 com.google.Chrome.framework 0x0090bf0b 0xd4000 + 8617739
5 com.google.Chrome.framework 0x0090bd96 0xd4000 + 8617366
6 com.google.Chrome.framework 0x008eb4e7 0xd4000 + 8484071
7 com.google.Chrome.framework 0x008e8a31 0xd4000 + 8473137
8 com.google.Chrome.framework 0x008fe6e1 0xd4000 + 8562401
9 com.google.Chrome.framework 0x008e87ba 0xd4000 + 8472506
10 com.google.Chrome.framework 0x00915191 0xd4000 + 8655249
11 com.google.Chrome.framework 0x02d7e8cf 0xd4000 + 46835919
12 com.google.Chrome.framework 0x00915270 0xd4000 + 8655472
13 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
14 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
15 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
16 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 7:: Chrome_FileThread
0 libsystem_kernel.dylib 0x94b23976 kevent + 10
1 com.google.Chrome.framework 0x009287bb 0xd4000 + 8734651
2 com.google.Chrome.framework 0x00926489 0xd4000 + 8725641
3 com.google.Chrome.framework 0x008a5193 0xd4000 + 8196499
4 com.google.Chrome.framework 0x008e8a31 0xd4000 + 8473137
5 com.google.Chrome.framework 0x008fe6e1 0xd4000 + 8562401
6 com.google.Chrome.framework 0x008e87ba 0xd4000 + 8472506
7 com.google.Chrome.framework 0x00915191 0xd4000 + 8655249
8 com.google.Chrome.framework 0x02d7e90f 0xd4000 + 46835983
9 com.google.Chrome.framework 0x00915270 0xd4000 + 8655472
10 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
11 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
12 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
13 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 8:: Chrome_FileUserBlockingThread
0 libsystem_kernel.dylib 0x94b227ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x9972ed1d _pthread_cond_wait + 728
2 libsystem_pthread.dylib 0x99730bd9 pthread_cond_wait$UNIX2003 + 71
3 com.google.Chrome.framework 0x0090ba08 0xd4000 + 8616456
4 com.google.Chrome.framework 0x0090bf0b 0xd4000 + 8617739
5 com.google.Chrome.framework 0x0090bd96 0xd4000 + 8617366
6 com.google.Chrome.framework 0x008eb4e7 0xd4000 + 8484071
7 com.google.Chrome.framework 0x008e8a31 0xd4000 + 8473137
8 com.google.Chrome.framework 0x008fe6e1 0xd4000 + 8562401
9 com.google.Chrome.framework 0x008e87ba 0xd4000 + 8472506
10 com.google.Chrome.framework 0x00915191 0xd4000 + 8655249
11 com.google.Chrome.framework 0x02d7e94f 0xd4000 + 46836047
12 com.google.Chrome.framework 0x00915270 0xd4000 + 8655472
13 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
14 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
15 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
16 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 9:: Chrome_ProcessLauncherThread
0 libsystem_kernel.dylib 0x94b227ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x9972ed1d _pthread_cond_wait + 728
2 libsystem_pthread.dylib 0x99730bd9 pthread_cond_wait$UNIX2003 + 71
3 com.google.Chrome.framework 0x0090ba08 0xd4000 + 8616456
4 com.google.Chrome.framework 0x0090bf0b 0xd4000 + 8617739
5 com.google.Chrome.framework 0x0090bd96 0xd4000 + 8617366
6 com.google.Chrome.framework 0x008eb4e7 0xd4000 + 8484071
7 com.google.Chrome.framework 0x008e8a31 0xd4000 + 8473137
8 com.google.Chrome.framework 0x008fe6e1 0xd4000 + 8562401
9 com.google.Chrome.framework 0x008e87ba 0xd4000 + 8472506
10 com.google.Chrome.framework 0x00915191 0xd4000 + 8655249
11 com.google.Chrome.framework 0x02d7e98f 0xd4000 + 46836111
12 com.google.Chrome.framework 0x00915270 0xd4000 + 8655472
13 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
14 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
15 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
16 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 10:: Chrome_CacheThread
0 libsystem_kernel.dylib 0x94b23976 kevent + 10
1 com.google.Chrome.framework 0x009287bb 0xd4000 + 8734651
2 com.google.Chrome.framework 0x00926489 0xd4000 + 8725641
3 com.google.Chrome.framework 0x008a5193 0xd4000 + 8196499
4 com.google.Chrome.framework 0x008e8a31 0xd4000 + 8473137
5 com.google.Chrome.framework 0x008fe6e1 0xd4000 + 8562401
6 com.google.Chrome.framework 0x008e87ba 0xd4000 + 8472506
7 com.google.Chrome.framework 0x00915191 0xd4000 + 8655249
8 com.google.Chrome.framework 0x02d7e9cf 0xd4000 + 46836175
9 com.google.Chrome.framework 0x00915270 0xd4000 + 8655472
10 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
11 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
12 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
13 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 11:: Chrome_IOThread
0 libsystem_kernel.dylib 0x94b23976 kevent + 10
1 com.google.Chrome.framework 0x009287bb 0xd4000 + 8734651
2 com.google.Chrome.framework 0x00926489 0xd4000 + 8725641
3 com.google.Chrome.framework 0x008a5193 0xd4000 + 8196499
4 com.google.Chrome.framework 0x008e8a31 0xd4000 + 8473137
5 com.google.Chrome.framework 0x008fe6e1 0xd4000 + 8562401
6 com.google.Chrome.framework 0x008e87ba 0xd4000 + 8472506
7 com.google.Chrome.framework 0x00915191 0xd4000 + 8655249
8 com.google.Chrome.framework 0x02d7ea0f 0xd4000 + 46836239
9 com.google.Chrome.framework 0x00915270 0xd4000 + 8655472
10 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
11 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
12 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
13 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 12:: IndexedDB
0 libsystem_kernel.dylib 0x94b227ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x9972ed1d _pthread_cond_wait + 728
2 libsystem_pthread.dylib 0x99730bd9 pthread_cond_wait$UNIX2003 + 71
3 com.google.Chrome.framework 0x0090ba08 0xd4000 + 8616456
4 com.google.Chrome.framework 0x0090bf0b 0xd4000 + 8617739
5 com.google.Chrome.framework 0x0090bd96 0xd4000 + 8617366
6 com.google.Chrome.framework 0x008eb4e7 0xd4000 + 8484071
7 com.google.Chrome.framework 0x008e8a31 0xd4000 + 8473137
8 com.google.Chrome.framework 0x008fe6e1 0xd4000 + 8562401
9 com.google.Chrome.framework 0x008e87ba 0xd4000 + 8472506
10 com.google.Chrome.framework 0x00915191 0xd4000 + 8655249
11 com.google.Chrome.framework 0x00915270 0xd4000 + 8655472
12 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
13 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
14 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
15 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 13:: NetworkConfigWatcher
0 libsystem_kernel.dylib 0x94b1df7a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x94b1d16c mach_msg + 68
2 com.apple.CoreFoundation 0x961b1c09 __CFRunLoopServiceMachPort + 169
3 com.apple.CoreFoundation 0x961b11e1 __CFRunLoopRun + 1393
4 com.apple.CoreFoundation 0x961b09fa CFRunLoopRunSpecific + 394
5 com.apple.CoreFoundation 0x961b085b CFRunLoopRunInMode + 123
6 com.apple.Foundation 0x95e0a2f9 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 277
7 com.google.Chrome.framework 0x008a645f 0xd4000 + 8201311
8 com.google.Chrome.framework 0x008a5ebc 0xd4000 + 8199868
9 com.google.Chrome.framework 0x008e8a31 0xd4000 + 8473137
10 com.google.Chrome.framework 0x008fe6e1 0xd4000 + 8562401
11 com.google.Chrome.framework 0x008e87ba 0xd4000 + 8472506
12 com.google.Chrome.framework 0x00915191 0xd4000 + 8655249
13 com.google.Chrome.framework 0x00915270 0xd4000 + 8655472
14 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
15 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
16 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
17 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 14:: Proxy resolver
0 libsystem_kernel.dylib 0x94b227ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x9972ed1d _pthread_cond_wait + 728
2 libsystem_pthread.dylib 0x99730bd9 pthread_cond_wait$UNIX2003 + 71
3 com.google.Chrome.framework 0x0090ba08 0xd4000 + 8616456
4 com.google.Chrome.framework 0x0090bf0b 0xd4000 + 8617739
5 com.google.Chrome.framework 0x0090bd96 0xd4000 + 8617366
6 com.google.Chrome.framework 0x008eb4e7 0xd4000 + 8484071
7 com.google.Chrome.framework 0x008e8a31 0xd4000 + 8473137
8 com.google.Chrome.framework 0x008fe6e1 0xd4000 + 8562401
9 com.google.Chrome.framework 0x008e87ba 0xd4000 + 8472506
10 com.google.Chrome.framework 0x00915191 0xd4000 + 8655249
11 com.google.Chrome.framework 0x00915270 0xd4000 + 8655472
12 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
13 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
14 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
15 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 15:: AudioThread
0 libsystem_kernel.dylib 0x94b227ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x9972ed1d _pthread_cond_wait + 728
2 libsystem_pthread.dylib 0x99730bd9 pthread_cond_wait$UNIX2003 + 71
3 com.apple.Foundation 0x95e04ffa -[NSCondition wait] + 274
4 com.apple.Foundation 0x95dce677 -[NSObject(NSThreadPerformAdditions) performSelector:onThread:withObject:waitUntilDone:modes:] + 741
5 com.apple.Foundation 0x95dce2a5 -[NSObject(NSThreadPerformAdditions) performSelectorOnMainThread:withObject:waitUntilDone:] + 159
6 com.google.Chrome.framework 0x016e5e38 0xd4000 + 23141944
7 com.google.Chrome.framework 0x016e4a22 0xd4000 + 23136802
8 com.google.Chrome.framework 0x02f02287 0xd4000 + 48423559
9 com.google.Chrome.framework 0x02f05faa 0xd4000 + 48439210
10 com.google.Chrome.framework 0x02f05c44 0xd4000 + 48438340
11 com.google.Chrome.framework 0x02f05e09 0xd4000 + 48438793
12 com.google.Chrome.framework 0x009113ab 0xd4000 + 8639403
13 com.google.Chrome.framework 0x00911441 0xd4000 + 8639553
14 com.google.Chrome.framework 0x008e8e1a 0xd4000 + 8474138
15 com.google.Chrome.framework 0x008e94a4 0xd4000 + 8475812
16 com.google.Chrome.framework 0x008eb555 0xd4000 + 8484181
17 com.google.Chrome.framework 0x008e8a31 0xd4000 + 8473137
18 com.google.Chrome.framework 0x008fe6e1 0xd4000 + 8562401
19 com.google.Chrome.framework 0x008e87ba 0xd4000 + 8472506
20 com.google.Chrome.framework 0x00915191 0xd4000 + 8655249
21 com.google.Chrome.framework 0x00915270 0xd4000 + 8655472
22 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
23 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
24 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
25 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 16:: BrowserWatchdog
0 libsystem_kernel.dylib 0x94b227ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x9972ed8a _pthread_cond_wait + 837
2 libsystem_pthread.dylib 0x9972f042 pthread_cond_timedwait_relative_np + 47
3 com.google.Chrome.framework 0x0090ba85 0xd4000 + 8616581
4 com.google.Chrome.framework 0x0090bee8 0xd4000 + 8617704
5 com.google.Chrome.framework 0x008eb523 0xd4000 + 8484131
6 com.google.Chrome.framework 0x008e8a31 0xd4000 + 8473137
7 com.google.Chrome.framework 0x008fe6e1 0xd4000 + 8562401
8 com.google.Chrome.framework 0x008e87ba 0xd4000 + 8472506
9 com.google.Chrome.framework 0x00915191 0xd4000 + 8655249
10 com.google.Chrome.framework 0x00915270 0xd4000 + 8655472
11 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
12 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
13 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
14 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 17:
0 libsystem_kernel.dylib 0x94b1df7a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x94b1d16c mach_msg + 68
2 com.google.Chrome.framework 0x02e97b80 0xd4000 + 47987584
3 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
4 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
5 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
6 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 18:: BrowserBlockingWorker1/39939
0 libsystem_kernel.dylib 0x94b227ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x9972ed8a _pthread_cond_wait + 837
2 libsystem_pthread.dylib 0x9972f042 pthread_cond_timedwait_relative_np + 47
3 com.google.Chrome.framework 0x0090ba85 0xd4000 + 8616581
4 com.google.Chrome.framework 0x00912069 0xd4000 + 8642665
5 com.google.Chrome.framework 0x0091176d 0xd4000 + 8640365
6 com.google.Chrome.framework 0x00914903 0xd4000 + 8653059
7 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
8 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
9 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
10 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 19:: NetworkConfigWatcher
0 libsystem_kernel.dylib 0x94b1df7a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x94b1d16c mach_msg + 68
2 com.apple.CoreFoundation 0x961b1c09 __CFRunLoopServiceMachPort + 169
3 com.apple.CoreFoundation 0x961b11e1 __CFRunLoopRun + 1393
4 com.apple.CoreFoundation 0x961b09fa CFRunLoopRunSpecific + 394
5 com.apple.CoreFoundation 0x961b085b CFRunLoopRunInMode + 123
6 com.apple.Foundation 0x95e0a2f9 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 277
7 com.google.Chrome.framework 0x008a645f 0xd4000 + 8201311
8 com.google.Chrome.framework 0x008a5ebc 0xd4000 + 8199868
9 com.google.Chrome.framework 0x008e8a31 0xd4000 + 8473137
10 com.google.Chrome.framework 0x008fe6e1 0xd4000 + 8562401
11 com.google.Chrome.framework 0x008e87ba 0xd4000 + 8472506
12 com.google.Chrome.framework 0x00915191 0xd4000 + 8655249
13 com.google.Chrome.framework 0x00915270 0xd4000 + 8655472
14 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
15 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
16 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
17 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 20:: Proxy resolver
0 libsystem_kernel.dylib 0x94b227ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x9972ed1d _pthread_cond_wait + 728
2 libsystem_pthread.dylib 0x99730bd9 pthread_cond_wait$UNIX2003 + 71
3 com.google.Chrome.framework 0x0090ba08 0xd4000 + 8616456
4 com.google.Chrome.framework 0x0090bf0b 0xd4000 + 8617739
5 com.google.Chrome.framework 0x0090bd96 0xd4000 + 8617366
6 com.google.Chrome.framework 0x008eb4e7 0xd4000 + 8484071
7 com.google.Chrome.framework 0x008e8a31 0xd4000 + 8473137
8 com.google.Chrome.framework 0x008fe6e1 0xd4000 + 8562401
9 com.google.Chrome.framework 0x008e87ba 0xd4000 + 8472506
10 com.google.Chrome.framework 0x00915191 0xd4000 + 8655249
11 com.google.Chrome.framework 0x00915270 0xd4000 + 8655472
12 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
13 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
14 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
15 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 21:: Chrome_SafeBrowsingThread
0 libsystem_kernel.dylib 0x94b227ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x9972ed1d _pthread_cond_wait + 728
2 libsystem_pthread.dylib 0x99730bd9 pthread_cond_wait$UNIX2003 + 71
3 com.google.Chrome.framework 0x0090ba08 0xd4000 + 8616456
4 com.google.Chrome.framework 0x0090bf0b 0xd4000 + 8617739
5 com.google.Chrome.framework 0x0090bd96 0xd4000 + 8617366
6 com.google.Chrome.framework 0x008eb4e7 0xd4000 + 8484071
7 com.google.Chrome.framework 0x008e8a31 0xd4000 + 8473137
8 com.google.Chrome.framework 0x008fe6e1 0xd4000 + 8562401
9 com.google.Chrome.framework 0x008e87ba 0xd4000 + 8472506
10 com.google.Chrome.framework 0x00915191 0xd4000 + 8655249
11 com.google.Chrome.framework 0x00915270 0xd4000 + 8655472
12 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
13 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
14 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
15 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 22:: BrowserBlockingWorker2/42243
0 libsystem_kernel.dylib 0x94b227ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x9972ed8a _pthread_cond_wait + 837
2 libsystem_pthread.dylib 0x9972f042 pthread_cond_timedwait_relative_np + 47
3 com.google.Chrome.framework 0x0090ba85 0xd4000 + 8616581
4 com.google.Chrome.framework 0x00912069 0xd4000 + 8642665
5 com.google.Chrome.framework 0x0091176d 0xd4000 + 8640365
6 com.google.Chrome.framework 0x00914903 0xd4000 + 8653059
7 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
8 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
9 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
10 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 23:: BrowserBlockingWorker3/48643
0 libsystem_kernel.dylib 0x94b227ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x9972ed8a _pthread_cond_wait + 837
2 libsystem_pthread.dylib 0x9972f042 pthread_cond_timedwait_relative_np + 47
3 com.google.Chrome.framework 0x0090ba85 0xd4000 + 8616581
4 com.google.Chrome.framework 0x00912069 0xd4000 + 8642665
5 com.google.Chrome.framework 0x0091176d 0xd4000 + 8640365
6 com.google.Chrome.framework 0x00914903 0xd4000 + 8653059
7 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
8 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
9 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
10 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 24:: Chrome_HistoryThread
0 libsystem_kernel.dylib 0x94b227ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x9972ed8a _pthread_cond_wait + 837
2 libsystem_pthread.dylib 0x9972f042 pthread_cond_timedwait_relative_np + 47
3 com.google.Chrome.framework 0x0090ba85 0xd4000 + 8616581
4 com.google.Chrome.framework 0x0090bee8 0xd4000 + 8617704
5 com.google.Chrome.framework 0x008eb523 0xd4000 + 8484131
6 com.google.Chrome.framework 0x008e8a31 0xd4000 + 8473137
7 com.google.Chrome.framework 0x008fe6e1 0xd4000 + 8562401
8 com.google.Chrome.framework 0x008e87ba 0xd4000 + 8472506
9 com.google.Chrome.framework 0x00915191 0xd4000 + 8655249
10 com.google.Chrome.framework 0x00915270 0xd4000 + 8655472
11 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
12 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
13 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
14 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 25:
0 libsystem_kernel.dylib 0x94b1df7a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x94b1d16c mach_msg + 68
2 com.apple.CoreFoundation 0x961b1c09 __CFRunLoopServiceMachPort + 169
3 com.apple.CoreFoundation 0x961b11e1 __CFRunLoopRun + 1393
4 com.apple.CoreFoundation 0x961b09fa CFRunLoopRunSpecific + 394
5 com.apple.CoreFoundation 0x961b085b CFRunLoopRunInMode + 123
6 com.apple.AppKit 0x91314b88 _NSEventThread + 283
7 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
8 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
9 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 26:: CachePoolWorker1/71175
0 libsystem_kernel.dylib 0x94b227ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x9972ed1d _pthread_cond_wait + 728
2 libsystem_pthread.dylib 0x99730bd9 pthread_cond_wait$UNIX2003 + 71
3 com.google.Chrome.framework 0x0090ba08 0xd4000 + 8616456
4 com.google.Chrome.framework 0x009120db 0xd4000 + 8642779
5 com.google.Chrome.framework 0x0091176d 0xd4000 + 8640365
6 com.google.Chrome.framework 0x00914903 0xd4000 + 8653059
7 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
8 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
9 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
10 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 27:: LevelDBEnv
0 libsystem_kernel.dylib 0x94b227ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x9972ed1d _pthread_cond_wait + 728
2 libsystem_pthread.dylib 0x99730bd9 pthread_cond_wait$UNIX2003 + 71
3 com.google.Chrome.framework 0x0090ba08 0xd4000 + 8616456
4 com.google.Chrome.framework 0x02c2ee58 0xd4000 + 45461080
5 com.google.Chrome.framework 0x02c2f7e1 0xd4000 + 45463521
6 com.google.Chrome.framework 0x02c30081 0xd4000 + 45465729
7 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
8 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
9 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
10 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 28:: Service Discovery Thread
0 libsystem_kernel.dylib 0x94b1df7a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x94b1d16c mach_msg + 68
2 com.apple.CoreFoundation 0x961b1c09 __CFRunLoopServiceMachPort + 169
3 com.apple.CoreFoundation 0x961b11e1 __CFRunLoopRun + 1393
4 com.apple.CoreFoundation 0x961b09fa CFRunLoopRunSpecific + 394
5 com.apple.CoreFoundation 0x961b085b CFRunLoopRunInMode + 123
6 com.apple.Foundation 0x95e0a2f9 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 277
7 com.google.Chrome.framework 0x008a645f 0xd4000 + 8201311
8 com.google.Chrome.framework 0x008a5ebc 0xd4000 + 8199868
9 com.google.Chrome.framework 0x008e8a31 0xd4000 + 8473137
10 com.google.Chrome.framework 0x008fe6e1 0xd4000 + 8562401
11 com.google.Chrome.framework 0x008e87ba 0xd4000 + 8472506
12 com.google.Chrome.framework 0x00915191 0xd4000 + 8655249
13 com.google.Chrome.framework 0x00915270 0xd4000 + 8655472
14 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
15 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
16 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
17 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 29:: com.apple.CFSocket.private
0 libsystem_kernel.dylib 0x94b22ace __select + 10
1 com.apple.CoreFoundation 0x96201af6 __CFSocketManager + 1158
2 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
3 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
4 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 30:
0 libsystem_kernel.dylib 0x94b23046 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x9972ddcf _pthread_wqthread + 372
2 libsystem_pthread.dylib 0x99731cce start_wqthread + 30
Thread 31:
0 libsystem_kernel.dylib 0x94b23046 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x9972ddcf _pthread_wqthread + 372
2 libsystem_pthread.dylib 0x99731cce start_wqthread + 30
Thread 32:: PowerSaveBlocker
0 libsystem_kernel.dylib 0x94b227ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x9972ed1d _pthread_cond_wait + 728
2 libsystem_pthread.dylib 0x99730bd9 pthread_cond_wait$UNIX2003 + 71
3 com.google.Chrome.framework 0x0090ba08 0xd4000 + 8616456
4 com.google.Chrome.framework 0x0090bf0b 0xd4000 + 8617739
5 com.google.Chrome.framework 0x0090bd96 0xd4000 + 8617366
6 com.google.Chrome.framework 0x008eb4e7 0xd4000 + 8484071
7 com.google.Chrome.framework 0x008e8a31 0xd4000 + 8473137
8 com.google.Chrome.framework 0x008fe6e1 0xd4000 + 8562401
9 com.google.Chrome.framework 0x008e87ba 0xd4000 + 8472506
10 com.google.Chrome.framework 0x00915191 0xd4000 + 8655249
11 com.google.Chrome.framework 0x00915270 0xd4000 + 8655472
12 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
13 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
14 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
15 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 33:: WorkerPool/83255
0 libsystem_kernel.dylib 0x94b227ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x9972ed8a _pthread_cond_wait + 837
2 libsystem_pthread.dylib 0x9972f042 pthread_cond_timedwait_relative_np + 47
3 com.google.Chrome.framework 0x0090ba85 0xd4000 + 8616581
4 com.google.Chrome.framework 0x00917cc1 0xd4000 + 8666305
5 com.google.Chrome.framework 0x0091821d 0xd4000 + 8667677
6 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
7 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
8 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
9 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 34:: Chrome_PasswordStore_Thread
0 libsystem_kernel.dylib 0x94b227ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x9972ed1d _pthread_cond_wait + 728
2 libsystem_pthread.dylib 0x99730bd9 pthread_cond_wait$UNIX2003 + 71
3 com.google.Chrome.framework 0x0090ba08 0xd4000 + 8616456
4 com.google.Chrome.framework 0x0090bf0b 0xd4000 + 8617739
5 com.google.Chrome.framework 0x0090bd96 0xd4000 + 8617366
6 com.google.Chrome.framework 0x008eb4e7 0xd4000 + 8484071
7 com.google.Chrome.framework 0x008e8a31 0xd4000 + 8473137
8 com.google.Chrome.framework 0x008fe6e1 0xd4000 + 8562401
9 com.google.Chrome.framework 0x008e87ba 0xd4000 + 8472506
10 com.google.Chrome.framework 0x00915191 0xd4000 + 8655249
11 com.google.Chrome.framework 0x00915270 0xd4000 + 8655472
12 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
13 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
14 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
15 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 35:: CachePoolWorker2/80539
0 libsystem_kernel.dylib 0x94b227ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x9972ed1d _pthread_cond_wait + 728
2 libsystem_pthread.dylib 0x99730bd9 pthread_cond_wait$UNIX2003 + 71
3 com.google.Chrome.framework 0x0090ba08 0xd4000 + 8616456
4 com.google.Chrome.framework 0x009120db 0xd4000 + 8642779
5 com.google.Chrome.framework 0x0091176d 0xd4000 + 8640365
6 com.google.Chrome.framework 0x00914903 0xd4000 + 8653059
7 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
8 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
9 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
10 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 36:: CVDisplayLink
0 libsystem_kernel.dylib 0x94b227ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x9972ed8a _pthread_cond_wait + 837
2 libsystem_pthread.dylib 0x9972f042 pthread_cond_timedwait_relative_np + 47
3 com.apple.CoreVideo 0x99bc933d CVDisplayLink::waitUntil(unsigned long long) + 287
4 com.apple.CoreVideo 0x99bc842e CVDisplayLink::runIOThread() + 662
5 com.apple.CoreVideo 0x99bc8180 startIOThread(void*) + 159
6 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
7 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
8 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 37:: CachePoolWorker3/79919
0 libsystem_kernel.dylib 0x94b227ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x9972ed1d _pthread_cond_wait + 728
2 libsystem_pthread.dylib 0x99730bd9 pthread_cond_wait$UNIX2003 + 71
3 com.google.Chrome.framework 0x0090ba08 0xd4000 + 8616456
4 com.google.Chrome.framework 0x009120db 0xd4000 + 8642779
5 com.google.Chrome.framework 0x0091176d 0xd4000 + 8640365
6 com.google.Chrome.framework 0x00914903 0xd4000 + 8653059
7 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
8 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
9 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
10 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 38:: CachePoolWorker4/70423
0 libsystem_kernel.dylib 0x94b227ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x9972ed1d _pthread_cond_wait + 728
2 libsystem_pthread.dylib 0x99730bd9 pthread_cond_wait$UNIX2003 + 71
3 com.google.Chrome.framework 0x0090ba08 0xd4000 + 8616456
4 com.google.Chrome.framework 0x009120db 0xd4000 + 8642779
5 com.google.Chrome.framework 0x0091176d 0xd4000 + 8640365
6 com.google.Chrome.framework 0x00914903 0xd4000 + 8653059
7 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
8 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
9 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
10 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 39:: CachePoolWorker5/16143
0 libsystem_kernel.dylib 0x94b227ca __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x9972ed1d _pthread_cond_wait + 728
2 libsystem_pthread.dylib 0x99730bd9 pthread_cond_wait$UNIX2003 + 71
3 com.google.Chrome.framework 0x0090ba08 0xd4000 + 8616456
4 com.google.Chrome.framework 0x009120db 0xd4000 + 8642779
5 com.google.Chrome.framework 0x0091176d 0xd4000 + 8640365
6 com.google.Chrome.framework 0x00914903 0xd4000 + 8653059
7 com.google.Chrome.framework 0x00911165 0xd4000 + 8638821
8 libsystem_pthread.dylib 0x9972c5fb _pthread_body + 144
9 libsystem_pthread.dylib 0x9972c485 _pthread_start + 130
10 libsystem_pthread.dylib 0x99731cf2 thread_start + 34
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0xbff30b12 ebx: 0x00000081 ecx: 0x00000000 edx: 0x9b270606
edi: 0x00000081 esi: 0x00000081 ebp: 0xbff30af8 esp: 0xbff30adc
ss: 0x00000023 efl: 0x00010202 eip: 0x9b27068b cs: 0x0000001b
ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f
cr2: 0x00000006
Logical CPU: 0
Error Code: 0x00000006
Trap Number: 14
Binary Images:
0xcd000 - 0xcdff3 +com.google.Chrome (35.0.1916.153 - 1916.153) <59BC7C1F-40CC-3C24-BDCF-A3A6EFA9A193> /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
0xd4000 - 0x45c5fa3 +com.google.Chrome.framework (35.0.1916.15Did you remove them according to the developer's instructions?
How to Uninstall CleanMyMac Classic ... - MacPaw
How To Uninstall CleanMyMac 2? Complete Removal of ...
AVG knowledge base -
Setting Up Google Chrome Features for Cloud Printing from an Android Device
These steps are organized for optimal setup procedure and to decrease the time it would take to set this option up from start to finish. This is a lengthy process and is more for possibly troubleshooting issues that may arise during the setup of Google Chrome's Cloud Print feature. However, if you have an Android phone or tablet and are interested in being able to print virtually anything at anytime from anywhere from your phone to any brand of printer regardless of setup, there is a way. And this is how:
Open/Install Google Chrome onto a computer
Sign in with personal email to access the same Google Chrome account you intent to print from
Download Google Drive as an external storage you can access from anywhere
Open Google Chrome Settings (three lines stacked on top of each other)
Scroll down to the bottom of settings and click "Advanced Settings"
"Sign in/add printers/manage printers" are three of the print options you may see here
Follow this link for information on:
adding a classic printer to this option: https://support.google.com/cloudprint/answer/1686197?rd=1
how to add an HP ePrint email: https://www.google.com/cloudprint/learn/printers.html#info-hp
on registering the email of that printer (HP registration page): https://www.google.com/cloudprint/learn/setup-hp.html
8. add the printer to this section of Google Chrome
9. at the bottom of the page you will see "Send a test page/print test page" (that will be useful later)
10. at the top of this page is the option to share this printer with other Google Chrome users
11. Open Google Drive from www.google.com (likely displayed at the top of the webpage)
Can create a new document of any file type, upload, draw, etc
Leave computer on if intending to print from off the network or another location
The next steps are in regards to printing from a mobile device:
Install/open Cloud Print App
Add personal email account associated with Google Chrome
Select printer management if on the same network as the printer
Select Web tab and Google Drive if not on the same home network
Find earlier test page in Google Drive Documents
To locate other documents one could find many applications within this app or
In another app like Documents To Go, you can select to send previously saved documents (like one might send an email on the Android) to the Cloud Print app to open, view, and print
Print Test Document – this function means the printer has officially been added now
In Google Drive, but within the Cloud Print app, you can select the printer that was added to this network or from "Printer Management Options."
There are many ways to determine if your printer is still connected (offline, ready, etc.) but after confirmation that the printer is available, print jobs rest in the print queue until the printer receives the command to print. Then the documents are stored and available for reprinting.
Converts most print jobs to .pdf but prints most file formats from other applications as well
In Printer Management advanced settings
You can add a contact from the phone to use this printer
Set as default
See an extensive page of setup and printing options
*After a test print while the computer was off the document did not print and the printer appeared offline until approx. 4 min after computer was rebooted, then the document printed automatically.
Also if a document does not print, the troubleshooting guide on the phone suggested logging out of Google Chrome Cloud Print but I was unable to find that option it was suggesting (unable to log out)
To completely finish adding any additional Google Chrome accounts that wish to share this printer using the suggestion in step 10, you must log into the email that was added and select ADD PRINTER from within the email that was sent for the confirmation and follow the link and instructions on how to do this from your email.
Google Chrome and Google Drive support Windows, MAC, and Linux
You can also change share options, privacy settings, etc. but if you choose to go with the two-step verification process, you may not be able to add your Google Chrome email account to the app without a 16 digit code generated within Google Chrome Privacy Settings for your app (not recommended)
Now you have the option to also email any document to either the Cloud Print App or HP ePrint from the phone/tablet without actually accessing the app first. Locate the document, press the menu button for more options, select "Send to" and a list of available apps will appear. Choosing Cloud Print or HP ePrint sends the document or photo directly to the "print" function within the apps, instead of opening the app first and then searching for what it is you want to print.
**computer connected to printer must be on**
Requirements: a) Google Chrome, Google Drive, and Cloud Print mobile app b) These steps outline the use of an Android device on the network for setup c) will need the computer connected to the printer to be on at all times d) go to this webpage http://www.google.com/cloudprint/learn/ if you have any more questions.
Available features of Cloud Print App
a. Print all file formats from Google Drive (uploaded or create)
b. Has an internal notepad and drawing tool
c. Prints off all contacts and phone numbers as well as specified text messages
d. The scan option actually just means take a picture
e. Without Cloud Print Pro you get 5 days to test the features of printing Facebook pictures, Drop Box and Schedules before those features are no longer available
Don't forgot to say thanks by giving "Kudos" if I helped solve your problem.
When a solution is found please mark the post that solves your issue.
Every problem has a solution!
This question was solved.
View Solution.This document is to assist others in understanding and troubleshooting Cloud Print. This took me many hours to get setup, troubleshoot, and prepare a document that is simple and easy to understand. These are literally step-by-step instructions on how you could be able to print from any Android device to any printer connected to a computer that has Google Chrome. You would then be able to use the Cloud Print App without having to use HP ePrint to print to any printer connected to any computer (USB or wireless) basically allowing you to print virtually anything from your Android.
Don't forgot to say thanks by giving "Kudos" if I helped solve your problem.
When a solution is found please mark the post that solves your issue.
Every problem has a solution!
Maybe you are looking for
-
How to summarize on multiple cross tabs
Dear Sirs/Madams I have created a report in which I am using 2 queries. For each query I have created a crosstab which looks like this: Crosstab Query 1 Jan 2010 Feb 2010 Keyfigure 1 X1 X2 Keyfigure 2
-
Using BAPI_REQUISITION_CREATE has Error Message ME038 "No direct postings c
I am using BAPI_REQUISITION_CREATE to create PR on Lotus Notes but there are Error Message ME038 "No direct postings can be made to G/L acct. XXXXX in CoCode XXXX". When I created PR in T-code ME51N on SAP, there are not this Error Message . I have c
-
Saving the Control Values on a Front Panel
I am creating a VI in which I have approximately 10 front panel controls that can be changed by a user. Instead of entering the same values over an over again, I would like to provide the user the option to save a set of control values that can then
-
Spotlight/Finder Search not finding files in search
Hello everyone, When I do a search for a file, any file or folder in fact, that exists in any of the system folders or the /library and user/library folders, they NEVER appear in the search results. Could someone please explain to me, for example, wh
-
Removing div with flash/flex from page crushes browser
Hallo to all Flex experts ! For an application based on dojo ( javascript ) we prototype the migration to flex - The application is very big, we already work on it more than 2 years, so we try to make the migration smooth by implementing parts of the