[mkgmap-dev] Commit r4702: show stacktrace when OutOfMemoryError occurs, helps to decide if maxjobs should be decreased or if one of the combiners is the problem
From Mike Baggaley mike at tvage.co.uk on Tue May 11 11:11:28 BST 2021
Hi Gerd, Would it not be better for the code to detect whether it is a combiner and adjust the message accordingly? Cheers, Mike -----Original Message----- From: svn commit [mailto:svn at mkgmap.org.uk] Sent: 11 May 2021 08:33 To: mkgmap-svn at lists.mkgmap.org.uk; mkgmap-dev at lists.mkgmap.org.uk Subject: [mkgmap-dev] Commit r4702: show stacktrace when OutOfMemoryError occurs, helps to decide if maxjobs should be decreased or if one of the combiners is the problem Version mkgmap-r4702 was committed by gerd on Tue, 11 May 2021 show stacktrace when OutOfMemoryError occurs, helps to decide if maxjobs should be decreased or if one of the combiners is the problem http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4702
- Previous message: [mkgmap-dev] Commit r4702: show stacktrace when OutOfMemoryError occurs, helps to decide if maxjobs should be decreased or if one of the combiners is the problem
- Next message: [mkgmap-dev] Commit r4702: show stacktrace when OutOfMemoryError occurs, helps to decide if maxjobs should be decreased or if one of the combiners is the problem
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list