Interesting problem I just encountered: I started a new chilipeppr/grbl session, and dragged a nc file onto the web page to load it. Even though it’s only 5 megs, for some reason now Chilipeppr won’t display it. I get continual timeout messages, and the “loading workspace” seems to hang forever, until final crash (Chrome says something about “oh snap”).
Since chilipeppr appears to default to open the last file you were working on when opened (which I wish wasn’t the case) , now whenever I open it, it just hangs trying to load that file.
I’d made a custom workspace a while back to always load the chilipeppr cut, but it seems to be experiencing different, unrelated issues.
What can I do to get Chilipeppr back to normal again?
Thanks!
Maybe the cache is full? In the “Workspace TinyG” box click the folder with the arrow. Select “Clear Recent Files”. I’m no expert but I figured maybe that would help. Also there’s clearing your entire browser cache too.
Thanks @Daniel_Gliebe : issue is, I can’t even get that far: Since chilipeppr loads the last file by default, and my last file is corrupt or something, I can’t access any of the menus, since… it just hangs trying to load the file before it gives me control to any of that :S
You need to go into your localstorage in the Chrome debug console and wipe the last file. The key is “last-imported”. To be able to see that localstorage entry you need to at least be on some page in the http://chilipeppr.com domain so load the homepage and then open the debug console.
Thanks John, after some digging I found that and deleted it. Working again. Note, for whatever reason chilipeppr won’t load the gcode I’m after, but UGS eats it fine. I’m guessing this is because chilipeppr is trying to render it all on screen, and my old mac just can’t handle it.
Still would like to put a request in to at least have the option to, on open, either load nothing, or the chilipeppr logo by default. I rarely cut the same thing twice, and some of the items take forever to open up, which means I have to wait twice as long as I should to access any new cut. Not the worst thing (hey, the software is free), but would at least make my life easier 
Hi Eric, I suppose the only way that feature would get in there is if somebody were to go add it. It wouldn’t be too hard, but it would also get to be annoying to have a dialog box that pops up every time you load asking you what file you want. Perhaps a workaround is to hold the shift key or something on load and if it is held then don’t load the last file. Again, somebody else would have to add that feature. The code to place it in would be the Drag Drop Widget which is forkable from the file pulldown in the workspace region.
I can code, but not in that language
Not trying to beat a dead horse, but any other software I use, when I open it, opens to a new\empty scene\file. Whether it’s Word, Maya, MeshMixer, etc. I’m just not used to software that opens an old file by default, seems weird, to me at least. That’s what the “Recent Files” menu is for Or like I said, if it just loaded the Chilipeppr logo every time, that’d be just fine by me.
But again, love Chilipeppr overall, just this one users opinion.
On a side-note, I completely disable the 3d view via the prefs thinking this was causing the load issue of my gcode: It was not, same problem. I got it working in UGS though, so i’m unblocked.
Thanks again for the support.
The reason ChiliPeppr opens the same file as your previous file is that if your job is running and all lines are uploaded to SPJS and you close the browser, then when you come back and reload you’ll start getting position updates from SPJS. It makes sense to reload the last file then because it shows you where you are at in your job. If it loaded the CP logo instead on reload then it wouldn’t make any sense to you. So it was a design feature to reload the last file. Also, given the nature of the browser and how often refreshes occur, it makes more sense in a browser app to reload the last file.
The broader issue is that CP shouldn’t crash. One possible approach is to just monitor RAM usage as the 3D object gets built up and then just give up with a nice error. Unfortunately adding up RAM is not super easy.
BTW, disabling the 3D viewer does nothing but stop refreshes being drawn to screen. The 3D object is still generated in memory regardless when the file loads because it’s core to CP.
Ah, I get it now, that makes compete sense based on how it functions.
I think I finally figured out what’s going on. The file I’m trying to load is greater than 5 megs (it’s 5.2) and Chrome has a 5 meg limit on local storage. I was able to get it to load by splitting the rough and final passes into two separate files. But now this begs the question, how does one cut a file in Chilipeppr if it’s greater than 5 megs? The piece I’m doing is 6"x12"x2.5", topo map of a mountain, so there’s a lot of detail in there. I have plans to eventually do one a good 4x this size, but since this one is currently pushing the limit of what apparently Chilipepr’s platform is (in my case, Chrome), what is the recommended solution? Again, I can switch to using UGS, but… I like Chilipeppr 