Support Staff2 Posted by Will White on 12 Oct, 2011 10:55 PM
You may be experiencing
this issue. Try vacuuming the sqlite databases and loading the
project again. If that doesn't work, can you look in
~/Library/Logs/DiagnosticReports/ for a crash report
Thanks for the suggestions. I vacuumed both my spatial data and
related table using BASE. Unfortunately, it didn't make a
difference in the project - still no response from server, and a
maxed out processor until I kill TileMill.
For the crash logs, I found loads for NODE - does that help? I
had 9 today, so I zip'd them up in case it's useful for you to
Thanks, that is encouraging to hear. I can't post this data
here, but I'll see if I can get it to you directly.
Getting back to my original query - are there any options for
users to get more information on chasing these problems? I usually
test in QGIS or other GIS package to validate - but SQLite is a
little curious as it doesn't seem to enforce things like data
types. Would you recommend that fields always have "types"
(VARCHAR, INT, etc.), what other kinds of integrity checks make
sense when the data is not behaving with TileMill.
I'm happy to hear there is a new update coming, but I was hoping
to add a few tools of my own to diagnose these issues (debug mode,
verbose logging, etc.).
Appreciate the help and I'll look into sending you that
Support Staff7 Posted by Dane on 15 Oct, 2011 01:21 AM
Thanks for the effort in the data - see your email and will take
a look as soon as I can next week.
Re: your original query - yes agree SQLite is quite "curious" -
it's defaults are very forgiving but its errors also often very
silent. Datatypes actually are independent in sqlite of how they
are declared and rather they are handled though "type affinity" -
Regarding your own debugging tools - in your case the console
was the right place to look. Those crashes are a direct result of
this sqlite bug. However you also mention pegged CPU, which sounds
potentially like another issue. For a pegged CPU/hung app the
thing to do ( I see you are on a mac, right?) is to open up
Activity monitor, find the "node" process and sample it. The result
will not make a ton of sense to you but if you post it back here I
can help interpret it and it will show exactly what TileMill is
doing when it is hung or not behaving correctly.