Try to do a flip canvas, or something that is a process. It also will happen on saves when it gets really bad. You have to use it for a while. It will start happening in random operations.Try to do a flip canvas, or something that is a process. Right now I'm working on a 3600x5400 piece and sai is very likely to crash if I try anything intensive with it, on a 4gb quad core. It's probably worse of course if you're using other apps that are sapping memory. I usually have a browser open that's taking up a ram or two.
Sai is limited to 10kx10k, but the upper limits of a particular system are ram dependant. My max size on this machine is supposed to be 5800x5800. You can go into options and look at workspace usage.
Those limits are pretty sad for a graphic application. I'm working on a poster right now. If I wanted to go larger I wouldn't be able to use sai at all, even if I was using my 64 bit machine with 8 gigs. Of course sai being 32 bit will only recognize 4gb even if you have 8gb. Max size on my 64 bit machine is 8191x8191, with full 4095 memory showing out of the available 8gb.
Probably also layers will be a generator of problems. I usually have at least 10 layers for my works, so that may be the difference between us.
This was an attempt at a flip, followed by a rotate, that caused a failed canvas, on a legal copy. It happens. At its upper limits when you try to really push the canvas Sai unfortunately fails.

This is actually a well known problem. I've spoken with the designer about it. This is actually why I believe sai development is stalled. The designer stated to me that he had to go back and start at the beginning and basically create a new sai to add more tools because of the memory leaks in sai.
Sai is not a completed program. There are blatant tools like a text tool completely missing. The designer basically dropped the project in the middle of working on it and decided to release it as is because of these problems.
Also there is a huge difference in how sai handles opacity and dragging of colors to any other app out there, and that's what I believe the original poster was complaining about. It may seem like nit picking, but it's actually a huge time saver the way sai does it, and I've never found it on any other application.
The big difference you can really see though is when you layer percentage painting translucent strokes over each other. Sai has an absolute control that is always linked to the pressure of the tablet, while every other painting application is a relative control that will layer a stroke over the one under it, creating a darker streak between two paint strokes layered over each other on the same layer.
I've noted this before in a similar thread. This is a very small thing, but it makes sai a much better handler of digital paint in my opinion than any other app out there. If you're an artist going for a particular look and become used to the way sai handles it, it really is a step back when you go to another application. It can be really frustrating to achieve a smooth shaded surface in those applications compared to sai.
This is something at the core of sai, that is different from every other way painting apps have been designed and really a great feature. It's just sad that sai isn't more complete and the development has stalled. There really needs to be a sai 2.0