LR3.5 RC Bugs...........

  • 1
  • Problem
  • Updated 8 years ago
Post your bugs here please.
Photo of Geoff Walker

Geoff Walker, Champion

  • 222 Posts
  • 46 Reply Likes

Posted 8 years ago

  • 1
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 386 Reply Likes
Tried to move a file from one folder to another, nothing out of the ordinary that I'm aware of, but Lightroom (3.5 RC 1) crashed. Error Message:

File was missing. (1)
{name}.xmp

Problem signature:
Problem Event Name: APPCRASH
Application Name: lightroom.exe
Application Version: 3.5.0.10
Application Timestamp: 4e4ef0f7
Fault Module Name: CameraRaw.dll
Fault Module Version: 3.5.0.6
Fault Module Timestamp: 4e4ef0c7
Exception Code: c0000005
Exception Offset: 000000000024908f
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: aa2a
Additional Information 2: aa2aaa99aefdbadd4b37795651072bf6
Additional Information 3: ea5a
Additional Information 4: ea5a62db9612d6cfe8620199e68d09a8

PS - The photo was not missing, although the xmp may very well have been missing.

Also, it was actually moved to the target directory, and if I try to import it by folder sync, it is found, but then won't import (since already in catalog in another directory). But there's no error message, just: "No photos found to import" - needs an accurate message -e.g. Photo can not be imported: already in catalog...
Photo of Geoff Walker

Geoff Walker, Champion

  • 222 Posts
  • 46 Reply Likes
Thanks Rob.
Can you check and detail the steps to reproduce this please. That is: OS, what type of file, was there an xmp file or not...............
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 386 Reply Likes
win7/64, NEF, I'm guessing an xmp was expected but was not there to begin with and that's what tripped the trigger. I simply dragged a photo from one folder to another. Standby, and I'll see if I can reproduce.

Huh. - just putting the photo back to where it was caused Lightroom to crash. After restart, I can no longer select the folder containing the offending photo, or Lightroom crashes. I renamed the photo file using explorer, and then I could select the folder after restarting Lightroom. I then removed the missing photo and re-imported the renamed photo and all is well. I then removed the renamed photo, and renamed it back to what it was originally (using Explorer) and re-imported - all is well now.

Not able to reproduce original problem. If I delete the xmp file then move the photo, I get the same error, but Lightroom not crashing.
Photo of Geoff Walker

Geoff Walker, Champion

  • 222 Posts
  • 46 Reply Likes
Thanks for checking and responding but please do check that your issues are reproducible before posting. It saves time all round and especially for the engineers monitoring for bugs.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 386 Reply Likes
I thought Adobe might want to know, whether its reproducible or not.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 386 Reply Likes
Seems like memory leakage is rampant - I've had to restart Lightroom several times now, total memory consumption climbing to 85%+, mostly doing gradients and tone brushes. After exiting Lightroom, total memory consumption dropping to below 40%, of 8GB.
Photo of Geoff Walker

Geoff Walker, Champion

  • 222 Posts
  • 46 Reply Likes
Rob, blanket statements really don't help much. Please provide system details and exact steps to what is not working as expected. Thanks.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 386 Reply Likes
I don't have time right now to dig much deeper into this. If Adobe wants to pursue it, they can take the next step.
Photo of Iliyan Gochev

Iliyan Gochev

  • 1 Post
  • 0 Reply Likes
I just upgraded my Lightroom 3.4.1 to 3.5 RC1 on a 64bit Windows 7, CR2 files.

My Lightroom opened in Library mode and loaded the last image I was working on. I switched to the Develop module and it started loading the settings, but just right before it finished, Lightroom crashed.
I've repeated those steps couple of times with the same image and the result was the same: crash. Then I changed the picture in the Library module and switched to Develop and it loaded just fine and I was able to edit it. Thinking the problem was gone I changed back to the previous picture that always crashed Lightroom and it crashed again. Then I decided to use the quick develop tools in the Library module on the same picture and Lightroom crashed again as soon as I hit the exposure up arrow.

One of the times Lightroom crashed I saved the mini crash dump and I decided to look into it for some insight for where the problem might be:

SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: cameraraw!AgTemperatureTint_load+17c04f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: CameraRaw
IMAGE_NAME: CameraRaw.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 4e4ef0c7
STACK_COMMAND: ~27s; .ecxr ; kb
FAILURE_BUCKET_ID: STRING_DEREFERENCE_c0000005_CameraRaw.dll!AgTemperatureTint_load
BUCKET_ID: X64_APPLICATION_FAULT_STRING_DEREFERENCE_INVALID_POINTER_READ_cameraraw!AgTemperatureTint_load+17c04f


With that info I came to the conclusion that something goes wrong when Lightroom/ Camera Raw tries to load the the development settings for that particular picture and I came with this work-around: When I'm in the Library module I have to use the Reset All button and then I can edit the picture without any problem or crash in the Develop module.
Photo of Becky Sowada

Becky Sowada, Adobe Employee

  • 508 Posts
  • 105 Reply Likes
Iliyan, I'll contact you privately to get the problematic file.
Photo of Jon & Ibe

Jon & Ibe

  • 2 Posts
  • 0 Reply Likes
I've got the same bug.

Lightroom-versie: 3.5 RC [769362]
Besturingssysteem: Windows 7 Business Edition
Versie: 6.1 [7601]
Toepassingsarchitectuur: x64
Systeemarchitectuur: x64
Aantal fysieke processoren: 4
Processorsnelheid: 2,4 GHz
Ingebouwd geheugen: 4094,5 MB
Beschikbaar fysiek geheugen voor Lightroom: 4094,5 MB
Fysiek geheugen gebruikt door Lightroom: 538,8 MB (13,1%)
Virtueel geheugen gebruikt door Lightroom: 577,1 MB
Cachegeheugengrootte: 222,8 MB
Dpi-instelling systeem: 96 dpi
Bureaubladcompositie ingeschakeld: Ja
Schermen: 1) 1680x1050
Serienummer:

Crash happened after applying lens profile. Looking at the file in Library goes fine. Switching to Develop starts loading and then LR crashes.

Restoring the images devolopment settings solves the problem, i can continue to work (develop) on it. After 20+ edits returning to that state causes the crash again.
Photo of Geoff Walker

Geoff Walker, Champion

  • 222 Posts
  • 46 Reply Likes
If you have any doubt about what constitutes an accurate bug report follow the format of this one:
http://feedback.photoshop.com/photosh...
Photo of Hans van Eijsden

Hans van Eijsden

  • 32 Posts
  • 4 Reply Likes
I have some problems with orientation in combination with external editing.

- I import my CR2-files in Lightroom (5D II files, full size, DNG or CR2 doesn't matter)
- I go to Develop
- I right click and do Transform -> Flip Horizontal
- I right click and do Edit In -> Edit In Adobe Photoshop CS 5.1
- In Photoshop, the photo opens upside down and I have to rotate the image 180 degrees, to get it right.

The problem exists in Lightroom < 3.3, 3.4, 3.4.1 but also in 3.5 RC.
A video (sorry for the grey scrambled first seconds) from the february situation of 3.3 is here: https://www.youtube.com/watch?v=UYk4bf...

Specs:
Lightroom version: 3.5 RC [769362]
Version: 10.7 [1]
Application architecture: x64
Physical processor count: 2
Processor speed: 2,4 GHz
Built-in memory: 4096,0 MB
Real memory available to Lightroom: 4096,0 MB
Real memory used by Lightroom: 163,3 MB (3,9%)
Virtual memory used by Lightroom: 2136,1 MB
Memory cache size: 38,6 MB
Displays: 1) 1680x1050

Adobe Photoshop Version: 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch]) x64
Operating System: Mac OS 10.7.1
System architecture: Intel CPU Family:6, Model:23, Stepping:6 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1
Physical processor count: 2
Processor speed: 2400 MHz
Built-in memory: 4096 MB
Free memory: 2337 MB
Memory available to Photoshop: 3680 MB
Memory used by Photoshop: 69 %
Image tile size: 1024K
Image cache levels: 5
OpenGL Drawing: Enabled.
OpenGL Drawing Mode: Basic
OpenGL Allow Normal Mode: False.
OpenGL Allow Advanced Mode: False.
OpenGL Crash File: Not Detected.
OpenGL Allow Old GPUs: Not Detected.
OpenGL Version: 2.1 ATI-7.4.10
Video Card Vendor: ATI Technologies Inc.
Video Card Renderer: ATI Radeon HD 2400 OpenGL Engine
Display: 1
Main Display
Display Depth:= 32
Display Bounds:= top: 0, left: 0, bottom: 1050, right: 1680
Video Renderer ID: 16914947
Video Card Memory: 119 MB
Serial number: 92299707063692191340
Application folder: Macintosh HD:Applications:Adobe Photoshop CS5.1:
Photoshop scratch has async I/O enabled
Scratch volume(s):
Macintosh HD, 232,1G, 63,2G free
Data & Backups, 931,4G, 195,0G free

Camera RAW Plugin: 6.5.0.200
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4709 Posts
  • 1808 Reply Likes
I've seen something similar - can I get you to repost this as a separate bug report please, as it affects all 3.x builds and will be easier to track separately. Thanks!
Photo of Hans van Eijsden

Hans van Eijsden

  • 32 Posts
  • 4 Reply Likes
Done, thanks to you! :)
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4709 Posts
  • 1808 Reply Likes
Brilliant, thanks Hans. I'll try to make sure I update your new thread when I see the bugbase updated.
Photo of John Pane

John Pane

  • 5 Posts
  • 0 Reply Likes
Reproducible bug in RC 3.5 Mac. This bug existed in earlier versions.

1. Go to develop module.
2. Make any edit to photo (Edit 1).
3. Adjust a slider to make a second edit. (Edit 2). Do not release the slider.
4. Hit command-Z (undo).

I would expect this to undo Edit 2 (or to do so as soon as I release the mouse). However, the only effect of the undo is to permanently remove Edit 1 from the History. The effects of Edit 1 and Edit 2 remain. Redo is not available.

Another undo removes Edit 2.

At this point, Edit 1 is still in effect, cannot be undone, and cannot be seen in History.

John
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4732 Posts
  • 1825 Reply Likes
Can I get you to repost this as a separate bug report please, as it affects all 3.x builds and will be easier to track separately. I've seen something similar, where an export is running and an undo at the wrong moment will just remove the 'export' history state instead of the mistaken action. Thanks!
Photo of John Pane

John Pane

  • 5 Posts
  • 0 Reply Likes
No you cannot...feel free to DIY.

If the LR team wants bug reports and feedback, they need to streamline the process.

On the LR 3.5 RC page, it says, "If you experience an issue with this release candidate, please report it in the bug report form." But the bug report form does not accept feedback about Lightroom. Instead it refers you to "Photoshop Family product Feedback Site on Photoshop.com"

When I posted the bug report there, I was told "John, post your bug here. (http://feedback.photoshop.com/photosh....

Now, when I did so, you are telling me to post it somewhere else!

Sorry, I'm done. Bye.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4732 Posts
  • 1825 Reply Likes
No problem John, I'll be very pleased to separate the bug report off myself. I simply thought you might like to be able to track the progress, which is easier to do on ones own reports.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4732 Posts
  • 1825 Reply Likes
Bugbase 2940547
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4737 Posts
  • 1828 Reply Likes
Just to clarify, can we just use this thread for bugs that are NEW to the 3.5rc please?

Bugs that affected previous builds too will be better as separate threads, as their bugbase numbers can be more easily tracked than they can in one long thread.

If you have a 3.5 RC bug with clearly reproducible steps, that would also be better as a separate thread, so it doesn't get lost in the more general discussion.

This thread will work very nice for 'gut feeling' and 'needle in a haystack' discussions though... ;-)

Thanks!
Photo of LRuserXY

LRuserXY

  • 426 Posts
  • 41 Reply Likes
In 3.5 RC (Win XP 32 Bit), I had some repeated, but not strictly reproducable crashes when starting the import dialog from within the develop module (each time with some hundret photos in the film strip). It never crashed from within the library module. I never noticed that in previous versions. Unfortunately, I have not recorded the crash details :-( ... but I hope this helps anyway.
Photo of Robert Peters

Robert Peters

  • 39 Posts
  • 15 Reply Likes
2011 MacBook Air, 4GB RAM, 128GB SSD; OS X Lion (10.7.1)
Lightroom 3.5RC

Activate the gradient tool. If I select the Exposure value field of the slider, depress the SHIFT key and UPARROW or DOWNARROW the Exposure slider setting changes to +4 or -4. In fact, the only values possible with these key combinations are +4 and -4 no matter what the initial value happened to be.

This only happens if I have selected the value field of the Exposure slider. If I place the pointer over that field without selecting it the key combinations work as expected.
Photo of Becky Sowada

Becky Sowada, Adobe Employee

  • 509 Posts
  • 105 Reply Likes
I've reported this as a bug.
Photo of LRuserXY

LRuserXY

  • 426 Posts
  • 41 Reply Likes
I can reproduce that on windows xp 32 bit. Not sure whether this was already the case in 3.4.x.
Photo of LRuserXY

LRuserXY

  • 426 Posts
  • 41 Reply Likes
I hope this is the right thread here: In the release notes, under fixed issues: "Using the arrow keys to modify image adjustment settings lacked responsiveness.". What exactly does this mean?

In LR 3.5 RC, at least for windows xp 32 bit, value modification by arrow key and by "scrubby sliders" is still not right for the local corrections. Increments by arrow keys are still much to small (e.g. 0.01 for exposure), regardless whether the shift key is pressed or not.

Scrubby sliders move one pixel per ten "mouse cursor pixels" (estimated), and on the other hand, while holding down shift are too fast.

And another issue: For the up/down arrows in the global adjustments (at least for exposure), the shift key for increasing the steps does not work when a local correction panel is open [EDIT: and a gradient or brush pin is selected] [EDIT 2: AND the slider was clicked-on before - very mysterious]. Ok, to clarify: Open brush panel, select a brush pin, click on global exposure slider, use up/down keys: Shift doesn't work. And sometimes, just hovering with up/down keys will not work, too, in this situation. Seems that LR gets the mouse and key events confused when a local correction panel is open.

EDIT 3: Sorry, sorry ;-) New insight: The shift key *generally* does not work for up/down arrows if the slider was clicked-on before. It does *not* matter whether local corrections are open or not.

Edit 4: Same for the ALT key to decrease the increments - does not work when shift key does not work.

Note: As for my previous comment, I am not exactly sure whether these problems were already in 3.4.
Photo of TK

TK

  • 531 Posts
  • 113 Reply Likes
LR 3.5RC, Windows XP, 32-bit.

Grid view scrolling still frequently gets stuck shortly when using the vertical scroll bar. It is not a performance issue as the same or higher scrolling speed can be obtained using the cursor keys without a stuttery response by the grid.

The Alt key still cannot be used in combination with a number key to change the flow of a temporary eraser brush (-> "Temporary eraser brush has no keyboard control"). Is it not very, very easy to add these keyboard mappings? It should be.

The following problem is still present: When switching from the Develop module to "Loupe" view then noise reduction is applied but the image is blurry. The correct sharpening can only be achieved by zooming in to 100% and then zooming out again. This causes a very cumbersome manual set of actions to obtain a proper preview of an image that looks very noise in less then 1:1 magnification in the Develop module.

Switching images in the Develop module might have become faster or not; I didn't measure it. Happy to do so, if someone wants the figures.
Photo of TK

TK

  • 531 Posts
  • 113 Reply Likes
Another bug that has been showing quite frequently since I started using 3.5RC:

Occasionally, after having set up adjustment brush settings, the first brush stroke makes the brush cursor disappear (i.e., it changes into the "magnifying glass" cursor) and the brush settings panels hides. I can continue painting with the brush using the "magnifying glass" cursor, leaving actual strokes behind. After I have finished the stroke, I can invoke the adjustment brush panel again and continue painting with the brush.

I'm pretty sure I've experienced this behaviour with earlier versions already but it never has been this frequent than with 3.5RC. The higher frequency may be related to something else, I don't know. In any event, it's definitely a bug that (still) lives in 3.5RC.
Photo of seb 3ds4

seb 3ds4

  • 3 Posts
  • 0 Reply Likes
LR 3.5RC, Windows Seven 64-bit.

Bug for Update of the information in file with scrool button of the mouse.
Selection of a file.
Click on the "E" key
Click on the "I" key to display the information in the file (the name of file for example).
Click on the arrow keys to move from one image has another, the update is instant.
With the Scroll of the mouse, the information in the file above is posted 2 s, and then update the information.
Photo of John Pane

John Pane

  • 5 Posts
  • 0 Reply Likes
LR 3.5RC Macintosh

I have a Hard Drive publish service, with the destination an AFP file share (Time Capusule disk).

When publishing, Lightroom reports an assertion failure and halts the Publish. Examining the destination folder, I see that it had created a tmp folder and finished writing an image to that folder. Apparently the assertion failure occurred when it was attempting to move the image into the correct place.

I rebooted and the same problem occurred. Then I tried the same action with LR 3.4.1 and it worked fine. Thus, this looks like a new bug in LR 3.5 RC.

John
Photo of Becky Sowada

Becky Sowada, Adobe Employee

  • 509 Posts
  • 105 Reply Likes
Official Response
For tracking and tagging purposes, it would help if unique bugs were reported in their own threads.

This conversation is no longer open for comments or replies.