 |
|
|
|
|
|
 |
| ||||||||
 |
 
|
|
|
|
|
|
|
|
|
| ||||||||
|
|
| 
| User list | You are not logged in.
Pages: 1
APP 2.0.6 (64-bit) trial.
Win7-64
By mistake, I had APP do a "auto folder detect" on a folder with 300 .dng's with about 25 panos. I meant to have it do "folder detect" on the .jpg's that were generated from the dng's.
Anyway, about half-way through, APP hung (not responding message from o/s) and then gave a message about the temp file not having enough space.
Hmmmmm .... the drive that was designated for Temp is about 250gb, with about 110gb free. There are 1347 .tif files in H:\Temp, with a total of about 40gb in use.
Seems like a bug, but perhaps I did something wrong. I think this has happened several times before. I didn't get a "BugSplat" popup this time.
The "official" TEMP folder for Win7 is G:\Temp, which has about 50gb free.
Offline
I didn't watch the TEMP file while the "auto folder detect" was being done. I suppose I could do that and see if it is repeatable ... but that would take time that I'm kind of in short supply right now.
Seems like a good test-case for APP q/a .... have a situation with "auto folder detect" with .dng's so that gb's of .tif's were generated.
What happens with APP's TEMP folder is exhausted of disk space? Does it handle it gracefully? BugSplat? Or hang with somewhat misleading error message showing up a minute or so later?
Offline
hankkarl wrote:
APP takes a ton of temp space, and will free it up. Did you look at the amount of the drive used when APP was working?
I tried again with generated .jpg's rather than .dng's. The folder has a total of about 730 .jpg's, with about 90 panos between 2 and 7 files, 27 between 8 and 18, and a 20 image pano, and a 22 image pano. It's quite a few panos, but each individual pano seems of rather modest size.
During folder detect, APP hung doing the 97th pano (which was 9 images). There was no BugSplat. After a minute or so, it put up the error message:
"Unable to create the error report. Please verify that there is enough space in your TEMP folder."
I did watch the TEMP folders for the o/s and the designated TEMP folder for APP. Since .jpg's rather than .dng's were involved, neither changed as APP was doing folder detect (24gb in o/s temp, and 155gb for APP temp).
Seems like a bug. Perhaps a limit of about 100 panos in "auto folder detect"? The workaround seems to be having fewer panos in a folder. I am now splitting folders when I have a lot of small panos.
I did find that APP still hangs if I do the "auto folder detect" in two phases, but during the same "session". I had it do "auto folder detect" for the first 50 or so, and it was fine. Then I removed the left side for the "Groups", but left the right side for "Panos". The ideas was to keep the Group# in the file name in the actual sequence. This caused APP to hang. I don't recall if it was the 97th group or not.
I'm attaching a screen shot of APP while hung.
Last edited by l_d_allan (2010-03-03 14:47:06)
Offline
* We don't have any internal limit of panorama detection. The fact that it happened around 100 panoramas is just a coincidence.
* "Unable to create the error report. Please verify that there is enough space in your TEMP folder." : doesn't refer to APP temp folder, but system temp folder.
There is something there that used all the space and prevent the crash handler to work.
* each panorama in the right column has a cost in memory ( between 1 and 5 MB ). So having 100 panoramas opened means 200 to 500 MB used in memory. Be aware of that. Opening the editor on a panorama takes a lot of memory too ( 20 to 100 MB per panorama ). When just displayed on right column, it's far less of course.
Offline
If your out of space then just disable hibernate if you have vista or 7.
turning hibernate off gets you almost 2gb free!
Offline
Pages: 1