Reproducible crash on Win 7 in Loupe View

This morning I started the beta version again, showing me the grid view.
I then double clicked on a photograph and while rendering the view (with the busy spinning thing showing), the application crashed.
Fortunately, it happens every time I try to view that particular photograph and I have tried not to do anything else until I have a full report.
Attaching the VS 2010 debugger didn't offer much more information, but I can now say the crash happens in CameraRaw.dll (probably).
The output window in VS reads:
First-chance exception at 0x0000000180168ee9 in lightroom.exe: 0xC0000005: Access violation writing location 0x000007fff9b9b0b0.
Unhandled exception at 0x0000000180168ee9 in lightroom.exe: 0xC0000005: Access violation writing location 0x000007fff9b9b0b0.
stack trace:
CameraRaw.dll!0000000180168ee9()
[Frames below may be incorrect and/or missing, no symbols loaded for CameraRaw.dll]
CameraRaw.dll!00000001801d46ec()
CameraRaw.dll!00000001801da142()
CameraRaw.dll!00000001802c4c33()
CameraRaw.dll!000000018019fbfd()
CameraRaw.dll!000000018019f8b6()
CameraRaw.dll!00000001802fadc1()
>
msvcr100.dll!_callthreadstartex() Line 314 + 0xd bytes
C
msvcr100.dll!_threadstartex(void * ptd=0x0000000000000000) Line 292 + 0x5 bytes
C
kernel32.dll!BaseThreadInitThunk() + 0xd bytes
ntdll.dll!RtlUserThreadStart() + 0x21 bytes
More information:
- Windows 7 Pro SP 1 (64 bit)
- Intel Core 2 Duo E8500, 4GB RAW, no SSD, ATI Radeo HD 3450 - Dell Optiplex
- Lightroom 4 beta, installed yesterday morning (LR 3.6 already installed)
- New blank-slate catalog, then imported a few files from different cameras by copying them
What I can provide by uploading and sending a link via email to a dev:
- Info I got from VS 2010 as text files (stack trace, threads and the output window)
- The 3 files that Windows would like to send to Microsoft
- The entire catalog with the particular file (but without the other files, but crash occurs even if they are missing)
- All the settings in the user folder (Local and Roaming)
- A limited CameraRaw cache that only contains the files I have added to the blank-slate LR4 catalog yesterday.
- Upon specific request, I might be able to upload the other 400MB of the cache somewhere.
The whole 7zip archive would be 36MB only.
I really hope this would reproduce the crash on another computer (can't try right now by myself).

Here I am, writing the answer from scratch again because I clicked on "Reply to original post" (which is in the lower left corner of the text window...) instead of "Add Reply".
Only happened the third time in three days.
Victoria, 400 threads in 4 days, that is maniac ^^
But sorry, my computer should call home as little as possible.
So the crash reports stay here in this forum, available to any dev upon request.
jbm007, as for the registry clean: I hope you are joking.
Please note that I'm not trying to fix a problem directly but rather nail a bug. I know too well how difficult bug tracking can be if you cannot reproduce it.

Similar Messages

Loupe View Malfunction

I know I posted this before, but I didn't get an answer which adequately explained my problem.
I did a Batch rename of 179 photos of 300 in a folder; the others were rejected. Then, I exported them as reduced sized jpegs. I had other programs open, Browser and Photoshop Elements. After the process was finished, I lost the ability to see photos in the loupe view. I could see the grid, or even compare mode. When I tried to see a single photo in the loupe, I either got a blank screen, or it stayed in the grid mode. This has happened several other times.
I am running a 4200+ AMD Athlon 64X2 Dual Core, with 2G of Ram. HD has over 125GB of space left.
Video is onboard ATI Radeon Express 200 Series.
Samsung Syncmaster 206 BW 21Inch Widescreen 1680 X 1050
Seems to me that what I've asked of LR and my system should be properly handled by my system. Unless, I have a bug somewhere or an improper setting.

Have you rendered 1:1 previews in advance, since you are viewing 1:1?
Menu/Library/Previews/Render 1:1. You can do it on a Large Selection. You do not need to rednder for All Photographs.
Don
Don Ricklin, MacBook 1.83Ghz Duo 2 Core running 10.4.10 & Win XP, Pentax *ist D
http://donricklin.blogspot.com/

Grey thumbnail, grey loupe view-- no photograph displayed in library mode

When I import a new batch of photographs my library mode, both in grid and loupe view will not show my new photographs. And not that it just takes a bit of time to load-- the picture will not show, only gray. This has only happened in the last month or so. Previously everything worked well.
To get my pictures showing I have to go to develop mode and view them. The loading is taking considerably longer than it used to as well. I've been into my preference pane and can't see what to do. As per a tutorial I upped my "Camera Raw Cache Settings" to 50 GB. The problem hasn't coincided with this change however. I don't know what is going on but I am frustrated to have all photos load but not show up in Grid or Loupe mode.
Any ideas? I have over 7,000 photos in library. I've validated and checked library and it comes back okay.
Thanks for your help.
My computer is a newer 27" imac so I should have plenty of juice to run the program. Hard drive space isn't an issue as I have a 1TB.

Sounds like a corrupted preview cache. Let's test that theory. Close LR. Find your catalog on your hard drive, and rename the Previews.lrdata or move it to another location - you can delete it later when we know the new one's ok. Now restart LR, go to Grid view, select all and go to Library menu > Previews > Render Standard Previews. Hopefully that'll bring back your previews and if everything looks correct, you can then delete the previous one.

Error message in loupe view

I'm using Lightroom 1.3.1 in Windows XP. Sometimes when I'm looking at pictures in a library using loupe view, instead of seeing an image I see a grey rectangle where the image should be. At the top of the rectangle there is an error message that says "There was an error working with the photo." At the lower left hand corner of the rectangle there is a message written upside down in red letters that says "Error - A2of Memory - B". Once this problem happens I can no longer display images that were previously displayed normally. If I restart Lightroom it goes back to normal. I think this problem is more likely to happen if I am moving through the images rapidly, not giving Lightroom enough time to finish each preview. Is there some way to avoid this, besides going through the images very slowly?

HI friend,
Just check whether the error is due to the custom error message or standard error message.
If its standard then you have done any mistake which has makes the view to exit. If its custom message then it should change after you have changed the message.
If custom message , Just try activating it completely and check again. Goto SE80 and activate the function group and see is it showing any error.
Thanks,
Sri Hari.

Problem with loupe view after upgrade to LR 2.3

Has anyone had any problems similar to this? I could use some help. In the library module when I go to loupe view I don't see the selected photo, instead it gets frozen up or something. For example, if I open up a web browser on top of LR the image of the web browser is stuck in the loupe view. Any help would be greatly appreciated!

Thanks for your reply.
I can try with 1.5 (not installed on the server), but this is from the readme file:
1) To use APEXExport, a JDK of version 1.4 or greater must be used. Additionally, the Oracle JDBC
20 class libraries must be in your CLASSPATH.
So apparently, the JDK requirements didn't change.
Matthias

On my iPad Air Safari crashes and quits when I view a slideshow.

On my iPad Air , Safari crashes and quits when I view a slideshow on an internet site. Sometimes it doesn't crash but the slideshow is freezes. Any idea why?

Try clearing Safari's cache : Settings > Safari > Clear Cookies And Data (Clear Cache on iOS 4) and also Clear History
If that doesn't work then try closing Safari completely and then re-open it : from the home screen (i.e. not with Safari 'open' on-screen) double-click the home button to bring up the taskbar, then press and hold any of the apps on the taskbar for a couple of seconds or so until they start shaking, then press the '-' in the top left of the Safari app to close it, and touch any part of the screen above the taskbar so as to stop the shaking and close the taskbar.
A third option is a reset : press and hold both the sleep and home buttons for about 10 to 15 seconds (ignore the red slider), after which the Apple logo should appear - you won't lose any content, it's the iPad equivalent of a reboot.

Firefox keeps crashing in Win 8.1

I have a new system from HP. I installed firefox two days ago. It works for a while and then keeps crashing in Win 8.1. This usually happens together with a pop up saying something like a script is running, do I want to stop it or continue
Can someone help? What should I do?
fc74f728-060f-4806-be03-49332e1c9616 9/11/2014 7:29 PM
a25641f7-5069-483f-8236-c8d474cf97a5 9/11/2014 7:29 PM
f0af8b44-d9aa-43f5-b936-d230e7839c99 9/11/2014 7:28 PM
3fb1f1b0-712f-4e95-9aa6-e9bfe38286cd 9/11/2014 7:27 PM
4b6b61c4-8768-4e83-bb00-b41caf31bd87 9/11/2014 7:25 PM
2c9064ba-f077-44db-aa02-5db25fa066b1 9/11/2014 7:25 PM
2e029696-eab3-4d16-9522-c400c993ef98 9/11/2014 7:25 PM

Thanks for the help cor-el, much appreciated!

WRT350N + WMP300N = BSOD Crash on Win XP Pro SP2?

Yes, the problem I am having is that with WRT350N + Wireless + WMP300N = BSOD Crash on Win XP Pro SP2.   Really, from what I can tell, WRT350N + Wireless = BSOD Crash on Win XP Pro SP2.   Yes, I know, a router shouldn't be able to crash a computer, PC drivers, PC misconfigurations do.
However, my crashes didn't start happening until I switched to my WRT350N wireless router. Actually, at that time I didn't even have the linksys WMP300N ... it was another wireless card. Now I have the linksys WMP300N, and the crashes still happen.
I updated my driver on my NIC to the latest version two days ago, and at the same time upgraded the firmware on the router to the latest and greatest. You know what that did? Instead of crashing my PC once every day or so I get crashes about 5 mins after I start my PC.
I've tried using the linksys wireless configuration utility, and the Windows zero configuration, still crashes. I've tried Wireless Mixed bode, BG mixed, G only, still crashes.   Different channels, still crashes.   I disabled Symantec Client Security firewall, still crashes. Uninstalled SCS and used windows firewall, still crashes.   Disabled netbios and dynamic DNS registration on my adapter, still crashes.   Disabled wireless QoS on PC and router, still crashes. Tried disabling and enabling (individually) Wireless AP isolation, frame burst, CTS Protection mode, forced 54mbps rate ... still crashes. I have no HD attached to the router. I've disabled UPnP on the router, still crashes.
You know what does fix the crashes? Disabling my wireless adapter. You know what else fixes the crashes?   Connecting to a different wireless router.
I'm completely baffled. Any ideas what I can try? I'm an IT Consultant by trade, and have been working with PCs and networking in a professional capacity for over 8 years, so I have a decent amount of troubleshooting experience.   The BSOD doesn't say much, just equates to a hardware/driver fault ... but no indication what.   My crash dump analysis (full, not just minidump) also provides no data as to what driver).
Thoughts? As much as I hated my former Netgear, I'm about ready to even go back to that....
Edit: My PC is using DHCP, configured as a reserved address.
Message Edited by TroyL on 02-20-2008 07:08 AM

Hello, hopefully I can help you. Some things that resolved my issue were disabling some options in the advanced properties of my NIC (WMP300N) Even if you don't have the same NIC, you should probably have some similar options:
-Manage Wireless Settings = Disabled (note: I disabled this since I'm using Windows to manage the settings)
-Mixed Cell Support = Disabled
-Minimum Power Consumption = Disabled
-Power Save Mode = Disabled
-Wake Up Capabilities = None
-Bluetooth Collaboration = Disabled
-40MHz Intolerant = Disabled
Try disabling those things, and go from there ... good luck . With those settings, I haven't crashed in several months now. I don't know which setting it was fixed it, I haven't been brave enough to go playing with it again ... if it ain't broke, don't fix it, lol.

Detail seen different in Develop view and Loupe view

I recently took some aurora pictures, and was adjusting them to put in a slideshow, and noticed something peculiar, i.e., that the details seen in the Develop module are less than those seen in the Loupe view in the Library. This is true in several pictures. The Develop view (2nd picture) is smoother and shows fewer of the fainter stars than the Loupe view (first picture). I hope it shows in the pictures below, which I created by using the Snipping Tool in Windows.
Why is this the case?
The problem is that the Slideshow results in LR seem to be closer to the Loupe view than the Develop view.
The Exif information is as follows:
and the adjustments I made were:
and
I'm using the LR 2014 v 8.7.1, Camera Raw 8.7.1.
TIA.

Hi Michael:
You're right. When I magnified the view to 100%, the results in the two modules were identical, as you said.
It does, however, raise a practical difficulty for me. With these kinds of long exposure, high ISO pictures, if I zoom in to 1:1, I find it extremely difficult to make any adjustments because the noise is so high. I would basically set all the noise sliders to max, and the details to minimum. However, this results in overadjusting for noise and losing too much detail when the picture is viewed zoomed out to fit on a computer monitor as a slideshow. Usually, this is not a problem, but at the high ISO/long exposures of these pictures, I find it very difficult to work in the develop module at 1:1.

Screen redraw bug when panning in Loupe view at high magnification

I think I've found a bug in Lightroom.
Using the Loupe view at higher than 1:1 magnification and panning whilst zoomed seems to cause screen redraw artifacts. It is most noticable at high zoom (say 11:1) when panning diagonally. The edges being revealed draw incorrectly. Seems to only happen once the 1:1 preview rendering has been completed, initial panning whilst the preview is being rendered looks fine. Zooming out and back in redraws the screen correctly, but subsequent panning still causes artifacts.
I first thought it must be my graphics drivers, but have updated to the latest available driver (version 7.2 21 Feb 2007) for my ATI Radeon 9800 and the problem remains. I have also tried this on my laptop a Sony VAIO VGN-S3HP (with NVidia GeForce 6200 based graphics) with the same problem. Therefore as this happens on both a NVidia and an ATI card I can't blame my graphics drivers any more.
Can anyone reproduce?
Best regards,
Andrew

I've just seen a similar problem on my DELL laptop. Anything at 2:1 or greater magification gets the jagged edges whilst panning up and down in loupe mode. This makes the compare mode to be worthless as the two images can't be compared as they each suffer different amounts of jaggies.
Windows XP, Intel Mobile 915GM/GMS, 910GML Express Chipset.
I'm going to raise a bug report.

Missing Loupe View File Info

I use the File Info feature a lot in Loupe View. However recently it does not show despite selecting it in the View>Loupe Info Menu. Control+I also fails to work. It happened before recent upgrade so do not link it with that software change.
In the past I occasionally had to reset the viewing option to reinstate visibility, for no apparent reason. Has anyone had a similar problem and found a permanent cure? Thank you.

Hal, thank you. Yes, I have tried all known short cuts. I forgot to mention I am using Windows 7 OS.
Strangely, I have just been into Develop module and the data is presented as normal there. Very odd!

Bigger 'Rejected' Indicator in Loupe View?

Any way to get a larger, solitary flag indicator in the loupe view?
Kind of like taking a red Sharpie and drawing a line through rejects on a contact sheet or proofs. Very rapid to discern and move on.
(The custom loupe overlays include the flag status, but they're lumped in with the label and star rating (which I don't use), and are tedious to read.)
Maybe a plug-in? Or is this a feature request? Thanks.

Any way to get a larger, solitary flag indicator in the loupe view?
No.
Why is this a concern? Lightroom gives you several ways to find the items with a rejected flag.

Loupe view thumbnail size

Somehow I accidentally made the thumbnails in the loupe view (the small row of images along the bottom of the screen) get larger. I can't make them smaller like they used to be and cannot find anything in help to make them small again. It's very annoying. Can someone please help me restore them to a smaller size?? Please??
Thanks!
Bill

Grab the border above the filmstrip and drag up or down until the thumbnails are a size you like.
Hal

Initial loupe view appears a little soft in LR3

Windows 7 64bit Ultimate
12 GB ram
30 inch monitor resolution 2560x1600
12000+ images in catalog
Standard previews set to 2048 Medium
Detail in loupe view seems to be soft. When I zoom in, the detail is great. When I zoom back, the detail remains good. If I close LR3 and reopen, I have to zoom in and out to get the best detail in loupe view even on the same image. I deleted the preview folder and regenerated previews at 2048 High Quality. The same problem occurs. This is making it hard to determine the quality of my shots. It’s too time consuming to zoom in and out on every shot. Any suggestions would be appreciated.

Thanks for the update Ian,
Maybe next time around.
That's really the only problem that I'm having, so otherwise I'm real happy with 3.2.
Thanks for all the hard work!

Imovie crashes when i try to view the video full screen or export it. How do i fix this?

iMovie crashes when i try to view the project full screen and export it. How do i fix this?

Close out of the camera app, double tap the home button and completely close out of the app.
Then do a reset, no data loss. Hold down the home/sleep button together until you see the apple logo and then release, then wait for the phone to boot back up.
Then check your camera roll again.

Reproducible crash on Win 7 in Loupe View

Similar Messages

Maybe you are looking for