AFP2PDF Size Limitation

[jsquizz]

Just wondering if anyone has reached an input filesize limitation with AFP2PDF. Is anyone currently using AFP2PDF to convert very large AFP files (2-3 GB) to PDF?

I am getting a core dump when this is attempted  :-[ ::)

[Justin Derrick]

I would imagine you're blowing out the size limit of PDF documents.  Can you get coredumps/traces from the conversion?

[Alessandro Perucchi]

From which platform are you doing such transformation?

If you are on Windows, then since the AFP2PDF is in 32bit, then "maybe", you have reached a problem... which could not be there with the Linux/Unix version, which is 64bits.
Otherwise... no idea...

[jsquizz]

AIX 5.3 :(

[Alessandro Perucchi]

did you check the "ulimit" ? maybe your have there some "limitation" on your user...

[jsquizz]

THANK YOU ALLESANDRO! I said this but its glad to see someone backs me up

whatever one that is (coredumps) isn't set to unlimited.

[Justin Derrick]

ulimit on coredumps only means you get bigger core files.  It doesn't change how much memory is available to your process.

What other changes did you make to the limits?

[jsquizz]

none as of yet. Heres the current ulimits:

:user@aixbox:# ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 4194304
memory(kbytes) unlimited
coredump(blocks) 2097151
nofiles(descriptors) 2000

:user@aixbox:# ulimit -Ha
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 4194304
memory(kbytes) unlimited
coredump(blocks) unlimited
nofiles(descriptors) unlimited

[Alessandro Perucchi]

try

Code Select Expand


ulimit -s unlimited


this is to put the STACK to unlimited... sometimes the stack limitation can cause such problem...

[Justin Derrick]

And change your coredump limit back to something reasonable like 10 or 20MB.  You can accidentially fill a filesystem writing out core-dumps from processes that run out of memory...

[jsquizz]

Haven't made any changes as of yet.