Issue Don't know where to start: "Cannot enlarge memory arrays"

Questions
1

Hi, so I have a project that gives me a blank black screen. Works well when building and shows up when building in Windows but not in HTML build.

A fair warning, I’m lost on this one, and at this point I’d need help just figuring out where to start.

The warning I get is:
Cannot enlarge memory arrays. Either (1) compile with -s TOTAL_MEMORY=X with X higher than the current value 268435456, (2) compile with -s ALLOW_MEMORY_GROWTH=1 which allows increasing the size at runtime, or (3) if you want malloc to return NULL (0) instead of this abort, compile with -s ABORTING_MALLOC=0

I’ve uploaded it as well here
Uploaded Project

Some additional notes:

-> I tried to amp up the heap memory to 9999999999, but same black screen
-> I haven’t tried “ALLOW_MEMORY_GROWTH=1” since I don’t know where to assign that value

Anyhow, any help is much appreciated even if just in the right direction.

All the best,
Alfredo

2

Do you have a lot of large textures or other large resources? You can generate a build report by checking the Generate Build Report checkbox in the Bundle dialog. Generate one and share it here.

3

Hi, yeah you might be spot on. And come to think of it, that is a recent change.

The report uploaded here:
Report

4

As I’m reading the report, I’m trying to figure out the “texturec” that is being referred to as 170MB in the report.

Is that being dynamically created by the build? And if so, are the numbers amount of small images affect?

Worth mentioning, I’ve imported a spine with bout 25 skins , so in total there are alomst 300 small body parts (but only about 10 used at the same time in run time)

1 Like
5

Yes, /main/background.texturec is 170Mb and it is either the output from an atlas or tilesource file. 170 means that it is huuuuge. You can see the dimensions of an atlas when you open it. Anything above 8kx8k pixels is really not recommended, and even less for mobile.

2 Likes