Re: mochalua heap memory issues?

[Raymond Jacobs <raymondj@...>]

I have some test files but unfortunetly I wont be able to deliver them until after the weekend at the soonest, sorry.

The -key- issue is not to feed mochalua (or anything) potentially corupt data; the big issue is that with what mochalua expects for byte data (it being in a String type) makes it 'very' easy to wrongly convert your binary data and not even know it.

I have found that taking a byte[] and manually converting it to a char[], byte by byte; and using that char[] to init the string seems to work fine; I have read online that new String(byte[]) is particularly insidious about it's conversion.

-Raymond

On Fri, Nov 6, 2009 at 9:09 AM, Kristofer Karlsson <kristofer.karlsson@gmail.com> wrote:

Can you provide a preferably minimal test case to reproduce the problem?
Seems like it would be a memory leak.

I would personally like to verify it in Kahlua to see if it suffers from the same potiential problem as Mochalua.

/Kristofer

On Thu, Nov 5, 2009 at 4:22 PM, Raymond Jacobs <raymondj@gmail.com> wrote:

Greetings all,

I hope it is alright posting about mochalua here;
I couldn't seem to find a good spot to talk about mochalua elsewhere.

I've recently started using mochalua in my Java 1.6 SE application;
and while I can get small, trivial lua code to run; a larger multi-function script
results in a Java out of heap memory exception.

I've tried to set the xms and xmm VM arguments to up the JVM heap size but nothing seems to be helping.

I am using luaL_loadstring to load the data;

has anyone had similar issues when working with mochalua?

Any information is appreciated,

Thanks,

Raymond Jacobs
Owner,
Ethereal Darkness Interactive
www.edigames.com