Lightroom: 3.4.1 crashing - first during export, then when starting up.

  • 1
  • Problem
  • Updated 7 years ago
  • (Edited)
I don't have a lot of solid supporting information yet, but I'm having a hard time with the new release.

Seems like multiple simultaneous plugin-based exports are particularly problematic.

And, the only way I've been able to get it to start up again after crashing during export is to rename the folder where I keep my plugins.

I didn't have this problem with 3.4.0, but once the problem occurred in 3.4.1, my attempts to fall back to 3.4.0 did not alleviate. Note: After uninstalling 3.4.1 and reinstalling 3.4.0, windows control panel still says its 3.4.1.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 378 Reply Likes

Posted 7 years ago

  • 1
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 3960 Posts
  • 1380 Reply Likes
Rob, can you reproduce the problems without any plug-ins in use? If so, can you try narrowing it down to which plug-in is causing the problem?

You could also try rolling back to 3.3 (which should roll back ok) to see if you get the same problem.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 378 Reply Likes
I'll try to get some better info. So far, it seems to be the concurrency that is the problem. This may be the same problem I've been having just gotten worse. - I've always had a problem with FTP'ing plugins, but perhaps the reason is that the FTP'ing is happening in an asynchronous task. I have now been able to get failure from different pairs of plugins when their execution is overlapping, whether FTP'ing or not. Note: there aren't any conflicts like trying to write the same file at the same time, however they are sharing some common code. It was my assumption that modules would be loaded into separate environments for each plugin, even if they shared the same source code - am I wrong about that? I'll try separating the source code so none is common and see if that makes a difference. I don't know yet about non-plugin based exports.
Photo of Dan Tull

Dan Tull, Employee

  • 172 Posts
  • 38 Reply Likes
I'd guess this is also in 3.4 since the changes from 3.4 were extremely localized, but it would be possible that it somehow managed to affect JPEG exports.

In any case, if by "crash" you mean the process aborts (I've been running into ambiguous uses of the term lately) or hangs, I'd be interested in getting a crash dump to inspect for clues.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 378 Reply Likes
Hi Dan, I've got it working reliably now by simply exporting sequentially (no concurrent export tasks) and FTP'ing using external app. (It may have also helped to tick the "reload before each export" box - not sure yet) So, my motivation has dropped some. Regardless, I'll try and get a crash dump out, in case it would help. As I've mentioned before, I've been having a similar problem for some time, although I thought it was just the FTP'ing (maybe I was wrong), but I'd never ever had a crash that wouldn't be cleared by restarting Lightroom, that was new. It started with 3.4.1 but I can't say it was caused by 3.4.1...

PS - by "crash" I mean Windows presents me with the "Lightroom is crashed" dialog box (e.g. do you want to check for a solution online or just deep-6 the process... - my words, not Microsoft's ;-}). This is generally preceded by the spinning blue doughnut of death...

*** One question that has come to mind: if two plugins share some of the same plugin source files, is there any potential for conflict, or are those modules handled in a completely separate fashion for each plugin? I've always assumed the latter, but now I'm wondering...
Photo of Dan Tull

Dan Tull, Employee

  • 172 Posts
  • 38 Reply Likes
Oh, wait. There is a known 3.x bug where FTP (maybe just SFTP, I don't recall for sure) crashes on 64-bit Windows. There's a fix internally, but it was invasive enough we didn't put it into the 3.x line. Were you previously using LR built-in FTP or were you using the external process for FTP when you were seeing the crashes?

As for plugin file sharing, I think each plugin is separate in terms of code loading at least.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 378 Reply Likes
Lr built-in FTP (win7/64) - not sFTP. (I'm not sure which external process for FTP you mean). Reminder: I've been able to reproduce the problem with simultaneously executing export tasks, even when they are not doing FTP, so FTP may be a red herring.

I had a private message from you with instructions for sending you a crash dump but I'm not able to get at it now (I assume private messaging has been discontinued on the old site).

- how do I obtain and send a crash dump?
Photo of Dan Tull

Dan Tull, Employee

  • 172 Posts
  • 38 Reply Likes
> not sure which external process you mean
From your prior comment. "by simply exporting sequentially (no concurrent export tasks) and FTP'ing using external app."

Still, though given you've seen it w/o FTP, it probably is a red herring.

The LocalDumps registry key should work:
http://msdn.microsoft.com/en-us/libra...

It defaults to writing mini dumps. We might need to circle back and get a full dump, but a mini dump is a lot easier (smaller, just a few MB instead of as big as the process's memory size) to send if it turns out to be sufficient.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 378 Reply Likes
I just had a crash without even doing an export (note: all plugin background processes are disabled), and Lightroom would then not start back up, until I renamed my plugins folder. So, it seems at least part of the problem is tied to plugins somehow. I will send crash dump, but I'm now suspecting a recent plugin change may be a culprit, so I will commence troubleshooting for that...
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 378 Reply Likes
So far, I have been unable to obtain a crash dump for Lightroom. Configuration:



What am I doing wrong? (I also tried setting the dump-folder to an explicit absolute path - didn't help).
Photo of Dan Tull

Dan Tull, Employee

  • 172 Posts
  • 38 Reply Likes
When I've done it, I just set the LocalDumps key. All the other stuff defaults to reasonable values. Maybe you have a value set wrong. The other possibility is that you're not getting a crash in the strict sense, but a hang (in Win7/Vista it's hard to tell the difference based on the message alone). For that, the instructions are different.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 378 Reply Likes
Probably I'm only having hangs now. Its clear there is something happening upon plugin initialization that Lightroom is not liking, since once it gets in a funk, it will not usually restart (without hanging) until I rename my plugins folder - I will try to isolate further...
Photo of Dan Tull

Dan Tull, Employee

  • 172 Posts
  • 38 Reply Likes
If you're familiar with WinDbg (or want to get familiar), it's fairly easy to run an app in it and save mini dumps when it gets into trouble. I use the .dump command, but I think it might be in the menus as well.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 378 Reply Likes
I'll check it out - thanks Dan.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 378 Reply Likes
Progress:

- I've learned the difference between a crash and a hang. And, as I tried to find the reason for the hanging, it stopped happening. Dunno if it was the yields I added, or just letting the hang go (much to my surprise it recovered after a few minutes), or what...

- So, I'm back to the problem I've been having for some time: crash during FTP task. Also, I did get the crash dump - how to send it in?
Photo of Dan Tull

Dan Tull, Employee

  • 172 Posts
  • 38 Reply Likes
Yields could definitely fix a hang. As for the FTP part, that's a known bug, so I don't need crash dumps. That's not to say it'll be fixed in 3.x based on the scope of changes that were involved, but it is at least past the diagnostic phase.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 378 Reply Likes
Thanks Dan.