Loading Profile...
Photosynth ran out of memory during processing (8007000E)
While processing about 200 images, Photosynth reported an error "ran out of memory" err=8007000E. What causes that and what can one do?
I’m bummed - it would have been great to see the synth!
10
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
-
Inappropriate?what cpu and how much ram do you have?3 Comments
Add a comment
This solves the problem
-
Its an AMD Athlon 64 X2 Dual Core 4200+ 2.2Ghz, with 3.25 gigs of RAM running Windows XP Home, Service Pack 3 -
Also: paging size is "system managed" with 71 Gigs free on the drive.
-
200 photos? I can't upload more than three.
-
Inappropriate?200 is a normal number of images for the synthing process to handle. how much RAM do you have? how many cpus on your machine?
-
Inappropriate?The machine is an AMD Athlon 64 X2 Dual Core 4200+ 2.2Ghz, with 3.25 gigs of RAM running Windows XP Home, Service Pack 3 Also: paging size is "system managed" with 71 Gigs free on the drive.
-
Inappropriate?The images are all overlapping ones (aerial images) from a single series of shots. Each image is about 1.2 megs, nothing out of the ordinary (i.e., other synths I have done have worked).
-
Inappropriate?Hm, this really shouldn't have been a problem. Maybe try rebooting? (Please no OS jokes :)
I’m puzzled
-
Inappropriate?I've rebooted w/o any luck. Oddly other synths worked. I went through the set of images and removed some that were blurry (always a problem with KAP images). Im not sure which image or set of images that caused the problem, but when I tried it again, the synth was successful (this one is: http://photosynth.net/view.aspx?cid=5...
I would have guess that Photosynth would simply not include photos that didnt match. Why would slightly blurry images cause a problem?
-
Inappropriate?I think it's just a function of the number of photos-- any that you remove will reduce the memory burden. Photosynth is fine with blurry photos or photos that don't match-- they just don't end up in the same 'group'. I'm still puzzled that the 200 posed a problem on your machine-- not sure what's up with that.
-
Inappropriate?Can you possibly tell at which stage "out of memory" happens? Is it during "Extracting image features", "matching", or "reconstruction", etc?
-
Inappropriate?I have the same problem. Tryed on 2 PCs:
Atlon 64 3200+ single core 2Gb RAM, Vista SP1 32bit
Core 2 Dou T8300 dual-core 3Gb RAM, Vista SP1 32bit
TaskInfo showed that there was plenty of free RAM when the error occured.
Error in log:
23:12:27 VtApp: Feature extraction time: 1119.4
23:13:07 VtApp: IndexFeatures time: 40.5
00:03:25 VtApp: PredictImages time: 3017.4
02:35:32 VtApp: ChoosePairs+MatchPairs time: 9126.9
02:35:33 VtApp: Total feature matching time: 12146.4
02:35:37 HR test fail <>\ReconstructionState.cpp(662) hr(8007000e)
02:35:37 HR test fail <>\ReconstructionState.cpp(450) hr(8007000e)
02:35:37 HR test fail <>\Registration.cpp(976) hr(8007000e)
exception SynthPipeline.cpp(202) hr(0x8007000E)
exception CollectionUploader.cpp(341) hr(0x80004004)
Will installing 64bit OS help?
I’m frustrated
4 Comments Add a comment
This solves the problem
-
For lots of images with really dense overlap, the synther can find tons of matches. It tries to allocate some pretty big blocks of contiguous memory in the reconstruction phase, which appears to be the problem here. How many images were you uploading?
-
I managed to synth those 900 images by installing 64bit windows (Server 2008).
-
Awesome! how did it turn out?
-
It synthed for 9+ hours, but managed to complete.
I have mixed feelings. I synthed the inside of a tiny and very cluttered room where 3 people live. There was a lot of overlap but it didn't synth 100%. 2-3 little series were detached.
Some shots are at the right place but at the very wrong angle (like 2 parallel photos of a plane synthed to be perpendicular). These phosos look especially bad whe changing views. I tried to make nice 360 halo from a cup, but it didn't turn out good (Photosynth didn't understand that all that photos were shot "horisontally"). I'm embarassed by the synth's content, but for the sake of science here it is: http://photosynth.net/view.aspx?cid=c... -
Inappropriate?I seem to get this problem whenever I have number of photos with substantial (e.g., >70%). In one synth attempt, I have 182 photos with a reasonable amount of overlap - taken as a series of blimp photos over the interior of the crater at Rano Raraku (Easter Island). The photos are all different but certainly contain overlap. Ive tried weeding out photos to make them as different as possible but I consistently get the "out of memory" error. This happens on more than one machine (with Vista and XP) all with 4 gigs of RAM and plenty of disk space. Could photosynth blow a memory gasket when shared points become larger than some particularly limit?
I’m perplexed.
-
Inappropriate?I had the same problem. On my machine (a quad core with 2 gig RAM) running XP, I had to reduce number of photos from 700 to 440 (95% synthy) before it worked. The originals took up almost exactly 1 gig in the working version. In my attempts it ran out of memory at the reconstruction stage.
It worked out at the end, though!
http://photosynth.net/view.aspx?cid=C...
I’m very happy now!
-
Inappropriate?20GB of ram memory on a windows 2008 x64 isn't enough on a (very) large synth... :(
I’m frustrated
-
Inappropriate?clipo, can you post the end of the log file so I can see where it was when it ran out of memory? You can find it under %TEMP%\Photosynther\.
-
Inappropriate?Here is the end of the log file:
11:17:10 VtApp: Feature extraction time: 715.8
11:17:53 VtApp: IndexFeatures time: 42.6
11:30:32 VtApp: PredictImages time: 758.4
16:17:11 VtApp: ChoosePairs+MatchPairs time: 17199.3
16:17:11 VtApp: Total feature matching time: 17959.7
16:43:21 HR test fail <>\PSReconstructionState.cpp(228) hr(8007000e)
16:43:21 HR test fail <>\PSReconstruction.cpp(1156) hr(8007000e)
16:43:21 HR test fail <>\PSReconstruction.cpp(558) hr(8007000e)
16:43:22 HR test fail <>\PSReconstruction.cpp(35) hr(8007000e)
16:43:22 HR test fail <>\Registration.cpp(893) hr(8007000e)
16:43:22 HR test fail <>\Registration.cpp(979) hr(8007000e)
exception SynthPipeline.cpp(202) hr(0x8007000E)
exception CollectionUploader.cpp(341) hr(0x80004004)
I’m unsure
-
Inappropriate?This is the same issue Fduch is having. Unfortunately you are at the limit of what we can handle right now. One option is to try to reduce the amount of overlap some so you cover the same part of the scene with fewer images.
-
-
Inappropriate?Each point in the scene you want to reconstruct should be observed in at least 3 cameras. This corresponds to 50% overlap as a bare minimum. 60-75% overlap is more reliable.1 Comment Add a comment
This solves the problem
-
Isn't this conflicting with youre previous post.. "try to reduce the amount of overlap"...
-
Inappropriate?I'm curious, because no one seems to have asked this, and I THINK it might make a difference... how big are your image files? 200 small jpgs is one thing, 200 hi-def 20 megapixel images will be something else.1 Comment Add a comment
This solves the problem
-
Somewhere else this question was answered by someone from the staff:
Files are uploaded and displayed at full resolution. The process of synthing however is done with copies of the files that are shrunk to 1600x??? pxs. -
Inappropriate?I just tried 580 pictures on Pentium M 1,4GHz, 512MB RAM. It ran for 3 days and finished the "matching images" phase. But then I got: err=8007000E
_Three_ days!! (except for the times when the fan would have stopped me from sleeping)
the end of the log file:
22:55:03 VtApp: Uploading "dzi" file C:\DOKUME~1\JERTR~1\LOKALE~1\Temp\Photosynther\images\1.595.dziz (1396237 bytes).
22:55:17 VtApp: Upload finished
02:14:46 VtApp: PredictImages time: 16597.3
18:50:12 VtApp: ChoosePairs+MatchPairs time: 146115.8
18:50:40 VtApp: Total feature matching time: 162748.7
19:49:46 HR test fail <>\ReconstructionState.cpp(666) hr(8007000e)
19:49:46 HR test fail <>\ReconstructionState.cpp(450) hr(8007000e)
19:52:40 HR test fail <>\Registration.cpp(976) hr(8007000e)
exception SynthPipeline.cpp(202) hr(0x8007000E)
exception CollectionUploader.cpp(341) hr(0x80004004)
:-( I really looked forward to that synth :-(
I’m sad
-
Inappropriate?I just tried 551 pictures on the above mentioned Pentium M 1,4GHz, 512MB RAM. I ran out of memory again:
05:53:51 VtApp: PredictImages time: 9238.9
16:15:25 VtApp: ChoosePairs+MatchPairs time: 123694.0
16:15:45 VtApp: Total feature matching time: 132914.3
16:41:00 HR test fail <>\ReconstructionState.cpp(666) hr(8007000e)
16:41:00 HR test fail <>\ReconstructionState.cpp(450) hr(8007000e)
16:42:15 HR test fail <>\Registration.cpp(976) hr(8007000e)
exception SynthPipeline.cpp(202) hr(0x8007000E)
exception CollectionUploader.cpp(341) hr(0x80004004)
This time I was near the laptop when it ran the "Reconstructing Scene"-phase and I couldn't make out any problem? The RAM usage of the process repeatedly sank to 390MB and rose to 425MB. Then I left for a walk (16:30CEST) and when I came back I had ended up with the above quoted log file ending (16:46CEST). :-( -
Inappropriate?Same Issue,Tried my image 4 times now, its a large file I won't lie, its 760 pictures, Always died in the Extracting part, gets to about halfway each time and dies.
core duo 2 - 2.8ghz
1gb Ram
killed everything bar the windows process and task manager to watch the ram amounts used, topped out at 700mb then hovered at 500 mb for about an hour then crashed
I’m sad
-
Inappropriate?I have the same problem , I cant synth 180 or less photos 2,5 MB each, bt in the past over 300 pictures were running smoothly!? Can the problem be in the new version? BTW I have P4 3.0 Ghz 2GB Ram...1 Comment Add a comment
This solves the problem
-
Serious, can you confirm that 8007000E is the exact error message that you're receiving and that you're not running Windows xp SP2? (I really do mean SP2 not SP1 or SP3.)
I can't deny that you are really getting an out of memory error, but here's something you should understand:
1: It isn't the number of photos alone that will cause an out of memory error.
(It is how many image features (the parts of each image that Photosynth thinks it has a chance of recognising from different angles) there are in each image and how many times those features match between images. The number of image features per photo depends completely on what you took pictures of and the number of matches is controlled by how many photos you took of one part of the scene.)
2: It isn't the size of the photos that will cause an out of memory error. (Out of memory usually happens during 'Reconstructing Scene' which is where all the features that have been indexed and matched are then compared to each other to calculate where they must be in 3D. If there are too many matches for each feature then the math problem becomes too hard for your computer and the synth fails. The number of image features does not go up with higher resolution images because the synther always uses 1.5 megapixel versions of your photos to find the image features even though it is uploading the full size to be viewed later.)
This might explain why you successfully synthed over 300 images before but can't get 180 synthed now. Can you try running your old 300 image synth over again now to see whether something really has changed with the synther (or your computer) or if it's just the particular photos that you're using this time with your new synth that are giving Photosynth and you a rough time? -
Inappropriate?It just says "Photosynth ran out of memory", I don't get any number in the message. I'm using WinXp SP2, i also think that as soon as it generates all images, and starts to "Reconstruct Scene" or to "Extract image Features" the error occurs. Thanks for the info so far. Can it be that a problem in some of the previous synths could cause all others to be faulty as well, I tried to synth some of Hubble images (18000*18000 pixels each) together and it said that the images are too big, since then I can't get any other synth that has more than 10 pictures to work.
1 Comment Add a comment
This solves the problem
-
Okay, well sorry that you're having problems. Try reading this topic to see about a possible fix for the 'out of memory' error on Winxp SP2. (Basically you need to install either:
1: Windows Imaging Component
2: the very latest Windows Live Photo Gallery or
3: Windows XP SP3.) -
Inappropriate?Can I later add some more images to an already "synthed" synth.1 Comment Add a comment
This solves the problem
-
Not in the sense of going to the site and adding new photos to an existing synth, no. If you still have the photos from the original synth on your computer, you can make a new synth with the old photos plus new photos to fill in the gaps between the original pictures.
If you do this, the 'calculation' part of making the new synth will take as long as normal, but it will figure out which photos you've already uploaded to the site and only spend time uploading the new photos so the upload should be a good bit shorter than normal, depending on the number of new photos that you're including in the new synth. -
Inappropriate?Thank you for all your help. I finally uploaded it by gradually adding more and more images until I was satisfied with the result. You can see the result :
http://photosynth.net/view.aspx?cid=7...
(If it doesn't work by clicking on it just copy it into the address bar :) ).
1 Comment Add a comment
This solves the problem
-
It works by clicking on it. =]
I'm glad you got to a point that you were satisfied with the result, but I also wish that I were more convinced that your problem was solved. Did you try installing any of the above three pieces of software that I linked to?
EMPLOYEE
EMPLOYEE
EMPLOYEE
