mapbox / mapbox-studio-classic

https://www.mapbox.com/mapbox-studio/
BSD 3-Clause "New" or "Revised" License
1.14k stars 229 forks source link

Windows 8.1/mapbox-studio-win32-x64-v0.2.5 Crash #1227

Open cwodwrth opened 9 years ago

cwodwrth commented 9 years ago

So Mapbox Studio crashed while I was trying to save my project, and now it just loads up, does the spinning wheel, and crashes. I've rebooted, uninstalled/reinstalled, nothing is working. Any thoughts?

Here is my error when running from the cmd line:

C:\Program Files\mapbox-studio>[1272:0304/133239:INFO:renderer_main.cc(211)] Renderer process started [4628:0304/133240:INFO:CONSOLE(0)] <Wed, 04 Mar 2015 19:32:40 GMT> Mapbox Studio exited with 8. [3892:0304/133240:ERROR:gles2_cmd_decoder.cc(9602)] Context lost because SwapBuffers failed. [3892:0304/133240:ERROR:gles2_cmd_decoder.cc(3952)] Error: 5 for Command kSwapBuffers [3892:0304/133240:ERROR:gles2_cmd_decoder.cc(9845)] Exiting GPU process because some drivers cannot reset a D3D device in the Chrome GPU process sandbox.

springmeyer commented 9 years ago

@cwodwrth - thanks for the report and sorry about the trouble. Can you:

1) Describe your project more so I can get some ideas about why it crashed? Is it a "source" or a "style"? If a "source" then what kind of data format and size of data were you loading in? If a "style" then what sort of styling were you doing before it crashed?

2) To fix the startup issue, find the .mapbox-studio/app.db file inside your user directory (aka %USERPROFILE%) and delete the app.db. This file stores the last project edited and because your project crashed this is likely preventing Studio from being able to start. If you delete the file then the next time you open studio it should open okay (and only crash when you try to navigate to the project again). HINT: if you do navigate to the project again and it crashes, then delete the app.db again.

cwodwrth commented 9 years ago

Sorry, I was saving my Style - I had just changed the color of a variable using the color picker and saved, and it just hung so I had to force close it.

It's now working again, after running it from the cmd line and crashing, I restarted from the shortcut and it started working again, so apparently something changed unbeknownst to me and it's back to working!

springmeyer commented 9 years ago

@cwodwrth - okay, interesting. I've not heard another report of a case like this. So can you keep a close eye on this and if it happens again post back here with additional details?

cwodwrth commented 9 years ago

Yes, of course. Thanks for addressing this so quickly.

stvno commented 9 years ago

I have the same problem, I was trying to create a postgis source from a 16M buildings database and it crashed while trying to preview the datasource. Afterwards I couldn't get it working, I have restarted the computer, removed and reinstalled Mapbox Studio to no effect.

Windows 7 64bit, mapbox studio 0.2.7

error when starting from commandline: C:\Program Files\mapbox-studio>[7604:0422/165652:INFO:renderer_main.cc(211)] Renderer process started [7420:0422/165654:INFO:CONSOLE(0)] <Wed, 22 Apr 2015 14:56:54 GMT> Mapbox Studio exited with 8. [3980:0422/165654:ERROR:gles2_cmd_decoder.cc(9602)] Context lost because SwapBuffers failed. [3980:0422/165654:ERROR:gles2_cmd_decoder.cc(3952)] Error: 5 for Command kSwapBuffers [3980:0422/165654:ERROR:gles2_cmd_decoder.cc(9845)] Exiting GPU process because some drivers cannot reset a D3D device in the Chrome GPU process sandbox.

stvno commented 9 years ago

After some experimenting I discovered that removing app.db.compacted did the trick.

First I removed app.db, which made it possible to start mapbox studio once, and produced the above error the next times. Removing app.db.compacted allowed me to use the original app.db (which I had copied elsewhere).