I got a bad one here. Rasberry pi 2… FF pro running.
.8 worked like slice bread… never a issue.
.9 and now .9 (1) are crashing badly and i mean really bad… lost over 30 hours of printing on this… ( maybe unstable?) sent the logs in…
Do we have a image of .8 i can download?
Apologies! 
@Daniel will review the logs and see what’s going on.
Can you describe how exactly it crashes? As in, during what stage?
Thanks!
Ok, i found official link for 0.8 image 
http://s3.amazonaws.com/astrobox-releases/AstroBox-rpi-0_8_3-20151002.zip
Btw. I have Rpi 2 and latest 0.9.1 and all is stable… printed today entire day with this version without problems…
first crash .9 (0) it would crash like at 16 % into a 45 hour print… I also noticed after the update the pi would not fully shut down either like it was hanging on shut down…
Last crash .9 (1) we crashed at 26% into a 34 hour print…
One thing it does it just pauses and freezes right there on the print ( glad it stops the extruder motor) on .9 (0)
On .9(1) this crash just stopped put the bed half way down and stopped.
When i logged in it was active like it was ready to print. both times on .9(0) and .9(1) i can log in and it acts like its waiting on me to start a new print… like the print on the bed just vanished to it like it forgot it…
thanks for the link…
I dont know if the long prints past 32 hours are causing the problem maybe?
I have seen this sudden stop mid print too. I have found if I reslice and resubmit sometimes it works. I assumed it was a bad upload or download or slice as I have have been fighting some internet issues. But maybe not.
My prints are seldom over 4 hours and the crash might be only 1 hour in. Hasn’t happened again since I reflashed the Pi. However today i had one completely fail to start. The printer started heating and I walked away. When I came back the printer was cool and had gone to standby. Head had never left home position. The web site seemed to think the print was in progress but astrobox was sitting waiting to go. Clicking cancel just got me a failed to cancel message. I could not get them to resync until i rebooted the Pi.
At least I know I’m not crazy… I don’t use the cloud print I use the local print upload. I use my own slicer.
Same x3g file I used on .8 worked flawlessly… same file on .9 fails in mid print…
Funny you said that about starting up a print and failing. I had that happen the first time .9 was loaded on the pi.
Yeah, same here. X3G on previous .8 was fine, in fact never had a crash on AstroPrint previously (been super stable). On .9 stops midway through. And its not due to the length of the print. My died about 25% through on a 4 hour print. So no you’re not crazy. USB Camera also not working even though it is detected fine…but that is another story. I stumbled across this thread looking for a way to downgrade…
Please send logs so we can fix this. You can do this via the advanced settings section in the astrobox
I have seen the logs you guys sent and I can conclude this:
My recommendations until 0.9(2) is out for you is to not use the camera functionality so that your print job is not interrupted by camera errors. This is NOT acceptable and will be fixed. It’s just a workaround in the meantime.
Sending logs to us is very helpful to find and resolve these problems. We have done many tests before releasing this but we can’t test every camera in the market. We always pick a low, mid and high cost camera to test with. More info here:
That’s what I said… pi2…
@Daniel I don’t know if this makes any sense here now I noticed this too. I noticed my printer runs more fluid. On. .8 . On .9 it acted jumpy like it was having some kind of communication issue. Right now as I speak to you I’m back on .8 and the machine runs normal again.
That’s interesting. Which RPi ? 1, 2 or 3
It makes sense, it’s possible that the errors are taking up too much CPU and it’s affecting the communications process.
Do you remember what camera settings you had? Video format, fps and size ?
I had every set at default…
When you moved to 0.9, did you flash a fresh image or upgraded from an existing 0.8 one?
I did a fresh install to .9(0) then did the update via upgrade to .9(1)…
If you have some time to test, could use the 0.8 image you now have, upgrade it to 0.8(8) and then to 0.9(1) and see if you still have problems with the camera and prints.
No worries if you’d rather not do that.
I will give it a shot when the printer gets done… (for me I do very long prints rare I’m under 24hr prints most time 40 hours)
I will add this in with the camera problem. Tho I really only tested it to make sure it worked I would get the blue screen and if I hit refresh the camera would come to life. Do it again this time green then I would get the picture… I never tested the live part… it acted like there was a communication problem right there and it was slow to load the still image. Like you said all the resources where used up on the pi dealing with camera bug or bugs.
I have some elcheapo usb cam. I will get you the model info if I can.
I just updated to .91. Not sure if that clears the logs but in the interest of solving this i will continue to use the camera and next time it dies or something odd happens ill send the log. None of my prints are mission critical so if it fails oh well at least we learn something.