| Subject: | Re: JNI intBitsToFloat return error | |
|---|---|---|
| From: | phon...@mobileandembedded.org (phon...@mobileandembedded.org) | |
| Date: | Mar 28, 2007 12:47:31 pm | |
| List: | net.java.dev.phoneme.advanced | |
Bob,
I'm glad to hear that someone is experimenting with this code. As for the
OutOfMemoryError issues, that could simply be because you aren't giving it
enough memory. Please download the mr2 bundle which contains a runtime
resizable heap. It should for the most part just build. You may have to
reapply the patches you've done if it does not build successfully.
When you run, try specifying -Xmx20M or whatever Java heap size is needed by
Tomcat and your apps. In JavaSE, I think (but am not sure) the default max heap
is 64M for the client VM. That means when you run your app on a PC, it will
grow up to 64M as needed. It may not actually need that much in practice. For
your ARM device, with phoneME Advanced MR2, you'll get the same growable heap
feature. Since your device is limited to 64M, I don't think a max heap of 64M
is reasonable. Hence, I suggest trying -Xmx20M. You can try something smaller
or larger as well. The max size specified does not mean that that amount of
memory will actually be used. In practice, it may use less. By default, the
heap size is only 5M which is probably too small to run Tomcat and your app.
That's why you are seeing the OutOfMemoryError.
Let me know if you are still seeing problems. Alternatively, try running with
-Xmx50M or some very large value. Then while your app is running, run top in a
separate linux terminal to check the memory usage of CVM. Note that top reports
both the reserved memory as well as the actual memory usage. You only need to
be concerned about the actual memory usage. Use that as a guide as to how much
to set your max heap size to.
Mark [Message sent by forum member 'mlam' (mlam)]





