1j01
commented
3 years ago Yep, I figured it was more important to include this dialog than to get the condition exactly right. I'm not sure of a good way to exclude cases where the image is supposed to be completely transparent. I thought of having an extra canvas to test if it becomes blank when memory is cleared, but it turns out individual canvases can be cleared while leaving others in tact, and bigger ones probably get cleared first, and I don't really want a giant canvas taking up memory in order to detect when memory gets cleared because then it'll get cleared earlier, and it might be unreliable anyways. Probably there needs to be some flag that's maintained of whether it's supposed to be blank or not, and canvas-clearing operations set it, and then it only gets reset when (after any operation) the canvas stops being blank. But what is a canvas-clearing operation? Image > Clear Image sure, but also deleting a selection sometimes, or dragging a selection off the canvas, or using the Fill tool to fill with transparency. Basically it's a surprisingly complicated problem, and not very interesting. Other options include making the dialog less alarming, maybe starting with "Did you mean to clear the canvas?" or something
Tubaleviao
Basically, the "the browser may have cleared the canvas due to memory leaks" message shows up every action I do while the image is empty with transparency. This happens not only if it actually cleared the canvas to memory leaks (the intended behavior), but also when it was done intentionally, i.e choosing the "Clear Canvas" option.