• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
9

P: Unable to backup catalog in Lightroom 4

Explorer ,
Mar 09, 2012 Mar 09, 2012

Copy link to clipboard

Copied

I have not been able to backup my catalog in Lightroom 4 since upgrading two days ago. I did not have this problem with 4 beta. It runs through checking integrity, backing up, and optimizing, and then I get a message that it was unsuccessful and to make sure I have enough space and check directory permissions. There is plenty of space, and I have tried to create it to two different drives without success.

I am using the 32-bit version with Windows 7. The size of my catalog is 1.7 GB and includes my previous LR3 and LR4 beta catalogs. Thanks.

Bug Fixed
TOPICS
Windows

Views

829

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , May 31, 2012 May 31, 2012
This issue has been fixed in Lightroom 4.1, which is now available. To download the 4.1 update, go to the Help menu in Lightroom and choose "Check for Updates".

Thanks,
Ben

Votes

Translate

Translate
55 Comments
Explorer ,
Mar 11, 2012 Mar 11, 2012

Copy link to clipboard

Copied

I seem to have found a work-around by splitting the catalog into two new ones using the Export as Catalog feature. Exporting to a single catalog creates a new catalog, which also fails to back up.

Is there a limit to the number of photos you can have in a catalog? I had well under 200,000. Could something in the original catalog cause the backup to fail?

I hate cryptic messages that don't identify what caused the error.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Mar 18, 2012 Mar 18, 2012

Copy link to clipboard

Copied

I'm a devoted Lightroom fan with the same backup error in Lightroom 4. I reproduced this error message 4 times (every time I try to exit):

"Lightroom was unable to back up the catalog named "[my specified name]"
Please check your folder permissions, and make sure that you have available space on your backup drive and main catalog's drive.
Try Again / Choose different Backup Folder... / Exit"

The catalog optimization seems to work without an error message (done both within Lightroom without exiting and also during the exit), but no backup is created after the error message during exit. Pressing "Try again" doesn't help.

I suppose a workaround is to simply manually copy the lrcat file to a backup location, or rely on my normal daily Windows Backup program take care of copying the lrcat file to my external USB backup hard drive. The problem makes me uneasy about the stability of Lightroom 4 and I hope Adobe can solve the problem.

The catalog is 3 gigabytes in size with 70,000 images. I have plenty of hard drive space (481 gb free on a 1.8 tb drive) and folder permissions are not a problem. No problem in previous Lightroom version 3.6 or earlier. I have Windows Vista Home Premium.

I tried moving the catalog.lrcat, Previews.lrdata, and Lightroom Settings files from where they started by default: USERS/myname/APDATA/ROAMING/ADOBE/LIGHTROOM/DEVELOP PRESETS/USER PRESETS/
to a folder in my PICTURES directory, but that didn't help the problem.

I sure don't want to split the catalog. That makes photo portfolio management a pain. Important image collections cross all directories. Adobe support, please advise.

Tom Dempsey
tom@photoseek.com
206-372-7673 mobile

Votes

Translate

Translate

Report

Report
Explorer ,
Mar 18, 2012 Mar 18, 2012

Copy link to clipboard

Copied

Tom, your description of the problem is the same as mine, except that I'm using Windows 7 rather than Vista and my catalog is a bit smaller.

Even after splitting the catalog, the backup still fails. For now, I am simply copying the catalog to back it up, but hopefully Adobe will address this.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Mar 18, 2012 Mar 18, 2012

Copy link to clipboard

Copied

Richard,
I got the Lightroom 4.0 catalog backup to work during Exit by NOT selecting the boxes for "Test integrity" and "optimize catalog after backup". I waited 10 minutes for "backing up" the 3 gb catalog, and the backup finally worked! I could see the backup nicely in the folder after Lightroom exited. Next test:

When I restarted Lightroom 4.0 (and registered the product so I could get support Monday-Friday: Adobe Support 800-833-6687), and this time re-selected the boxes for "Test integrity" and "optimize catalog after backup" during Exit, I reproduced the earlier error message after patiently waiting 25 minutes for my large 3 gigabyte catalog to say "Testing integrity," and "backing up catalog" -- which actually created the backup file as shown in Windows -- but it was deleted after the "optimizing catalog" process, which ends with this error:

"Lightroom was unable to back up the catalog named "[my named catalog]"
Please check your folder permissions, and make sure that you have available space on your backup drive and main catalog's drive."

- Pressing "Try Again" just creates the same error message.
- "Exit" will exit okay but without backing up.
- "Choose different Backup Folder" hangs for a long minute before sometimes responding with a black window labeled "&Choose Folder (Not Responding)" or no window at all, with the mouse cursor in forever "waiting" mode. After minutes of waiting, I'm forced to make Windows close the window and abort the hung Lightroom process. Not pretty.

Current workarounds:
A. Backup by copying the lrcat file manually, not automatically during exit,
B. or if choosing Backup during exit, DON'T select the boxes for "Test integrity" and "optimize catalog after backup".
Use File>Optimize Catalog command maybe once every few weeks within Lightroom 4.0, but NOT during Exit.

Tom

Votes

Translate

Translate

Report

Report
Advisor ,
Mar 18, 2012 Mar 18, 2012

Copy link to clipboard

Copied

I had the same problem. Could not make a backup to S:\users\cfw\Pictures\ .
I tried another drive and then it went fine.
I tried S:\ disk again it failed.
Then I changed drive letter S to X: and it's working since .
I have a catalog with 38.000 photos.

Frans

Votes

Translate

Translate

Report

Report
Explorer ,
Mar 18, 2012 Mar 18, 2012

Copy link to clipboard

Copied

Tom,

Your message was very helpful. I got similar results to yours.

I tried an optimize from the File menu separately from exiting and creating backup. It appeared to optimize successfully in just under 5 minutes. I only got a "bing" sound when it completed and no other confirmation, but when I tried to optimize again, the time it gave for previous optimize was a minute earlier.

I also told it to make a backup next time I exit, and I unchecked the "text integrity" and "optimize during backup" boxes. It successfully created a backup in just over 3 minutes.

Last night when I attempted to make a weekly backup with both boxes checked, the process seemed to take several hours and left me with an empty directory. I assume it created the file, but deleted it during the integrity checking process.

I'm surprised more people haven't reported this problem, but at least I know it's not just me.

Frans, I have tried creating backups to several drives, all without success. All the drives have plenty of space. I'm glad it worked for you.

Richard

Votes

Translate

Translate

Report

Report
Explorer ,
Mar 18, 2012 Mar 18, 2012

Copy link to clipboard

Copied

Tom,

I just did some further testing.

When I tried to create a backup with unchecking only the "test integrity" box, but leaving "optimize catalog" checked, I was successful in about 7 minutes.

When I tried the reverse, checking "test integrity" but unchecking "optimize catalog", I was successful in just over 3 minutes.

It only seems to fail with BOTH boxes are checked. If only one, either, is checked, it works.

The work around for now would seem to be to optimize separately, and uncheck the "optimize" box when creating the backup. Hopefully Adobe has a more permanent solution.

Richard

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Mar 19, 2012 Mar 19, 2012

Copy link to clipboard

Copied

I am not able to reproduce this problem. If you create a new Lightroom catalog, will it back up successfully? You don't have to make much of a catalog, just create a new catalog in Lightroom 4, import a couple images, and then try backing it up (with "test integrity" and "optimize" both checked). Let me know if that works, and we'll proceed from there.

Thanks,
Ben

Votes

Translate

Translate

Report

Report
Community Beginner ,
Mar 19, 2012 Mar 19, 2012

Copy link to clipboard

Copied

There is no problem when I create a new catalog in Lightroom 4, import 100 images, then backup with "test integrity" and "optimize" both checked. The backup then works fine.
I only get the problem using my large catalog converted from LR version 3.6.
What's the next step to isolate the problem?
Tom

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Mar 19, 2012 Mar 19, 2012

Copy link to clipboard

Copied

Thanks Tom. I am contacting Richard privately to obtain his catalog for testing, if he's willing to provide it. Just contacting Richard first, since his catalog is smaller. If for any reason that doesn't work out, or doesn't give me the info I need, I'll contact you privately as well. I'll post back to this thread with what I find.

Thanks,
Ben

Votes

Translate

Translate

Report

Report
Community Beginner ,
Mar 19, 2012 Mar 19, 2012

Copy link to clipboard

Copied

My 3 gb database also fails the backup with the error message when I check "optimize" and uncheck "test integrity."

To work around the problem, I uncheck both boxes during exit.
I used File>Optimize Catalog command once, inside of Lightroom 4, which seemed to work (taking about 20 minutes or so on 3 gb datalog), but it would be nice to get it working during exit.

Votes

Translate

Translate

Report

Report
Explorer ,
Mar 19, 2012 Mar 19, 2012

Copy link to clipboard

Copied

I have sent Ben my catalog to test.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Mar 21, 2012 Mar 21, 2012

Copy link to clipboard

Copied

Hi Richard,

Unfortunately, your catalog backs up just fine more me, so I have been unable to reproduce the problem. If you and Thomas (and anyone else experiencing the problem) could try the following, it may prove helpful. These steps describe how to enable debug mode for Lightroom:

1. Right click the Lightroom icon you use to launch on the desktop and choose Copy from the menu.
2. Right click the Desktop and choose Paste from the menu.
3. Right click the new icon and choose Properties... from the menu.
4. In the Target field of the properties dialog append -tracebacks (separated from the path by a space): (It will look like this at the end when you're done (leave the rest of the path alone): lightroom.exe" -tracebacks)
5. In the general tab, you might also want to change the name so you can easily visually distinguish this new icon from the original (we'll delete it when we're done).
6. Go to this site in your browser: http://technet.microsoft.com/en-us/sy...
On the right hand side of the page, click the "Run DebugView" link (it's safe – it's just a debug output viewer from Microsoft)
7. Click through the Eula if necessary.
8. With DebugView running, double click the new icon we created in steps 1-5.
Repeat the steps in Lightroom that cause the problem that you are seeing.
9. Save the output from the debugger. You can either highlight and copy/paste or choose "Save as..." from the menu to save the output to a file.
10. Post the debug info back to this thread.

With luck, there will be something meaningful in there that will explain the failure. Let me know if you have any questions.

Thanks,
Ben

P.S. Just for yucks, try throwing out your Lightroom preferences, if you haven't already. That will often fix all manner of weird little problems. Go to Users/[user name]/AppData/Roaming/Adobe/Lightroom/ and in there you'll see a folder called "Preferences." Throw that out, or just move it to the desktop if you want to keep it. Then If removing it doesn't help, you can put it back if you wish.

Votes

Translate

Translate

Report

Report
New Here ,
Mar 21, 2012 Mar 21, 2012

Copy link to clipboard

Copied

Hi and Thanks to all who have already posted with this issue.
I am also having problems and can now backup my catalog by unchecking optimize and chechk integrity- so thanks for that woprk around.

I have also just run the bug check that Ben has mentioned. Is seems as though there is a memory issue but I'm not too clear from the data why.Here is the data:-

00000001 0.00000000 [972] L:
00000002 0.00005184 [972] canceled
00000003 0.00005184 [972] 0: global error - C
00000004 0.00005184 [972] 1: [unnamed] - 1250880549:150+4
00000005 0.00005184 [972] 2: [unnamed] - C
00000006 0.00005184 [972] 3: global pcall - C
00000007 0.00005184 [972] 4: upvalue ? - 2040030245:1819+4
00000008 0.00005184 [972] 5: upvalue ? - 2040030245:2514+28
00000009 0.00005184 [972] 6: field readNegativeInfo - 2040030245:2554+8
00000010 0.00005184 [972] 7: field loadNegative - 476383837:280+37
00000011 0.00005184 [972] 8: [unnamed] - 1225751237:0+9
00000012 0.00005184 [972] 9: [unnamed] - tail
00000013 0.00005184 [972] 10: global pcall - C
00000014 0.00005184 [972] 11: [unnamed] - 155295939:73+43
00000015 0.00005184 [972] 12: [unnamed] - C
00000016 0.00005184 [972] 13: global AgCallWithAutoreleasePool - C
00000017 0.00005184 [972] 14: [unnamed] - 155295939:0+25
00000018 0.00005184 [972] ---------------------------------
00000019 0.00009547 [972]
00000020 0.00055177 [972] L:
00000021 0.00058308 [972] canceled
00000022 0.00058308 [972] 0: global assert - C
00000023 0.00058308 [972] 1: field readNegativeInfo - 2040030245:2554+9
00000024 0.00058308 [972] 2: field loadNegative - 476383837:280+37
00000025 0.00058308 [972] 3: [unnamed] - 1225751237:0+9
00000026 0.00058308 [972] 4: [unnamed] - tail
00000027 0.00058308 [972] 5: global pcall - C
00000028 0.00058308 [972] 6: [unnamed] - 155295939:73+43
00000029 0.00058308 [972] 7: [unnamed] - C
00000030 0.00058308 [972] 8: global AgCallWithAutoreleasePool - C
00000031 0.00058308 [972] 9: [unnamed] - 155295939:0+25
00000032 0.00058308 [972] ---------------------------------
00000033 0.00061131 [972]
00000034 242.96647644 [972] L:
00000035 242.96656799 [972] Database "D:\Libraries\lightroom\lightroom 4.0\lightroom 4\lightroom 4.lrcat": out of memory
00000036 242.96656799 [972] Statement: VACUUM
00000037 242.96656799 [972] 0: method exec - C
00000038 242.96656799 [972] 1: method exec - 59600407:436+44
00000039 242.96656799 [972] 2: method exec - 1098400342:842+5
00000040 242.96656799 [972] 3: [unnamed] - 219380148:1250+5
00000041 242.96656799 [972] 4: global pcall - C
00000042 242.96656799 [972] 5: [unnamed] - 64465982:209+5
00000043 242.96656799 [972] 6: global pcall - C
00000044 242.96656799 [972] 7: [unnamed] - 1098400342:536+44
00000045 242.96656799 [972] 8: [unnamed] - tail
00000046 242.96656799 [972] 9: [unnamed] - tail
00000047 242.96656799 [972] 10: global pcall - C
00000048 242.96656799 [972] 11: [unnamed] - 1098400342:1046+19
00000049 242.96656799 [972] 12: [unnamed] - tail
00000050 242.96656799 [972] 13: global pcall - C
00000051 242.96656799 [972] 14: [unnamed] - 40549723:887+13
00000052 242.96656799 [972] 15: global pcall - C
00000053 242.96656799 [972] 16: [unnamed] - 1098400342:499+13
00000054 242.96656799 [972] 17: [unnamed] - tail
00000055 242.96656799 [972] 18: [unnamed] - 1317688261:99+46
00000056 242.96656799 [972] 19: global pcall - C
00000057 242.96656799 [972] 20: [unnamed] - 1002929302:1193+34
00000058 242.96656799 [972] 21: [unnamed] - tail
00000059 242.96656799 [972] 22: [unnamed] - tail
00000060 242.96656799 [972] 23: [unnamed] - tail
00000061 242.96656799 [972] 24: method dispatch - 1002929302:971+75
00000062 242.96656799 [972] 25: [unnamed] - 1002929302:1679+77
00000063 242.96656799 [972] 26: global AgCallWithAutoreleasePool - C
00000064 242.96656799 [972] 27: method run - 1002929302:1642+28
00000065 242.96656799 [972] 28: [unnamed] - 435542093:0+6
00000066 242.96656799 [972] ---------------------------------
00000067 242.96665955 [972]

I hope that this can be of some use

Mike

Votes

Translate

Translate

Report

Report
Explorer ,
Mar 21, 2012 Mar 21, 2012

Copy link to clipboard

Copied

My debug log also seems to indicate an "out of memory" problem. I can't paste the entire log here -- it''s long and it's not letting me, but below is an excerpt. It seemed to keep trying the same thing over and over and then giving up.

I can e-mail the log to you as an attachment if you like, Ben. Thanks.

00000021 490.16159058 [6060] Database "F:\Richard's Documents\My Pictures\Lightroom\Lightroom 4 Catalog.lrcat": out of memory
00000022 490.16159058 [6060] Statement: VACUUM
00000023 490.16159058 [6060] 0: method exec - C
00000024 490.16159058 [6060] 1: method exec - 59600407:436+44
00000025 490.16159058 [6060] 2: method exec - 1098400342:842+5
00000026 490.16159058 [6060] 3: [unnamed] - 219380148:1250+5
00000027 490.16159058 [6060] 4: global pcall - C
00000028 490.16159058 [6060] 5: [unnamed] - 64465982:209+5
00000029 490.16159058 [6060] 6: global pcall - C
00000030 490.16159058 [6060] 7: [unnamed] - 1098400342:536+44
00000031 490.16159058 [6060] 8: [unnamed] - tail
00000032 490.16159058 [6060] 9: [unnamed] - tail
00000033 490.16159058 [6060] 10: global pcall - C
00000034 490.16159058 [6060] 11: [unnamed] - 1098400342:1046+19
00000035 490.16159058 [6060] 12: [unnamed] - tail
00000036 490.16159058 [6060] 13: global pcall - C
00000037 490.16159058 [6060] 14: [unnamed] - 40549723:887+13
00000038 490.16159058 [6060] 15: [unnamed] - tail
00000039 490.16159058 [6060] 16: global pcall - C
00000040 490.16159058 [6060] 17: [unnamed] - 1098400342:499+13
00000041 490.16159058 [6060] 18: [unnamed] - tail
00000042 490.16159058 [6060] 19: [unnamed] - 1317688261:99+46
00000043 490.16159058 [6060] 20: global pcall - C
00000044 490.16159058 [6060] 21: [unnamed] - 1002929302:1193+34
00000045 490.16159058 [6060] 22: [unnamed] - tail
00000046 490.16159058 [6060] 23: [unnamed] - tail
00000047 490.16159058 [6060] 24: [unnamed] - tail
00000048 490.16159058 [6060] 25: method dispatch - 1002929302:971+75
00000049 490.16159058 [6060] 26: [unnamed] - 1002929302:1679+77
00000050 490.16159058 [6060] 27: global AgCallWithAutoreleasePool - C
00000051 490.16159058 [6060] 28: method run - 1002929302:1642+28
00000052 490.16159058 [6060] 29: [unnamed] - 435542093:0+6
00000053 490.16159058 [6060] ---------------------------------
00000054 490.16168213 [6060]
00000055 490.83874512 [6060] L:
00000056 490.83883667 [6060] Database "F:\Richard's Documents\My Pictures\Lightroom\Lightroom 4 Catalog.lrcat": out of memory
00000057 490.83883667 [6060] Statement: PRAGMA integrity_check
00000058 490.83883667 [6060] 0: [unnamed] - C
00000059 490.83883667 [6060] 1: [unnamed] - 59600407:614+42
00000060 490.83883667 [6060] 2: [unnamed] - tail
00000061 490.83883667 [6060] 3: [unnamed] - 40549723:773+3
00000062 490.83883667 [6060] 4: global pcall - C
00000063 490.83883667 [6060] 5: [unnamed] - 1098400342:536+44
00000064 490.83883667 [6060] 6: [unnamed] - tail
00000065 490.83883667 [6060] 7: [unnamed] - 40549723:798+3
00000066 490.83883667 [6060] 8: global pcall - C
00000067 490.83883667 [6060] 9: [unnamed] - 1098400342:1046+19
00000068 490.83883667 [6060] 10: [unnamed] - tail
00000069 490.83883667 [6060] 11: global pcall - C
00000070 490.83883667 [6060] 12: upvalue ? - 40549723:812+9
00000071 490.83883667 [6060] 13: [unnamed] - 40549723:985+59
00000072 490.83883667 [6060] 14: global pcall - C
00000073 490.83883667 [6060] 15: [unnamed] - 1098400342:499+13
00000074 490.83883667 [6060] 16: [unnamed] - tail
00000075 490.83883667 [6060] 17: [unnamed] - 1317688261:99+46
00000076 490.83883667 [6060] 18: global pcall - C
00000077 490.83883667 [6060] 19: [unnamed] - 1002929302:1193+34
00000078 490.83883667 [6060] 20: [unnamed] - tail
00000079 490.83883667 [6060] 21: [unnamed] - tail
00000080 490.83883667 [6060] 22: [unnamed] - tail
00000081 490.83883667 [6060] 23: method dispatch - 1002929302:971+75
00000082 490.83883667 [6060] 24: [unnamed] - 1002929302:1679+77
00000083 490.83883667 [6060] 25: global AgCallWithAutoreleasePool - C
00000084 490.83883667 [6060] 26: method run - 1002929302:1642+28
00000085 490.83883667 [6060] 27: [unnamed] - 435542093:0+6
00000086 490.83883667 [6060] ---------------------------------
00000087 490.83892822 [6060]
00000088 490.83920288 [6060] L:
00000089 490.83923340 [6060] Database "F:\Richard's Documents\My Pictures\Lightroom\Lightroom 4 Catalog.lrcat": out of memory
00000090 490.83923340 [6060] Statement: PRAGMA integrity_check
00000091 490.83923340 [6060] 0: global assert - C
00000092 490.83923340 [6060] 1: [unnamed] - 1098400342:536+66
00000093 490.83923340 [6060] 2: [unnamed] - tail
00000094 490.83923340 [6060] 3: [unnamed] - 40549723:798+3
00000095 490.83923340 [6060] 4: global pcall - C
00000096 490.83923340 [6060] 5: [unnamed] - 1098400342:1046+19
00000097 490.83923340 [6060] 6: [unnamed] - tail
00000098 490.83923340 [6060] 7: global pcall - C
00000099 490.83923340 [6060] 8: upvalue ? - 40549723:812+9
00000100 490.83923340 [6060] 9: [unnamed] - 40549723:985+59
00000101 490.83923340 [6060] 10: global pcall - C
00000102 490.83923340 [6060] 11: [unnamed] - 1098400342:499+13
00000103 490.83923340 [6060] 12: [unnamed] - tail
00000104 490.83923340 [6060] 13: [unnamed] - 1317688261:99+46
00000105 490.83923340 [6060] 14: global pcall - C
00000106 490.83923340 [6060] 15: [unnamed] - 1002929302:1193+34
00000107 490.83923340 [6060] 16: [unnamed] - tail
00000108 490.83923340 [6060] 17: [unnamed] - tail
00000109 490.83923340 [6060] 18: [unnamed] - tail
00000110 490.83923340 [6060] 19: method dispatch - 1002929302:971+75
00000111 490.83923340 [6060] 20: [unnamed] - 1002929302:1679+77
00000112 490.83923340 [6060] 21: global AgCallWithAutoreleasePool - C
00000113 490.83923340 [6060] 22: method run - 1002929302:1642+28
00000114 490.83923340 [6060] 23: [unnamed] - 435542093:0+6
00000115 490.83923340 [6060] ---------------------------------
00000116 490.83932495 [6060]
00000117 490.83969116 [6060] L:
00000118 490.83972168 [6060] Database "F:\Richard's Documents\My Pictures\Lightroom\Lightroom 4 Catalog.lrcat": out of memory
00000119 490.83972168 [6060] Statement: PRAGMA integrity_check
00000120 490.83972168 [6060] 0: global assert - C
00000121 490.83972168 [6060] 1: [unnamed] - 1098400342:1046+35
00000122 490.83972168 [6060] 2: [unnamed] - tail
00000123 490.83972168 [6060] 3: global pcall - C
00000124 490.83972168 [6060] 4: upvalue ? - 40549723:812+9
00000125 490.83972168 [6060] 5: [unnamed] - 40549723:985+59
00000126 490.83972168 [6060] 6: global pcall - C
00000127 490.83972168 [6060] 7: [unnamed] - 1098400342:499+13
00000128 490.83972168 [6060] 8: [unnamed] - tail
00000129 490.83972168 [6060] 9: [unnamed] - 1317688261:99+46
00000130 490.83972168 [6060] 10: global pcall - C
00000131 490.83972168 [6060] 11: [unnamed] - 1002929302:1193+34
00000132 490.83972168 [6060] 12: [unnamed] - tail
00000133 490.83972168 [6060] 13: [unnamed] - tail
00000134 490.83972168 [6060] 14: [unnamed] - tail
00000135 490.83972168 [6060] 15: method dispatch - 1002929302:971+75
00000136 490.83972168 [6060] 16: [unnamed] - 1002929302:1679+77
00000137 490.83972168 [6060] 17: global AgCallWithAutoreleasePool - C
00000138 490.83972168 [6060] 18: method run - 1002929302:1642+28
00000139 490.83972168 [6060] 19: [unnamed] - 435542093:0+6
00000140 490.83972168 [6060] ---------------------------------
00000141 490.83981323 [6060]
00000142 490.84011841 [6060] L:
00000143 490.84014893 [6060] Database "F:\Richard's Documents\My Pictures\Lightroom\Lightroom 4 Catalog.lrcat": out of memory
00000144 490.84014893 [6060] Statement: PRAGMA integrity_check
00000145 490.84014893 [6060] 0: global error - C
00000146 490.84014893 [6060] 1: upvalue ? - 40549723:812+26
00000147 490.84014893 [6060] 2: [unnamed] - 40549723:985+59
00000148 490.84014893 [6060] 3: global pcall - C
00000149 490.84014893 [6060] 4: [unnamed] - 1098400342:499+13
00000150 490.84014893 [6060] 5: [unnamed] - tail
00000151 490.84014893 [6060] 6: [unnamed] - 1317688261:99+46
00000152 490.84014893 [6060] 7: global pcall - C
00000153 490.84014893 [6060] 8: [unnamed] - 1002929302:1193+34
00000154 490.84014893 [6060] 9: [unnamed] - tail
00000155 490.84014893 [6060] 10: [unnamed] - tail
00000156 490.84014893 [6060] 11: [unnamed] - tail
00000157 490.84014893 [6060] 12: method dispatch - 1002929302:971+75
00000158 490.84014893 [6060] 13: [unnamed] - 1002929302:1679+77
00000159 490.84014893 [6060] 14: global AgCallWithAutoreleasePool - C
00000160 490.84014893 [6060] 15: method run - 1002929302:1642+28
00000161 490.84014893 [6060] 16: [unnamed] - 435542093:0+6
00000162 490.84014893 [6060] ---------------------------------
00000163 490.84017944 [6060]
00000164 490.84042358 [6060] L:
00000165 490.84048462 [6060] Database "F:\Richard's Documents\My Pictures\Lightroom\Lightroom 4 Catalog.lrcat": out of memory
00000166 490.84048462 [6060] Statement: PRAGMA integrity_check
00000167 490.84048462 [6060] 0: global assert - C
00000168 490.84048462 [6060] 1: [unnamed] - 1098400342:499+30
00000169 490.84048462 [6060] 2: [unnamed] - tail
00000170 490.84048462 [6060] 3: [unnamed] - 1317688261:99+46
00000171 490.84048462 [6060] 4: global pcall - C
00000172 490.84048462 [6060] 5: [unnamed] - 1002929302:1193+34
00000173 490.84048462 [6060] 6: [unnamed] - tail
00000174 490.84048462 [6060] 7: [unnamed] - tail
00000175 490.84048462 [6060] 8: [unnamed] - tail
00000176 490.84048462 [6060] 9: method dispatch - 1002929302:971+75
00000177 490.84048462 [6060] 10: [unnamed] - 1002929302:1679+77
00000178 490.84048462 [6060] 11: global AgCallWithAutoreleasePool - C
00000179 490.84048462 [6060] 12: method run - 1002929302:1642+28
00000180 490.84048462 [6060] 13: [unnamed] - 435542093:0+6
00000181 490.84048462 [6060] ---------------------------------
00000182 490.84051514 [6060]
00000183 490.84103394 [6060] L:
00000184 490.84109497 [6060] Database "F:\Richard's Documents\My Pictures\Lightroom\Lightroom 4 Catalog.lrcat": out of memory
00000185 490.84109497 [6060] Statement: PRAGMA integrity_check
00000186 490.84109497 [6060] 0: global assert - C
00000187 490.84109497 [6060] 1: [unnamed] - 1317688261:269+81
00000188 490.84109497 [6060] 2: [unnamed] - 179812414:1976+12
00000189 490.84109497 [6060] ---------------------------------

Votes

Translate

Translate

Report

Report
New Here ,
Mar 22, 2012 Mar 22, 2012

Copy link to clipboard

Copied

Hi
I just thought that it would be helpful to know that I ran my bug check during the proccess of just optimizing catalog for the menu within lightroom not by backing it up. I can run further bug checks, during the back up process, if it helps.
Mike

Votes

Translate

Translate

Report

Report
Community Beginner ,
Mar 22, 2012 Mar 22, 2012

Copy link to clipboard

Copied

"out of memory" from Lightroom 4 after 15 minutes wait during attempt to Backup during Exit, with both "Test integrity" and "optimize catalog after backup" checked:

[3972] [DmmApp.cpp 2161] kPcMonitor_TimerId
[3972]
[3972] (2012-03-22 13:40:30)
[3972] [DmmApp.cpp 2161] kPcMonitor_TimerId
[3972]
[3972] (2012-03-22 13:40:40)
[3972] [DmmApp.cpp 2161] kPcMonitor_TimerId
[3972]
[3972] (2012-03-22 13:40:50)
[3972] [DmmApp.cpp 2161] kPcMonitor_TimerId
[3972]
[3972] (2012-03-22 13:41:00)
[3972] [DmmApp.cpp 2161] kPcMonitor_TimerId
[3972]
[3972] (2012-03-22 13:41:10)
[3972] [DmmApp.cpp 2161] kPcMonitor_TimerId
[3972]
[2880] L:
[2880] Database "C:\Users\dempsey\Pictures\Adobe Lightroom 4 MASTER database\LR4-Tom-Catalog.lrcat": out of memory
[2880] Statement: VACUUM
[2880] 0: method exec - C
[2880] 1: method exec - 59600407:436+44
[2880] 2: method exec - 1098400342:842+5
[2880] 3: [unnamed] - 219380148:1250+5
[2880] 4: global pcall - C
[2880] 5: [unnamed] - 64465982:209+5
[2880] 6: global pcall - C
[2880] 7: [unnamed] - 1098400342:536+44
[2880] 8: [unnamed] - tail
[2880] 9: [unnamed] - tail
[2880] 10: global pcall - C
[2880] 11: [unnamed] - 1098400342:1046+19
[2880] 12: [unnamed] - tail
[2880] 13: global pcall - C
[2880] 14: [unnamed] - 40549723:887+13
[2880] 15: [unnamed] - tail
[2880] 16: global pcall - C
[2880] 17: [unnamed] - 1098400342:499+13
[2880] 18: [unnamed] - tail
[2880] 19: [unnamed] - 1317688261:99+46
[2880] 20: global pcall - C
[2880] 21: [unnamed] - 1002929302:1193+34
[2880] 22: [unnamed] - tail
[2880] 23: [unnamed] - tail
[2880] 24: [unnamed] - tail
[2880] 25: method dispatch - 1002929302:971+75
[2880] 26: [unnamed] - 1002929302:1679+77
[2880] 27: global AgCallWithAutoreleasePool - C
[2880] 28: method run - 1002929302:1642+28
[2880] 29: [unnamed] - 435542093:0+6
[2880] ---------------------------------
[2880]
[3972] (2012-03-22 13:41:20)
[3972] [DmmApp.cpp 2161] kPcMonitor_TimerId
[3972]
[3972] (2012-03-22 13:41:30)
[3972] [DmmApp.cpp 2161] kPcMonitor_TimerId
[3972]
[3972] (2012-03-22 13:41:40)
[3972] [DmmApp.cpp 2161] kPcMonitor_TimerId
[3972]

Other memory problems in Lightroom 4:
1) Clicking between the Edit and Develop tabs takes 10 to 60% longer than in version 3.6.
2) After changing Develop sliders on a TIF images, attempting to zoom to 100% pixel view fails to sharpen and no "Loading" message displays. Only exiting and reentering Lightroom sharpens the 100% pixel view on that image. The problem isn't as frequent on RAW images, but can also happen after editing several RAW images. TIF images larger than about 5000 or 6000 pixels on the longer side tend to fail with recurring "there is a problem with the images" message. Exiting and reentering Lightroom eliminates the error message so I can continue editing the image.

Computer settings:
Nothing running in memory except Google Chrome browser with two tabs, plus Lightroom 4. The LR catalog is 3 gigabytes in size with 70,000 images.
4 gb RAM, 2.4 Ghz, Windows Vista Home Premium, Service Pack 2.
The computer has plenty of hard drive space (481 gb free on a 1.8 tb drive), a system check in Vista says system performance is good and "defragmenting the hard drive is not needed."
No problems in previous Lightroom version 3.6 on the same setup.

Tom

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Mar 22, 2012 Mar 22, 2012

Copy link to clipboard

Copied

Thanks everyone.

@Richard: yes, please email me the full log.

@everyone: please let me know your machine specs, particularly including OS version, amount of RAM, and whether it is a 32 bit system or a 64 bit system.

Thanks,
Ben

Votes

Translate

Translate

Report

Report
Community Beginner ,
Mar 22, 2012 Mar 22, 2012

Copy link to clipboard

Copied

The memory problems occur using:
32-bit Windows Vista Home Premium, Service Pack 2.
Dell XPS 420 Workstation (purchased December 2007).
Intel Core 2 Quad CPU Q6600 at 2.4 Gz.
4 gb RAM. After Vista loads, about 3.25 gb RAM is available for other processes.
NVIDIA geForce 8800 GT video.
1863 gb Raid level 0 hard drive striped for speed and size, 481 gb is currently free space, "defrag not needed" according to system check

Tom

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Mar 22, 2012 Mar 22, 2012

Copy link to clipboard

Copied

Thanks Thomas. We definitely have an unfortunate and varied history of out-of-memory problems on 32 bit Win machines, so this is useful info. My understanding is that on a 32 bit machine, Lightroom can only address 2 GB of RAM, no matter how much you have available. Is everyone else on this thread using 32 bit as well?

-Ben

Votes

Translate

Translate

Report

Report
LEGEND ,
Mar 22, 2012 Mar 22, 2012

Copy link to clipboard

Copied

@Ben I have the same problem with 3.6 on a MacBook pro with lion and 4gb ram as well. i can provide my log if it helps.

Votes

Translate

Translate

Report

Report
New Here ,
Mar 23, 2012 Mar 23, 2012

Copy link to clipboard

Copied

Hi Ben

I am using windows 7 32bit sp1 4gb ram loads of disk space. My cataloge size is 3.47gb

Mike

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Mar 26, 2012 Mar 26, 2012

Copy link to clipboard

Copied

Hi All,

Thanks for your help. I am now able to reproduce this problem when using Richard's or Tom's catalogs on a 32 bit Windows machine. I have entered the issue in our bug database, so an engineer will be taking a look at it. I'll update this thread with info as I get it.

Thanks,
Ben

Votes

Translate

Translate

Report

Report
Explorer ,
Mar 26, 2012 Mar 26, 2012

Copy link to clipboard

Copied

Thanks for the update, Ben. That's good news that it can be reproduced. Hopefully this will be resolved in the next update of LR4, as this was never a problem with LR3.

Richard

Votes

Translate

Translate

Report

Report
LEGEND ,
Mar 29, 2012 Mar 29, 2012

Copy link to clipboard

Copied

I use MacOSX Lion and I try to backup my LR4 catalog on a Samba-Share.
After it is checked, the dialog says it will save the catalog, but after a minute or so, i will get an error that it could not be saved.
A dir in my Backup-Share has been created, but no catalog file.

Votes

Translate

Translate

Report

Report