search

tilemill-project / tilemill

TileMill is a modern map design studio
https://tilemill-project.github.io/tilemill/
BSD 3-Clause "New" or "Revised" License
3.12k stars 527 forks source link

Tilemill crashes on start #2488

Open IReese opened 9 years ago

IReese commented 9 years ago

Hi Mapbox,

Regarding the newest build of Tilemill (tilemill-win32-x64) for Windows x64. I am working on:

Windows 7 Enterprise Intel(R) Core(TM) i7-3687U CPU@ 2.10GHz 16.0 GB RAM 64-bit

Upon start-up of Tilemill I receive the following error, followed by a crash:

C:\Program Files\TileMill>[5972:0311/194514:INFO:renderer_main.cc(211)] Renderer process started [5936:0311/194521:INFO:CONSOLE(0)] <Wed, 11 Mar 2015 06:45:21 GMT> TileMill exit ed with 0. [2600:0311/194521:ERROR:gles2_cmd_decoder.cc(9602)] Context lost because SwapBuf fers failed. [2600:0311/194521:ERROR:gles2_cmd_decoder.cc(3952)] Error: 5 for Command kSwapBu ffers [2600:0311/194521:ERROR:gles2_cmd_decoder.cc(9845)] Exiting GPU process because some drivers cannot reset a D3D device in the Chrome GPU process sandbox.

I do get a clean start, once, upon a restart of Windows, followed by successive crashes.

bsudekum commented 9 years ago

Same issue occurring in mapbox-studio, ref: https://github.com/mapbox/mapbox-studio/issues/1227

wilhelmberg commented 9 years ago

@IReese

Please try the following:

Wait till you see [tilemill] Started [Server Core:20009].. Open a recent version of Chrome or Firefox on http://localhost:20009/

Does it work now?

bsudekum commented 9 years ago

@BergWerkGIS I believe @IReese is using the pre-release tilemill-atom build here. TileMill be located instead at C:\Program Files (x86)\tilemill\resources\app

@IReese I also created a new build with GPU acceleration disabled on windows. Mind giving it a try?

https://s3.amazonaws.com/mapbox/tilemill/build/tilemill-win32-x64-atom.exe

springmeyer commented 9 years ago

@BergWerkGIS @bsudekum - I was able to debug this specific problem with @IReese at FOSS4G. The problem is that the windows build @IReese was provided by @bsudekum was leaving two node.exe processes running when the app was closed. This was preventing startup on the second time the app tried to launch. So @bsudekum - the next action is to replicate, fix this, and send another test build to @IReese.

bsudekum commented 9 years ago

@IReese @springmeyer I think I might have solved this issue with https://github.com/mapbox/tilemill/commit/9426752bfc5a1878f2e723edb704086fca7b4feb. I just tested this on a windows 7 x64 machine and the all child processes are exiting correctly. The reason it was failing on startup is because child process were still running after exiting.

The background on this is that .kill('SIGINT') is not properly handled on windows. This is where the package readline comes in which allows for SIGINT support on windows.

If you'd like to test it, builds can be found at https://gist.github.com/bsudekum/b4606871250d9d834b3d

springmeyer commented 9 years ago

@IReese - yes, would be great if you could test the above build and let us know how it works. Great work @bsudekum. I also added some comments and questions inline in the commit.

IReese commented 9 years ago

I’m on it, altho it may take a few days for me to get to it.

From: Dane Springmeyer [mailto:notifications@github.com] Sent: Wednesday, 25 March 2015 6:38 a.m. To: mapbox/tilemill Cc: Ian Reese Subject: Re: [tilemill] Tilemill crashes on start (#2488)

@IReesehttps://github.com/IReese - yes, would be great if you could test the above build and let us know how it works. Great work @bsudekumhttps://github.com/bsudekum. I also added some comments and questions inline in the commit.

— Reply to this email directly or view it on GitHubhttps://github.com/mapbox/tilemill/issues/2488#issuecomment-85612623.

This message contains information, which may be in confidence and may be subject to legal privilege. If you are not the intended recipient, you must not peruse, use, disseminate, distribute or copy this message. If you have received this message in error, please notify us immediately (Phone 0800 665 463 or info@linz.govt.nz) and destroy the original message. LINZ accepts no responsibility for changes to this email, or for any attachments, after its transmission from LINZ. Thank You.