iSyriux

My questions still haven't been answered. First, is it viable to relocate the sessiondata folder to the D drive, which is a separate disk, since I am using a desktop computer, even though I heard it is slower? If it is viable, is it even possible, and how do I do it? Secondly, is it absolutely impossible to restore sessiondata, even though these files become gigabytes large, and why would it be impossible if it is? And lastly, why can't there be a pop-up saying you cannot perform this action until the disk has enough space instead of just straight up crashing? I mean, copying to clipboard already has this pop-up.

As most hobbyists with mid-end computers can relate, the C drive does not have a lot of space, especially mine, which usually only has 1 GB free of storage when there are no temporary files. I also work on high resolution images for hours and hours on end without saving due to superstition with a hope that I would be able to save when I am finished. As such, I frequently run into crashes every time I work for a long time on these large images and I am looking for a way to solve this. Is it possible and efficient to redirect the session data folder into the D drive where I have more space even though I have heard it is a slower drive, and if it is a viable solution, how do I do it? Also, since these sessiondata folders are so large, how can it be that it cannot be reopened by paint.net and restored? I read an answer by an administrator on another post that these session data files cannot be read by any program, but then how is it read while the session is still active? Is there truly no way to restore a session from these large folders? Lastly, the very obvious feature to (at least) implement if redirecting session data folder to D drive is impossible/unviable, is preventing you from making any changes to the image until there is enough free space on the C drive. It should be a pop-up similar to when you're trying to copy to clipboard when there is not enough free space on your drive. It shouldn't crash. It should never crash.

Holy fricking smokers... It's been three years and this thread has not amassed another single reply. The absolute patheticality of the PDN community... I understand every point this post makes and I too have the same struggles as described in this post. Some people just don't understand humans aren't robots and people can make mistakes. But here I am, my PDN process not responding for seven hours. TL;DR, I accidentally hit CTRL+S when I was editing a PDN file that I meant to do only temporarily (ie. make some changes, flatten, copy image, paste image, then exit without saving), but I continued on thinking that I would be able to undo all my changes and go back to when I opened the image and CTRL+S it back, but when I finally did, PDN decided to freeze and I waited for 7 hours with still no change... I even tried increasing my memory priority with task manager...no change. I tried closing all my other processes...No change. PDN isn't even using any CPU in the task manager. I don't even know why or how it's managed to be frozen this long. Now I'm just trying to find out how to potentially save the temporary cache my current PDN process so I can recover my history and potentially restore the process to its previous state when I reopen it. But, as it turns out, NOBODY has even thought about this which makes my hair fall. The sheer unthoughtfulness and inactivity of the PDN community boggles my mind. I have no words but to say that this PDN project that I've been saving on my computer for an entire year is now gone and replaced with some temporary changes I made. Go ahead, tell me all you want to "MAKE BACKUPS AND BE MORE ORGANISED NEXT TIME". It's too freaking late. Why can't you just give me an actual solution?

So I was drawing a map and I forgot to save for the entire 3+ hour length of it and then paint.net just randomly froze for a second and then closed, all my hard work, gone. I had no apps open except chrome and discord, so I don't see how another app could interfere. There also was no crash log when I viewed the crash log directory.