> I have researched the problem in detail. The java executable on windows
> uses just 256KB of stack size instead of the default 1MB stack size. In
> this situation putting buffers of 100KB (SVN_STREAM_CHUNK_SIZE) becomes
> a problem. There are some functions putting 1 or 2 buffers on the stack.
> Other functions getting this kind of buffer space from an apr pool. To
> solve Marks problem, we could either reduce the buffer size to 90KB or
> take the space from the pool. Since both ways are out of my commit
> area, I would like to have some input, which way to go for working out a
> patch.
It would be great if you could figure out a way to move these to the heap.
I have done a lot of research, and there is no realistic way to increase
the stack size for Java on Windows. The only way it can be done is to use
a binary editor to edit the EXE.
If the memory you mentioned cannot be allocated from the heap, a frequent
suggestion I saw was to start a new thread/process and run the code in
that. These suggestions were assuming there was a way to control the stack
size of that new thread/process. I have no idea if this is feasible, but
it might be an alternative.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun May 8 14:19:46 2005