neko icon indicating copy to clipboard operation
neko copied to clipboard

Uncaught exception - alloc.c(177) : max_string_size reached

Open mynameGY opened this issue 5 years ago • 10 comments

How to deal with it please help me

mynameGY avatar Dec 28 '18 07:12 mynameGY

Hi @mynameGY , can you please add more details. What neko code are you running, can you post the source?

ppenzin avatar Dec 28 '18 19:12 ppenzin

I used haxeflixel to build flash and failed. When I delete some of the resources under my assets, I can build again successfully.

Here's the details error :

Called from ? line 1 Called from CommandLineTools.hx line 1385 Called from CommandLineTools.hx line 25 Called from CommandLineTools.hx line 126 Called from CommandLineTools.hx line 604 Called from lime/project/PlatformTarget.hx line 70 Called from lime/tools/platforms/FlashPlatform.hx line 260 Called from lime/tools/helpers/FlashHelper.hx line 872 Called from lime/tools/helpers/FlashHelper.hx line 685 Called from format/swf/Writer.hx line 60 Called from format/swf/Writer.hx line 1425 Called from format/tools/Deflate.hx line 33 Called from /usr/lib/haxe/std/neko/_std/haxe/zip/Compress.hx line 48 Called from /usr/lib/haxe/std/haxe/io/Bytes.hx line 457 Uncaught exception - alloc.c(177) : max_string_size reached Build halted with errors (haxelib.exe).

mynameGY avatar Jan 02 '19 09:01 mynameGY

Looks like the string describing resources becomes too long to be allocated in Neko. You would probably have to report the issue for the tool that is getting this error.

@ncannasse, @andyli, what do yo think?

ppenzin avatar Jan 02 '19 14:01 ppenzin

This is some issue related to lime and should be handled at lime level. It seems weird that there is a 256MB limit to resources as I think some projects have more than that.

ncannasse avatar Jan 02 '19 14:01 ncannasse

I want to increase the limit of more than 256M. How can I solve this problem?

mynameGY avatar Jan 03 '19 02:01 mynameGY

This needs to be fixed in Lime (openfl/lime, right @ncannasse?). To get help with fixing it you should report this issue in the lime repository.

ppenzin avatar Jan 04 '19 04:01 ppenzin

Okay, thank you very much @ppenzin .I really look forward to ncannasse's help. Thank @ncannasse in advance.

mynameGY avatar Jan 04 '19 09:01 mynameGY

@ppenzin yes, this is somewhat lime specific. Maybe recompiling and running the build tool with HashLink would prevent this error from occurring.

ncannasse avatar Jan 04 '19 15:01 ncannasse

Are strings allocated differently in HashLink? I haven't gotten to building it yet since I got stuck with FreeBSD build of Haxe :)

ppenzin avatar Jan 05 '19 06:01 ppenzin

Well you don't have the 256MB limit.

On Sat, Jan 5, 2019 at 7:18 AM Petr Penzin [email protected] wrote:

Are strings allocated differently in HashLink? I haven't gotten to building it yet since I got stuck with FreeBSD build of Haxe :)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/HaxeFoundation/neko/issues/189#issuecomment-451631657, or mute the thread https://github.com/notifications/unsubscribe-auth/AA-bwMDK3zNDTnTP4ZGB84Ivy445U5A1ks5vAEPLgaJpZM4Zjj3A .

ncannasse avatar Jan 05 '19 16:01 ncannasse