Closed nickponline closed 10 years ago
We'll need to get a backtrace out to know what happened. On linux you do that by first doing:
ulimit -c unlimited
Then, run the process again to trigger the crash. A core
file should then show up in your working directory.
Then do:
sudo apt-get install gdb
gdb which node
core
thread apply all bt
The thread apply all bt
might need to be scrolled. Capture all the output and share in a gist then link here.
Here's the core: https://gist.github.com/nickponline/cad5ea06479b086c60c1
Here's the thread bt: https://gist.github.com/nickponline/d4dd2e2be39fcb3ac4e1
On Thu, May 29, 2014 at 11:25 PM, Nicholas Pilkington < nicholas.pilkington@gmail.com> wrote:
On it
On Thu, May 29, 2014 at 11:24 PM, Dane Springmeyer < notifications@github.com> wrote:
We'll need to get a backtrace out to know what happened. On linux you do that by first doing:
ulimit -c unlimited
Then, run the process again to trigger the crash. A core file should then show up in your working directory.
Then do:
sudo apt-get install gdb gdb which node core thread apply all bt
The thread apply all bt might need to be scrolled. Capture all the output and share in a gist then link here.
— Reply to this email directly or view it on GitHub https://github.com/mapbox/tilemill/issues/2338#issuecomment-44618852.
With nodejs it gives similar output
ubuntu@ip-10-182-57-31:~/tilemill$ which nodejs
/usr/bin/nodejs
ubuntu@ip-10-182-57-31:~/tilemill$ gdb /usr/bin/nodejs core
GNU gdb (Ubuntu 7.7-0ubuntu3.1) 7.7
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/nodejs...(no debugging symbols found)...done.
warning: core file may not match specified executable file.
[New LWP 23445]
[New LWP 23447]
[New LWP 23450]
[New LWP 23449]
[New LWP 23440]
[New LWP 23441]
[New LWP 23451]
[New LWP 23448]
[New LWP 23444]
[New LWP 23439]
[New LWP 23438]
[New LWP 23442]
[New LWP 23446]
[New LWP 23443]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `tm-123123123_orthomosaic_1da7a1.mbtiles '.
Program terminated with signal SIGABRT, Aborted.
£0 0x00007f8a052a8f79 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) quit
Tilemill was installed (today) as:
apt-get update
apt-get install -y python-software-properties python g++ make
add-apt-repository ppa:chris-lea/node.js -y
apt-get update
apt-get install -y nodejs
git clone git@github.com:mapbox/tilemill.git
cd tilemill
npm install
ubuntu@ip-10-182-57-31:~$ node -v
v0.10.28
ubuntu@ip-10-182-57-31:~$ nodejs -v
v0.10.28
ubuntu@ip-10-182-57-31:~$ npm -v
1.4.9
@nickponline thanks a lot for that backtrace. This is a problem in the latest TileMill which pulls in node-mapnik at 1.4.4 or 1.4.5. You can workaround it by downgrading to node-mapnik 1.4.3 by editing the package.json
and then doing rm -rf node_modules/mapnik && npm install mapnik@1.4.3
. Tracking a fix at https://github.com/mapnik/node-mapnik/issues/265
Thanks Dane.
On Fri, May 30, 2014 at 5:09 PM, Dane Springmeyer notifications@github.com wrote:
@nickponline https://github.com/nickponline thanks a lot for that backtrace. This is a problem in the latest TileMill which pulls in node-mapnik at 1.4.4 or 1.4.5. You can workaround it by downgrading to node-mapnik 1.4.3 by editing the package.json and then doing rm -rf node_modules/mapnik && npm install mapnik@1.4.3. Tracking a fix at mapnik/node-mapnik#265 https://github.com/mapnik/node-mapnik/issues/265
— Reply to this email directly or view it on GitHub https://github.com/mapbox/tilemill/issues/2338#issuecomment-44712074.
Thanks for the report and workaround. Just ran into this as well, and the workaround seems to work. Just clarifying for anyone else that the line to change in package.json is from:
"mapnik": "~1.4.4",
to
"mapnik": "1.4.3",
This problem is now finally fixed in master tilemill by using the new node-mapnik release: https://github.com/mapbox/tilemill/commit/ae64a113dac7c7dfa4df86baf918cc75e1c01c22. More info on the backstory at https://github.com/mapnik/node-mapnik/issues/265 and https://github.com/mapnik/node-mapnik/issues/251
So if I am running into this problem trying to export a map as a PDF using TileMill on OSX , what should I do?
(I'm a complete mapping newbie)
@diegozaks - I don't think you are hitting this exact issue. Can you please create a new issue and in that issue describe in detail:
Done! https://github.com/mapbox/tilemill/issues/2353
I appreciate any help!
Diego Zaks
+1 (917) 940-1373 diegozaks.com
On Mon, Jun 16, 2014 at 2:39 PM, Dane Springmeyer notifications@github.com wrote:
@diegozaks https://github.com/diegozaks - I don't think you are hitting this exact issue. Can you please create a new issue and in that issue describe in detail:
- What TileMill version / How did you install it
- What OS X version are you running
- Do SVG exports work? Do PNG exports work?
- What do the logs show after trying a failed PDF export ( https://www.mapbox.com/tilemill/docs/manual/usage/#mac_os_x)
- Does your map use labels?
— Reply to this email directly or view it on GitHub https://github.com/mapbox/tilemill/issues/2338#issuecomment-46217289.
https://www.dropbox.com/s/dn6o22e7g7qdd9u/Screenshot%202014-05-29%2023.04.14.png