[prev in list] [next in list] [prev in thread] [next in thread]
List: imagemagick
Subject: RE: BIG tiff to jpeg causing problems
From: Bill Radcliffe <BillR () corbis ! com>
Date: 2000-03-30 16:43:54
[Download RAW message or body]
It sounds like it ran out of disk space.
In most of my scripted application like this, I have started adding logic to
check for a certain amount of disk space before doing the conversion in
order to stay out of trouble. I'm sure that there are holes in the error
checking for this kind of thing. It's not something that we spend a lot of
time on.
Let us know if this is the issue and I'll try to recreate it on my end.
> -----Original Message-----
> From: David T-G [SMTP:davidtg@bigfoot.com]
> Sent: Thursday, March 30, 2000 5:15 AM
> To: ImageMagick mailing list
> Subject: BIG tiff to jpeg causing problems
>
> Hi, folks --
>
> I think I've hit on one of my problems (as some of you may recall from
> my posts regarding difficulties with 5.1.1); I may just be working with
> files that are too darned big. I have some 4M tif files that I'd like
> to convert to jpg, and I just can't seem to do it. It looks like I'm
> probably running out of temp space, from what I can tell.
>
> I let my PII-400 (256M) Win98 laptop churn away at the files last night,
> and it actually managed to convert one to a [6M] jpg file, but it left
> a full disk behind. My C:, where \tmp is located, has about 2.7G free
> and that was burned up like this:
>
> Volume in drive C is LAKE-C
> Volume Serial Number is 0D4C-1508
> Directory of C:\tmp
>
> MAG10C3 185,144,665 03-27-00 11:37p mag10C3
> MAG6001 185,144,665 03-27-00 11:38p mag6001
> MAG6072 190,298,833 03-27-00 11:38p mag6072
> MAG6075 197,615,377 03-27-00 11:38p mag6075
> MAG2375 185,144,665 03-30-00 12:07a mag2375
> MAG9201 185,144,665 03-30-00 12:09a mag9201
> MAG4133 185,144,665 03-30-00 12:26a mag4133
> MAGA2F0 185,144,665 03-30-00 12:32a magA2F0
> MAG392 190,298,833 03-30-00 12:39a mag392
> MAG7175 197,615,377 03-30-00 12:46a mag7175
> MAGE174 204,346,801 03-30-00 12:55a magE174
> MAG73B1 204,346,801 03-30-00 1:06a mag73B1
> MAG60F0 204,346,801 03-30-00 1:15a mag60F0
> MAG4 0 03-30-00 1:16a mag4
> MAG130 0 03-30-00 1:16a mag130
> MAG270 0 03-30-00 1:16a mag270
> MAG5334 0 03-30-00 7:05a mag5334
> 17 file(s) 2,499,736,813 bytes
> 0 dir(s) 112,648,192 bytes free
>
> That last one is from me trying to run identify on the resultant jpg; it
> puked and told me that the application had written two few scan lines (or
> something close; sorry). With that I got the idea to check on my temp
> space, since that's the same sort of message I'd gotten on my Linux box a
> few times.
>
> This was actually kicked off from a batch file, and the output directory
> on D: looked like:
>
> Volume in drive D is CHUNK
> Volume Serial Number is 3B61-1EEC
> Directory of D:\data\download\ZModem\murphy\win-511
>
> . <DIR> 03-27-00 11:35p .
> .. <DIR> 03-27-00 11:35p ..
> TIF2JP~1 SWP 12,288 03-30-00 12:11a .tif2jpg.bat.swp
> TIF2JPG BAT 439 03-30-00 12:11a tif2jpg.bat
> MURPH-~1 JPG 6,240,240 03-30-00 12:19a murph-01.tif.l.jpg
> MURPH-~2 JPG 0 03-30-00 12:26a murph-02.tif.l.jpg
> MURPH-~3 JPG 0 03-30-00 12:32a murph-03.tif.l.jpg
> MURPH-~4 JPG 0 03-30-00 12:38a murph-04.tif.l.jpg
> MURPH-~5 JPG 0 03-30-00 12:45a murph-05.tif.l.jpg
> MURPH-~6 JPG 0 03-30-00 12:55a murph-06.tif.l.jpg
> MURPH-~7 JPG 0 03-30-00 1:05a murph-07.tif.l.jpg
> MURPH-~8 JPG 0 03-30-00 1:15a murph-08.tif.l.jpg
> 10 file(s) 6,252,967 bytes
> 2 dir(s) 1,719.40 MB free
>
> As you can see, the first jpg file seems to have been successfully
> created. What gets me is that the other files have timestamps in the
> middle of the run of temp files -- could magick not be cleaning up after
> itself? That doesn't sound clean, but perhaps I simply need to modify my
> batch file to wipe c:\tmp after each convert...
>
> Once I was able to run identify (after clearing off c:\tmp), I got
>
> D:\data\download\ZModem\murphy\win-511>identify murph-01.tif.l.jpg
> murph-01.tif.l.jpg 4826x6394 PseudoClass 256c 6093kb JPEG 337.4u 5:38
>
> and I think it ought to be a real file. I haven't yet pointed Netscape
> at it to see if I got anything :-) Yes, it's clearly really big.
>
> Anyway, I also (previously, in fact) tried this adventure on our dual
> Celeron-400 (128M) Linux box, and filled up /tmp pretty quickly. We've
> had some other difficulties with 5.1.1 and so we stepped down to 4.2.9,
> but with not much luck; I was able to make jpg output files (and the first
> is the same size as this Win98 one, so I figure the results are the same,
> whether or not it's a viewable file), but cannot identify them:
>
> [zero] [8:06am] ~/www/private/murphy> identify *01*jpg
> identify: Memory allocation failed (murph-01.tif.l.jpg).
> identify: Missing an image file name.
>
> /tmp is *not* full this time. I'm stumped.
>
> I have not yet pointed my laptop in its Linux incarnation (with 4.2.0
> straight from SuSE) at the files; well, I did once but I got a seg fault
> (and real, true, actual system lockup!) and haven't yet tried to duplicate
> or analyze it.
>
>
> Anyway, that's the bug report, of sorts. Now that I have free space
> again, I'll probably try thumbnailing the first (only, so far) jpg file
> here on my laptop tonight; the goal is to get these somewhat smaller :-)
> I sure would like to be able to do all of this on the Linux box, though.
>
> TIA for anything anyone can provide...
>
> :-D
> --
> David T-G * It's easier to fight for one's
> principles
> (play) davidtg@bigfoot.com * than to live up to them. -- fortune
> cookie
> (work) davidtgwork@bigfoot.com
> http://www.bigfoot.com/~davidtg/ Shpx gur Pbzzhavpngvbaf Qrprapl
> Npg!
> The "new millennium" starts at the beginning of 2001. There was no year
> 0.
> Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh*
>
***********************************************************************
To remove yourself from this mailing list, send mail to:
majordomo@wizards.dupont.com
Include the following command in the body of your message:
unsubscribe magick
***********************************************************************
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic