Adobe Community: Bridge CS6 (64bit) crashes if started as "normal" User (Windows 7 SP1 64bit)

FotoLinse Calculating status...

Currently Being Moderated

Bridge CS6 (64bit) crashes if started as "normal" User (Windows 7 SP1 64bit)

Mar 24, 2012 11:39 PM

Tags: #bridge #crash #bridge_cs6

When starting Bridge CS6 (64bit) from the start menu or the Mini Bridge panel in Photoshop CS6 the application crashes.

If Bridge CS6 is started as "Administrator" it works as it should

The 32bit is not tested as it is not installed.

4079 Views 41 Replies Latest reply: NormanPCN, Apr 25, 2012 2:23 PM

Replies 1 2 Previous Next

Currently Being Moderated

1. Pattie F,

Apr 4, 2012 12:49 AM in reply to FotoLinse

Report

When it crashed, did you copy the crash report to your clipboard? If so, can you post it here?

Just curious, what video card you are using and if you checked to see if it is supported or that the driver is up to date.

I'll also forward this on to the Bridge folks to look at.

Thanks,
Pattie

|
Mark as:
Currently Being Moderated

2. FotoLinse,

Apr 4, 2012 6:46 AM in reply to Pattie F

Report

There is no crash report. Just a Windows-Message-Box, telling me, that the application is not working any more and if I would like to send additional information to Microsoft.

My GFX-Cards are two AMD Radeon 6850HD linked via Crossfire nad my drivers are up to date.

|
Mark as:
Currently Being Moderated

3. NormanPCN,

Apr 4, 2012 9:40 AM in reply to FotoLinse

Report

This happens to me also. It appears to be a bug in Bridge with a stray temp file created in the root folder of the system drive. If that folder is protected, Bridge must be run as administrator. Here is the thread I created on this topic.
http://forums.adobe.com/message/4303312#4303312

-Norman

|
Mark as:
Currently Being Moderated

4. aochenglong,

Apr 5, 2012 7:58 PM in reply to FotoLinse

Report

Hi FotoLinse,
Could you please send a crash dump to me(alonao@adobe.com)? Below is the instruction about how to enable crash dump on Win7.
1.Copy text below (Marked as blue color) to a text editor and save as a file with .reg extension.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps]
"DumpFolder"=hex(2):25,00,4c,00,4f,00,43,00,41,00,4c,00,41,00,50,00,50 ,00,44,\
00,41,00,54,00,41,00,25,00,5c,00,43,00,72,00,61,00,73,00,68,00,44,00, 75,00,\
6d,00,70,00,73,00,00,00
"DumpCount"=dword:00000010
"DumpType"=dword:00000001
"CustomDumpFlags"=dword:00000000

2.And then import the .reg file to the Win7 Registry by double clicking it.

3.Attempt to launch Bridge. Once Bridge crash find the dump file from C:\Users\[username]\AppData\Local\CrashDumps folder.

Any problem please let me know.

Thanks
Adobe Bridge QE
Chenglong

|
Mark as:
Currently Being Moderated

5. aochenglong,

Apr 9, 2012 1:05 AM in reply to FotoLinse

Report

Hi FotoLinse,
I received your crash dump file and investigated it. It looks like same issue as Norman's. Could you please provide following information?
-Did you never launch Bridge?
-Did you change some settings like Norman’s description (Please see http://forums.adobe.com/message/4303312#4303312)?
-Did you install Bridge by administer or not?
-Did you try reinstalling PS to fix this?
-If disable the MMXCore plug-in by removing MMXCore.8BX file from location below, does this still happen?
C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\Plug-Ins\
-Can you paste your System Info here by going to Photoshop Help > System Info menu?

Thanks in advance.

Chenglong

|
Mark as:
Currently Being Moderated

6. FotoLinse,

Apr 9, 2012 1:25 AM in reply to aochenglong

Report

Hi Chenglong,

- I started Bridge several times (also before I created the Crashdump) as administrator. In that case Bridge is starting and works as it is supposed to do

- It is the same here. My system drive is also a tiny SSD and I moved all user profile using NTFS-Junctions to different drives. Also my Camera RAW cache points to a different location (RAID 0 for performance reasons)

- Bridge was installed as user that has granted administrator rights and I accepted the UAC window, that popped up for the installation.

- PS was not reinstalled until now. Should I try to reinstall PS as a solution?

- It also happens if I disable the MMXCore pug-in

- Here is my Systeminfo as requested.

Adobe Photoshop Version: 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00) x64
Operating System: Windows 7 64-bit
Version: 6.1 Service Pack 1
System architecture: Intel CPU Family:6, Model:10, Stepping:7 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, HyperThreading
Physical processor count: 4
Logical processor count: 8
Processor speed: 3400 MHz
Built-in memory: 16289 MB
Free memory: 11614 MB
Memory available to Photoshop: 14684 MB
Memory used by Photoshop: 82 %
Image tile size: 128K
Image cache levels: 4
OpenGL Drawing: Enabled.
OpenGL Drawing Mode: Advanced
OpenGL Allow Normal Mode: True.
OpenGL Allow Advanced Mode: True.
OpenGL Allow Old GPUs: Not Detected.
Video Card Vendor: ATI Technologies Inc.
Video Card Renderer: AMD Radeon HD 6800 Series
Display: 2
Display Bounds:= top: 0, left: 0, bottom: 1200, right: 1920
Display: 1
Display Bounds:= top: 0, left: 1920, bottom: 1200, right: 3520
Video Card Number: 3
Video Card: AMD Radeon HD 6800 Series
OpenCL Unavailable
Driver Version: 8.950.0.0
Driver Date: 20120214000000.000000-000
Video Card Driver: aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,ati umd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdv a,atiumd6a.cap,atitmm64.dll
Video Mode:
Video Card Caption: AMD Radeon HD 6800 Series
Video Card Memory: 1024 MB
Video Rect Texture Size: 16384
Video Card Number: 2
Video Card: Intel(R) HD Graphics Family
OpenCL Unavailable
Driver Version: 8.15.10.2509
Driver Date: 20110831000000.000000-000
Video Card Driver: igdumd64.dll,igd10umd64.dll,igd10umd64.dll,igdumdx32,igd10umd32,igd10 umd32
Video Mode: 1920 x 1200 x 4294967296 Farben
Video Card Caption: Intel(R) HD Graphics Family
Video Card Memory: 1024 MB
Video Rect Texture Size: 16384
Video Card Number: 1
Video Card: AMD Radeon HD 6800 Series
OpenCL Unavailable
Driver Version: 8.950.0.0
Driver Date: 20120214000000.000000-000
Video Card Driver: aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,ati umd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdv a,atiumd6a.cap,atitmm64.dll
Video Mode: 1600 x 1200 x 4294967296 Farben
Video Card Caption: AMD Radeon HD 6800 Series
Video Card Memory: 1024 MB
Video Rect Texture Size: 16384
Serial number: Tryout Version
Application folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\
Temporary file path: E:\Users\willi\AppData\Local\Temp\
Photoshop scratch has async I/O enabled
Scratch volume(s):
F:\, 745,2G, 405,3G free
Required Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Required\
Primary Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Plug-ins\
Additional Plug-ins folder: not set

Installed components:
   A3DLIBS.dll   A3DLIB Dynamic Link Library   9.2.0.112
   ACE.dll   ACE 2012/01/18-15:07:40   66.492997   66.492997
   adbeape.dll   Adobe APE 2012/01/25-10:04:55   66.1025012   66.1025012
   AdobeLinguistic.dll   Adobe Linguisitc Library   6.0.0
   AdobeOwl.dll   Adobe Owl 2012/02/09-16:00:02   4.0.93   66.496052
   AdobePDFL.dll   PDFL 2011/12/12-16:12:37   66.419471   66.419471
   AdobePIP.dll   Adobe Product Improvement Program   6.0.0.1642
   AdobeXMP.dll   Adobe XMP Core 2012/02/06-14:56:27   66.145661   66.145661
   AdobeXMPFiles.dll   Adobe XMP Files 2012/02/06-14:56:27   66.145661   66.145661
   AdobeXMPScript.dll   Adobe XMP Script 2012/02/06-14:56:27   66.145661   66.145661
   adobe_caps.dll   Adobe CAPS   5,0,10,0
   AGM.dll   AGM 2012/01/18-15:07:40   66.492997   66.492997
   ahclient.dll    AdobeHelp Dynamic Link Library   1,7,0,56
   aif_core.dll   AIF   3.0   62.490293
   aif_ocl.dll   AIF   3.0   62.490293
   aif_ogl.dll   AIF   3.0   62.490293
   amtlib.dll   AMTLib (64 Bit)   6.0.0.75 (BuildVersion: 6.0; BuildDate: Mon Jan 16 2012 18:00:00)   1.000000
   ARE.dll   ARE 2012/01/18-15:07:40   66.492997   66.492997
   AXE8SharedExpat.dll   AXE8SharedExpat 2011/12/16-15:10:49   66.26830   66.26830
   AXEDOMCore.dll   AXEDOMCore 2011/12/16-15:10:49   66.26830   66.26830
   Bib.dll   BIB 2012/01/18-15:07:40   66.492997   66.492997
   BIBUtils.dll   BIBUtils 2012/01/18-15:07:40   66.492997   66.492997
   boost_date_time.dll   DVA Product   6.0.0
   boost_signals.dll   DVA Product   6.0.0
   boost_system.dll   DVA Product   6.0.0
   boost_threads.dll   DVA Product   6.0.0
   cg.dll   NVIDIA Cg Runtime   3.0.00007
   cgGL.dll   NVIDIA Cg Runtime   3.0.00007
   CIT.dll   Adobe CIT   2.0.5.19287   2.0.5.19287
   CoolType.dll   CoolType 2012/01/18-15:07:40   66.492997   66.492997
   data_flow.dll   AIF   3.0   62.490293
   dvaaudiodevice.dll   DVA Product   6.0.0
   dvacore.dll   DVA Product   6.0.0
   dvamarshal.dll   DVA Product   6.0.0
   dvamediatypes.dll   DVA Product   6.0.0
   dvaplayer.dll   DVA Product   6.0.0
   dvatransport.dll   DVA Product   6.0.0
   dvaunittesting.dll   DVA Product   6.0.0
   dynamiclink.dll   DVA Product   6.0.0
   ExtendScript.dll   ExtendScript 2011/12/14-15:08:46   66.490082   66.490082
   FileInfo.dll   Adobe XMP FileInfo 2012/01/17-15:11:19   66.145433   66.145433
   filter_graph.dll   AIF   3.0   62.490293
   hydra_filters.dll   AIF   3.0   62.490293
   icucnv40.dll   International Components for Unicode 2011/11/15-16:30:22    Build gtlib_3.0.16615
   icudt40.dll   International Components for Unicode 2011/11/15-16:30:22    Build gtlib_3.0.16615
   image_compiler.dll   AIF   3.0   62.490293
   image_flow.dll   AIF   3.0   62.490293
   image_runtime.dll   AIF   3.0   62.490293
   JP2KLib.dll   JP2KLib 2011/12/12-16:12:37   66.236923   66.236923
   libifcoremd.dll   Intel(r) Visual Fortran Compiler   10.0 (Update A)
   libmmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler   10.0
   LogSession.dll   LogSession   2.1.2.1640
   mediacoreif.dll   DVA Product   6.0.0
   MPS.dll   MPS 2012/02/03-10:33:13   66.495174   66.495174
   msvcm80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcm90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   msvcp100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1
   msvcp80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcp90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   msvcr100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1
   msvcr80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcr90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   pdfsettings.dll   Adobe PDFSettings   1.04
   Photoshop.dll   Adobe Photoshop CS6   CS6
   Plugin.dll   Adobe Photoshop CS6   CS6
   PlugPlug.dll   Adobe(R) CSXS PlugPlug Standard Dll (64 bit)   3.0.0.383
   PSArt.dll   Adobe Photoshop CS6   CS6
   PSViews.dll   Adobe Photoshop CS6   CS6
   SCCore.dll   ScCore 2011/12/14-15:08:46   66.490082   66.490082
   ScriptUIFlex.dll   ScriptUIFlex 2011/12/14-15:08:46   66.490082   66.490082
   tbb.dll   Intel(R) Threading Building Blocks for Windows   3, 0, 2010, 0406
   tbbmalloc.dll   Intel(R) Threading Building Blocks for Windows   3, 0, 2010, 0406
   TfFontMgr.dll   FontMgr   9.3.0.113
   TfKernel.dll   Kernel   9.3.0.113
   TFKGEOM.dll   Kernel Geom   9.3.0.113
   TFUGEOM.dll   Adobe, UGeom©   9.3.0.113
   updaternotifications.dll   Adobe Updater Notifications Library   6.0.0.24 (BuildVersion: 1.0; BuildDate: BUILDDATETIME)   6.0.0.24
   WRServices.dll   WRServices Friday January 27 2012 13:22:12   Build 0.17112   0.17112
   wu3d.dll   U3D Writer   9.3.0.113

Required plug-ins:

   3D Studio 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Accented Edges 13.0
   Adaptive Wide Angle 13.0
   ADM 3.11x01
   Angled Strokes 13.0
   Average 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Bas Relief 13.0
   BMP 13.0
   Camera Raw 7.0
   Chalk & Charcoal 13.0
   Charcoal 13.0
   Chrome 13.0
   Cineon 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Clouds 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Collada 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Color Halftone 13.0
   Colored Pencil 13.0
   CompuServe GIF 13.0
   Conté Crayon 13.0
   Craquelure 13.0
   Crop and Straighten Photos 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Crop and Straighten Photos Filter 13.0
   Crosshatch 13.0
   Crystallize 13.0
   Cutout 13.0
   Dark Strokes 13.0
   De-Interlace 13.0
   Dicom 13.0
   Difference Clouds 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Diffuse Glow 13.0
   Displace 13.0
   Dry Brush 13.0
   Eazel Acquire 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Embed Watermark 4.0
   Entropy 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Extrude 13.0
   FastCore Routines 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Fibers 13.0
   Film Grain 13.0
   Filter Gallery 13.0
   Flash 3D 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Fresco 13.0
   Glass 13.0
   Glowing Edges 13.0
   Google Earth 4 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Grain 13.0
   Graphic Pen 13.0
   Halftone Pattern 13.0
   HDRMergeUI 13.0
   IFF Format 13.0
   Ink Outlines 13.0
   JPEG 2000 13.0
   Kurtosis 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Lens Blur 13.0
   Lens Correction 13.0
   Lens Flare 13.0
   Liquify 13.0
   Matlab Operation 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Maximum 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Mean 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Measurement Core 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Median 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Mezzotint 13.0
   Minimum 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   MMXCore Routines 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Mosaic Tiles 13.0
   Multiprocessor Support 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Neon Glow 13.0
   Note Paper 13.0
   NTSC Colors 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Ocean Ripple 13.0
   Oil Paint 13.0
   OpenEXR 13.0
   Paint Daubs 13.0
   Palette Knife 13.0
   Patchwork 13.0
   Paths to Illustrator 13.0
   PCX 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Photocopy 13.0
   Photoshop 3D Engine 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Picture Package Filter 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Pinch 13.0
   Pixar 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Plaster 13.0
   Plastic Wrap 13.0
   PNG 13.0
   Pointillize 13.0
   Polar Coordinates 13.0
   Portable Bit Map 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Poster Edges 13.0
   Radial Blur 13.0
   Radiance 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Range 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Read Watermark 4.0
   Reticulation 13.0
   Ripple 13.0
   Rough Pastels 13.0
   Save for Web 13.0
   ScriptingSupport 13.0
   Shear 13.0
   Skewness 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Smart Blur 13.0
   Smudge Stick 13.0
   Solarize 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Spatter 13.0
   Spherize 13.0
   Sponge 13.0
   Sprayed Strokes 13.0
   Stained Glass 13.0
   Stamp 13.0
   Standard Deviation 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Sumi-e 13.0
   Summation 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Targa 13.0
   Texturizer 13.0
   Tiles 13.0
   Torn Edges 13.0
   Twirl 13.0
   U3D 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Underpainting 13.0
   Vanishing Point 13.0
   Variance 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Variations 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Water Paper 13.0
   Watercolor 13.0
   Wave 13.0
   Wavefront|OBJ 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   WIA Support 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   Wind 13.0
   Wireless Bitmap 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
   ZigZag 13.0

Optional and third party plug-ins: NONE

Plug-ins that failed to load: NONE
Flash:
   Mini Bridge
   Kuler
Installed TWAIN devices: NONE

|
Mark as:
Currently Being Moderated

7. aochenglong,

Apr 12, 2012 3:29 AM in reply to FotoLinse

Report

Hi FotoLinse,
Can you let me know how did you apply a NTFS-Junction? like what cmd did you use? which folders did you link to other drives?

And have you tried resetting Bridge prefrences (Press ctrl key on launch)?

Thanks
Chenglong

|
Mark as:
Currently Being Moderated

8. FotoLinse,

Apr 12, 2012 4:21 AM in reply to aochenglong

Report

Hi Chenglong,

the NTFS-Junction was created using the commandline-command "mklink /J E:\Users c:\Users".
Only c:\users is linked to another drive. The corresponding line of my directory listing looks like:

04.04.2011 14:47 <VERBINDUNG> Users [E:\Users]

where <VERBINDUNG> means <JUNCTION>

Resetting Bridge-Preferences (using ctrl-key) does not change anything.

regards
FotoLinse

|
Mark as:
Currently Being Moderated

9. aochenglong,

Apr 13, 2012 2:54 AM in reply to FotoLinse

Report

I think you mean command "mklink /J C:\Users E:\Users", because C:\Users is the souce but not the target. When I ran the command, it failed with an error "Cannot create a file when that file already existes". How did you do that?

Anyway, can you try removing the junction and see whether the issue is fixed? And can you set the Camera RAW cache location to default and see what happens?

I still can't reproduce the issue on my side. Do you mind if we do a connect session through www.adobeconnect.com to investigate the issue on your machine?

Thanks
Chenglong

|
Mark as:
Currently Being Moderated

10. FotoLinse,

Apr 13, 2012 2:02 PM in reply to aochenglong

Report

Hi Chenglong,

no - my command was correct because the data resides on e:\users and the target (place where just the link will be placed) is c:\users.
To create the NTFS-junction I booted the system in rescue mode with the original DVD and copied the content of C:\users to E:\users preserving all rights and ownership (robocopy c:\users e:\users /mir /xj /copyall) . After that I renamed c:\users to some backup name and then created the junction. After I got everything in place I deleted the backup folder.
Usually this is absolutely transparent to any application as it is behaving like a hard link in linux/unix.
Unfortunately I cannot remove the junction, as I would have to move the content of my user directory back to the SSD and there is not enough space to do so.

Of course we may do a connect session. The place where I am living is UTC+2.
Monday UTC 1430 would be fine. Of course you are welcome to propose another time.

regards

|
Mark as:
20,993 posts
Dec 23, 2006

Currently Being Moderated

11. Noel Carboni,

Apr 13, 2012 2:05 PM in reply to FotoLinse

Report

I'm not being critical of your methods or choices, FotoLinse, but these kind of workaround problems are why I'm presently putting together a 2 TB RAID array of SSDs for drive C:.

-Noel

|
Mark as:
20,993 posts
Dec 23, 2006

Currently Being Moderated

12. Noel Carboni,

Apr 13, 2012 2:06 PM in reply to FotoLinse

Report

What are your permissions on the junction itself?

Does your USER NAME have Full Control permissions?

-Noel

|
Mark as:
Currently Being Moderated

13. FotoLinse,

Apr 13, 2012 2:41 PM in reply to Noel Carboni

Report

Hi Noel,
thanks for your comment.

The junction has the same permissions as the originating folder had. Of course does a single user not have full control permissions on the c:\users-Folder but of course to the c:\users\[Username] folder. Or in my case to e:\users\[Username].

I compared the permissions on my Laptops c:\users and my desktop c:\users (junction) - they are absolutely identical. And of course they have to, because the junction has the same permissions as the source-directory.
If required I will do an instllation of CS6 on my laptop to see if it behaves the same way.

BTW why is a junction (hard link) a work around. This is done for decades in other systems and is everything else than a workaround. (I also could have mounted another NTFS into c:\users with the same result)

gn8

|
Mark as:
20,993 posts
Dec 23, 2006

Currently Being Moderated

14. Noel Carboni,

Apr 13, 2012 3:12 PM in reply to FotoLinse

Report

Admittedly, I was thinking more about the workaround where one changes the locations known to Windows in the registry so that it actually says E:\Users instead of C:\Users (for example) when I made that statement. But having to put files that want to be on C: elsewhere to keep from overflowing a too-small SSD is most definitely a workaround.

I think you kind of answered your own question with this issue with Bridge. While it's a perfectly great idea, that really should work, it never *quite* works the same as if it was a real directory on a drive C:. Too many software developers take shortcuts or find system calls/algorithms that don't quite parse things out properly. You can imagine it's not nearly as well tested as the mainstream.

Windows is full of things that *almost* work properly, and "going with the flow" (e.g., having everything on C:) is more likely to work than any other means. Probably this throws back to the software's distant origins. All I know is that most everything works better if you allow it to go where it really wants to go, and that I hear from time to time about people with SSDs having unexpected issues.

I'm a career software engineer and Windows expert, by the way.

-Noel

|
Mark as:
Currently Being Moderated

15. FotoLinse,

Apr 14, 2012 10:01 AM in reply to Noel Carboni

Report

In fact the junction seems to the problem for Bridge CS6 64bit. After deep investigation and fixing some minor issues regarding rights and reinstalling Photoshop CS6 64bit the problem is still not solved.
I did another test installation on my Laptop computer without any junctions and Bridge works as it is supposed to.

The combination of SSD and HDD as I have it in my system was planed before I installed Windows and it worked for any application (including Photoshop / Bridge CS5 64bit, Lightroom 3, Lightroom 4) for more than one and a half year now. So I tend to say that there is something not working in Bridge CS6 64bit as it should.

cheers have a nice weekend

|
Mark as:
Currently Being Moderated

16. NormanPCN,

Apr 14, 2012 10:12 AM in reply to FotoLinse

Report

I never used Junctions and I have the same symptoms as others. I do have an SSD + HD setup.

I moved the documents, pictures, videos, downloads folders via the standard Windows 7 UI mechanism. All other account stuf is still in the default location.

I opened the account view/folder and right click for properties on each of the specificed library folder(s) and change the location via the location tab in the dialog.

-Norman

|
Mark as:
Currently Being Moderated

17. aochenglong,

Apr 15, 2012 8:40 PM in reply to FotoLinse

Report

Hi FotoLinse,
After reading your new post, some questions come to my mind.
-Did you also run Bridge in a non-admin account on your Laptop computer? You said this worked fine.
-If you create a new “normal” user account on the machine that has the problem, can Bridge launch?
-Do you have any anti-virus software installed? If yes, can you try disabling it and see if this is fixed?

I’m in Beijing (UTC + 8), Your 14:30 is my 8:30am. It’s OK for me. How about tomorrow morning my time (April 17)?

Thanks
Chenglong

|
Mark as:
Currently Being Moderated

18. aochenglong,

Apr 16, 2012 1:27 AM in reply to FotoLinse

Report

Hi FotoLinse,
I reproduced this issue by a trick on my machine. I made the temp folder(C:\Users\<username>\AppData\Local\Temp) write-protected for current user, then Bridge crashed after launching for a while. The crash dump is similar to yours.

Can you run command "set temp" in the Command Line window to see what it outputs? And make sure current user has write pemission for that folder, then see if the issue is fixed.

Chenglong

|
Mark as:
Currently Being Moderated

19. FotoLinse,

Apr 16, 2012 9:07 AM in reply to aochenglong

Report

The accounts I used on my laptop computer as well as on my desktop are administrative accounts in Windows 7 with UAC activated. Administrative rights are available if required, but not all the time.
Today I created another user account on my desktop and that user was able to launch Bridge CS6 64bit.
I checked the rights of all my Temp-Folders in use and the user having problems launching bridge has full access to them.

Regarding your time proposal there seems something wrong. In Bejing it is 6 hours later than in central europe. So my 1430 UTC (1630 local) should be your 2230. At the moment it is not possible for me to be available on Workdays (Mo. - Fr.) in the morning. The earliest possible time might be 1300 UTC (9pm for you).

FotoLinse

|
Mark as:
20,993 posts
Dec 23, 2006

Currently Being Moderated

20. Noel Carboni,

Apr 16, 2012 9:11 AM in reply to FotoLinse

Report

FotoLinse wrote:

Administrative rights are available if required, but not all the time.

I think what Chenglong may be asking, though, is whether your username specifically has Full Control access to your TEMP folder. You almost sort of said that, but a difference in specifics could be important.

If it works when run As Administrator there's a pretty good chance there's a permissions problem somewhere.

-Noel

|
Mark as:
Currently Being Moderated

21. FotoLinse,

Apr 16, 2012 10:25 AM in reply to Noel Carboni

Report

That is what I also answered. I just mentioned for completeness, what kind of user account I use.
The user having problems with Bridge CS6 has full access to any TEMP folders shown by the console command "set TEMP". So this is independent of granted admin rights.

regards
FotoLinse

|
Mark as:
20,993 posts
Dec 23, 2006

Currently Being Moderated

22. Noel Carboni,

Apr 16, 2012 1:04 PM in reply to FotoLinse

Report

Is there a reason you're unwilling to disable UAC? Just curious. You sound like you know what you're doing.

-Noel

|
Mark as:
Currently Being Moderated

23. aochenglong,

Apr 16, 2012 11:44 PM in reply to FotoLinse

Report

To test whether the user account really has full access to the temp folder, there is an easy way. You can try manually creating a file or folder under the temp folder and see whether you can do it without any authorization.

Since I reproduced the same crash we can postpone the connect session.

In addition, you might need to check the "tmp" variable by running command "set tmp" .

Chenglong

|
Mark as:
Currently Being Moderated

24. FotoLinse,

Apr 17, 2012 12:43 AM in reply to aochenglong

Report

Hello Chenglong,

i did your test and it confirmed my first statement. The user has full access to the temp foleders reported by the command "set tmp" and "set temp" (both are the same) without any authorization needs.

greets
FotoLinse

|
Mark as:
Currently Being Moderated

25. aochenglong,

Apr 17, 2012 1:48 AM in reply to FotoLinse

Report

Hi FotoLinse,
It seems we really need a connect session. How about tomorrow evening 9pm my time? It should be your 3pm, right?

Chenglong

|
Mark as:
Currently Being Moderated

26. FotoLinse,

Apr 17, 2012 2:21 AM in reply to aochenglong

Report

Hello Chenglong,

this should be possible. If there is nothing special in my office job I will be available. Do you provide a adobeconnect-room?

FotoLinse

|
Mark as:
Currently Being Moderated

27. aochenglong,

Apr 17, 2012 2:34 AM in reply to FotoLinse

Report

Hi FotoLinse,
Yes, I'll send you detail by email later.

Chenglong

|
Mark as:
Currently Being Moderated

28. aochenglong,

Apr 17, 2012 9:08 AM in reply to FotoLinse

Report

Hi Fotolinse,
Sorry, I will be unable to come to office tomorrow. Can we move the meeting to Thursday my 9pm, your 3pm? Any concern please let me know or email me.

Chenglong

|
Mark as:
Currently Being Moderated

29. FotoLinse,

Apr 17, 2012 9:17 AM in reply to aochenglong

Report

Hi Chenglong,
Thursday 3pm (your 9pm) is also ok for me.

FotoLinse

|
Mark as:
Currently Being Moderated

30. aochenglong,

Apr 23, 2012 11:40 PM in reply to FotoLinse

Report

After more investigation, I think I reproduced the issue. Here is my steps to reproduce the bug.
0) Turn on UAC of Windows.
1) Chang the user temp folder to a new location(Make sure the new temp folder location doesn’t exist), say D:\Temp.
3) Launch Bridge 64-bit/32-bit and browse some images. Bridge will crash.
4) Then I manually create the folder D:\Temp, but Bridge still crashes.
5) If I run Bridge as administrator, it always generates a temp file “Photoshop Tempxxxxxx” under the root of C drive. The phenomena is matching yours. But, by default, a user has no write permission for the root of C drive if UAC is on. So this might be the root cause.

Photoshop also has same issue, but it will pop up an error on launch, not crash.

Did you do similar thing as mine?

Chenglong

|
Mark as:
Currently Being Moderated

31. FotoLinse,

Apr 24, 2012 8:26 AM in reply to aochenglong

Report

Hello Chenglong,

that is exactly what I did here (except step 1 - I moved the Temp-Folder and it existed before the first start of Bridge/Photoshop CS6). And the behaviour is the same.
Also Photoshop tried to create a temp-file at the first start. But the location changed by editing the "Scratch Drive"-Option within Photoshop.

Greetings

FotoLinse

|
Mark as:
Currently Being Moderated

32. aochenglong,

Apr 24, 2012 10:47 PM in reply to FotoLinse

Report

As far as I know, there are following workarounds:
-Run Bridge as administrator.
-Trun off UAC.
-Reset user temp folder to default location or create a new user account.

We'll consider fixing this in dot release.

Chenglong

|
Mark as:
20,993 posts
Dec 23, 2006

Currently Being Moderated

33. Noel Carboni,

Apr 25, 2012 5:21 AM in reply to FotoLinse

Report

FotoLinse, as of yesterday I have gotten my SSD RAID0 system completely set up. OS, apps, and data all at SSD speed and I still have 1.2 TB free on drive C:. No reason to relocate anything. In fact, the ability to open temporary files on the zero-latency SSD array (and use it for scratch, swap space, etc.) speeds everything up markedly. No worry that workarounds to keep the usage of C: small by moving things elsewhere are going to cause problems.

Another option for you might be a hybrid drive.

-Noel

|
Mark as:
Currently Being Moderated

34. FotoLinse,

Apr 25, 2012 7:33 AM in reply to Noel Carboni

Report

Noel,
That is no help for me or Adobe to solve the drive C: issue you also encountered.
Hardlinks are transparent in the filesystem and are no tweaks.
As the problem is tracked down also on my system it is the fact, that the software tried to create files at the systems drive root directory where normal users have no write permission (for some good reasons).

The reason for me to relocate things away from the SSD to another drive was not the size of the disk but the fact, that permanent write access will kill SSDs (especially the older ones as I have it).

For size I have a big SAS storage system (Throughput up to 600MB/s on disk) where my data is located and gets backed up automatically. For fast work I prefer to rely on RAM instead of caching partitions.
Also I personally would not use a RAID0 system for data (failure probabiliity is raising proportional to the number of discs in the RAID0).

As you can see, there is no need for me to change my system as it is working well. Also the hardlinks (NTFS-junctions) work as they are supposed to do. Not one piece of software in the last one and a half years had a problem with that setup and as written above Bridge CS6 also has not, because the failure is something else (the same as it is on your system).

FotoLinse

P.S. Above you asked me why I did not turn off UAC. The answer is that UAC prevents the user (or software like Bridge CS6) from accidentially doing write access to ares where you usually should not work on except you know what you are doing.
Usually I know what I do, but I do not always know what different software does - that's the reason for me.

Message was edited by: FotoLinse

|
Mark as:
Currently Being Moderated

35. NormanPCN,

Apr 25, 2012 8:33 AM in reply to aochenglong

Report

Amazing all these "workarounds" except for Adobe FYS (fix your stuff).

Tip for the Adobe developers. Check out the GetTempPath API. 100% you will never have the problems you are having if you simply use the value returned by this API. I bet they are using this API, but then making a simple operation complicated with who knows what logic, modifying the path, after fetching the temp files directory from the system. No way this API ever returns C:\.

By default on Windows 7, TEMP is set to "%USERPROFILE%\AppData\Local\Temp". I have mine set to "D:\TEMP". How on earth could Adobe, or any software, care what the directory path is. It is really none of the applications business.

JUST USE IT.
DON'T F WITH IT.

Symbolic links (junctions) are a normal part of the system and are transparent. If an app does not work with them, IT IS BROKEN. FYS.
I have not used symbols links, and Bridge is just as broken, so this seems not to be the problem with Bridge.

Hey Adobe, join the rest of the world, and create your temp files where GetTempPath tells you to.

My two cents.

-Norman

|
Mark as:
20,993 posts
Dec 23, 2006

Currently Being Moderated

36. Noel Carboni,

Apr 25, 2012 9:13 AM in reply to FotoLinse

Report

FotoLinse wrote:

Noel,
That is no help for me or Adobe to solve the drive C: issue you also encountered.

Remind me again, what drive C: issue did I also encounter? Literally, I don't have the problems you're describing as I have been using a 2 TB C: drive for a long while. I've just upgraded to faster storage lately.

I'm not trying to heckle, really, just facing the reality that applications don't deal with data relocation workarounds very well. Adobe's application may be less integrated with Windows than most because they also have to support running on Macintosh systems.

And NOTHING deals with UAC very well. It's the stupidest, most hacked-in bit of software work Microsoft has ever done, and using it invites more problems than it avoids.

-Noel

|
Mark as:
Currently Being Moderated

37. FotoLinse,

Apr 25, 2012 9:33 AM in reply to Noel Carboni

Report

Sorry, I mixed-up your user name. Just remove the part regarding your non-existing drive C.-issue.
The rest of my post stays untouched.
The information of upgrading your storage does not help anyone in solving the behaviour encounterd by me and other users.
Disabling UAC allows Bridge to write Temp data at a location where it is not supposed to do. Why should I allow that?
Normans Post above says absolutely everything to be said.

FotoLinse

|
Mark as:
20,993 posts
Dec 23, 2006

Currently Being Moderated

38. Noel Carboni,

Apr 25, 2012 10:23 AM in reply to FotoLinse

Report

FotoLinse wrote:

write Temp data at a location where it is not supposed to do

Impossible to define. "Supposed to" could have many meanings... What Microsoft thinks isn't necessarily gospel, especially if you want things to just work.

That said, though it's pretty clear where Windows wants applications to write temporary files, is it even certain yet that this is a temporary file location issue? It doesn't seem cut and dried.

But I certainly don't want to argue or dilute the point that the software's not working for you. It really should be!

If / when Adobe fails to fix it, then we can talk about how to best work around the application shortcomings.

-Noel

|
Mark as:
Currently Being Moderated

39. NormanPCN,

Apr 25, 2012 11:04 AM in reply to Noel Carboni

Report

Easy to define, and in actual fact is defined since a system API exists. "Supposed to" is the convention of the system in question. In Windows, the API is just using previous defacto conventions for temp files. AKA The TEMP environment variable. This was a defacto standard in the DOS world and Windows dates back to that era. For example, Single Unix has a defacto of TMPDIR.

There is one GOD for a system, and that is the user. The user defines where their files go. It is their HD and their organization. Temp files are not actual user named files, but they are created on the users behalf while working on their actual files. The application has control of how it organizes its files in its app folder, but the usere control where that app folder goes. In other words, I am not saying the user has total control of every file location in the OS and APPs.

Windows does choose a default location of special folders, if the user decides to not make a choice, and this default has changed from version to version. Windows allows and respects users abilities to change location(s) of "special folders" through the GUI, for the most part.

What exactly is causing Bridge to crash only Adobe knows. What is clear is that Bridge is creating temp file(s) in the root directory of the system drive, AKA C:\. Just exactly where they got that garbage only they know. It is not the system temp convention and Bridge has no application preferences convention for temp files.

Adobe grew up on not protected file systems like Windows and the Mac, where create a file where the hell you want will work. If they grew up in the Unix world stuff like this would fail as Unix has always been much like UAC protections. Just try to create a file in the root folder on a Unix system. It will fail since only "root" has access to that, much like authenticated users only have access to the root folder of the system drive, C:.

Just look at Photoshop's scratch disk options on Windows. They default to creating scratch in the root of the C: drive. In past eras, not a problem. In the UAC era, it is a problem. Photoshop just plain crashes with no message. The average Joe is screwed. How are they to know to run PS as admin and change the preferences for scratch so PS can run as a normal user. If Adobe were smart, they would notice a access violation trying to create a critical and necessary temp file, scratch, and pop up a dialog stating as such and give the user the option to change the scratch location. The real point is why do they default scratch to the root folders? and why do they default to something other than the TEMP folder of the system which will be writable. Something you cannot say for root folders of drives. Windows defaults to protecting C:, but for exsample, I, as God of my machine, have the right to make D:\ restricted to whom ever I choose. The point being here, that PS should have me specify a file specification/folder and not just a drive for scratch. Basically it should be treated like a magic cookie. At that level, if it does not work, then it is the users fault.

|
Mark as: