Re: [MiNT] MiNT 1.19 and malloc size limitation?

[Rajah <rajah@triplea.fr>]

On the FireBee and its 512 MB, it's very hard to use all TT-RAM. And I 
the size for mxallocs where huge but decent (not false value). For 
example, file size 70 MB, mxalloc worked with MiNT 1.18, and returned 
error with MiNT 1.19.

I'll try to look in the MiNT sources, but my time and knowledge are very 
limited.

Cheers,

Rajah

Le 22/03/2015 09:33, Alan Hourihane a écrit :
> Yes, there is something that limits m(x)allocs. The size of physical memory.
>
> Alan.
>
> On 22/03/15 00:54, Rajah wrote:
> > Hi,
> >
> > This parameter PROC_MAXMEM is not used (commented with #) in my
> > MINT.CNF file.
> > No memory limitation in Thing preferences for applications.
> >
> > So I repeat my question: is there something in latest MiNT that limits
> > m(x)allocs?
> >
> > I'm thinking again about it when iconv.ldg (1 101 535 Bytes), loaded
> > with ldg_load() (using malloc that failed?), but crashes when
> > ldg_free() is called, crashing the desk by cascade.
> >
> > Cheers,
> >
> > Rajah
> >
> > Le 05/02/2015 11:03, Vincent Rivière a écrit :
> > > On 04/02/2015 20:17, Pierre Ton-That wrote:
> > > > Speaking of MiNT changes, from 1.18 to 1.19, I noticed one can't malloc
> > > > very big blocks. There is a limitation (about 1 MB ?). Could not malloc
> > > > 70 MB (MegaBytes) for a very big file for download in one row.
> > > I suggest you to have a look at the PROC_MAXMEM variable in your
> > > MINT.CNF.
> > >
> > > #PROC_MAXMEM=4096