[mkgmap-dev] Error in memory calculation

Tue Feb 11 15:29:20 GMT 2020

Hi Gerd, I'm not sure about the combination of summing the usage but using
the biggest heap. I would have thought it would be better to either use the
biggest usage and biggest available space, or the sum of usage and sum of
available space. However, the documentation on what exactly is returned by
these functions is rather sparse.

Regards,
Mike 

-----Original Message-----
From: Gerd Petermann [mailto:gpetermann_muenchen at hotmail.com] 
Sent: 11 February 2020 07:29
To: 'Development list for mkgmap' <mkgmap-dev at lists.mkgmap.org.uk>
Subject: Re: [mkgmap-dev] Error in memory calculation

Hi Mike,

the original problem with *.mp file remains. What do you think about my
patch?

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Mike
Baggaley <mike at tvage.co.uk>
Gesendet: Dienstag, 11. Februar 2020 01:08
An: 'Development list for mkgmap'
Betreff: Re: [mkgmap-dev] Error in memory calculation

>So, this is really a very special case. It happened for John Thorne who is
>using several rather small *.mp files as input, but I think it can also
>occur for others when the first input file is a typ file in *.txt format.

I can't see any reason for typ file compilation to be included in the list
of files to be processed as separate tasks, as the time taken is negligible.
If typ files were  processed immediately, then there would not be an issue
with typ compilation being used for the calculation of a memory requirement
which is unsuitable for subsequent img file generation.

Regards,
Mike

_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev