hi thomas,
i managed to get the jpeg transcoder working by just setting the KEY_AOI to
the exact size of the bounding box of my view on the canvass.earlier ,since
i didnt mention the AOI ,i presume that batik is trying to convert the whole
canvas into jpeg image which is blowing up memory.i am not
GVS Srinivas wrote:
i managed to get the jpeg transcoder working by just setting the KEY_AOI to
the exact size of the bounding box of my view on the canvass.earlier ,since
i didnt mention the AOI ,i presume that batik is trying to convert the whole
canvas into jpeg image which is blowing up memory
Chris Faulkner wrote:
Thanks for sticking with me on this, Thomas. That's a nuisance for me - I
can't go back to 1.3.1 for lots of reasons, but I could go for a later
version of 1.4. Does anyone else have any experience of this - does it work
with other flavours of 1.4 ?
Can you file a bugzill
hi
thomas,
thanks
for the reply.. suggest me how can i implement it. willing to
contribute.
regards
Yoga
Hi,
I know that you can use a parameter to give the java virtual machine more memory
at startup, using the -Xmx256M flag.
When I am using the alternative startup version, using the non-compiled cvs
version ("sh build.sh squiggle"), can I give the java virtual machine more
memory as well?
Modyfyi
Andreas Neumann wrote:
Hi,
I know that you can use a parameter to give the java virtual machine more memory
at startup, using the -Xmx256M flag.
When I am using the alternative startup version, using the non-compiled cvs
version ("sh build.sh squiggle"), can I give the java virtual machine more
m
>If you poke into the build.xml file and find the target with
> name="squiggle"
> you will see a 'jvmarg' tag line with a commented out -Xmx option.
yes - that helped! I really appreciate your quick and competent answers!
Thanks a lot,
Andreas
--
The only thing that stands between a man
