thehx Posted February 1, 2015 Share Posted February 1, 2015 To reproduce the bug, 1) create an empty image, 800x600 2) Ctrl+A, Ctrl+C, hold Ctrl+Shift+V for around 10 seconds, then hold Ctrl+Z (in hope of undoing making these additional layers) 3) Fatality! To those who think the scenario above is far too unusual to cause any real trouble, here is the simpliest possible way to shoot yourself in the leg with no intention to do it: 1) Draw a background and hide it 2) Create a drawing on a layer with opacity around 5% and rendering mode other than default 3) Ctrl+Shift+C the nearly-transparent drawing 4) Delete the now-useless drawing layer, display the background layer, then repeatedly hit Ctrl+Shift+V until everything looks as planned 5) Realize that the final result is totally unacceptable (either because it really is, or because of someone else's bleeding eyes) 6) Hit the Ctrl+Z pedal to the floor, to unwind those 10 or 15 new layers 7) All your unsaved work is gone... Attack the wall with own head, I suppose, unless your auto-saving instinct is on a level when you hit Ctrl+S before drawing a line, after drawing it, before zooming out to check how it looks in a big picture, and after zooming back in. PS. The same thing often occurs in similar scenarios involving adding or removing layers too quickly (You may use Ctrl+M, for example) Quote Link to comment Share on other sites More sharing options...
racerx Posted February 1, 2015 Share Posted February 1, 2015 (edited) To reproduce the bug, 1) create an empty image, 800x600 2) Ctrl+A, Ctrl+C, hold Ctrl+Shift+V for around 10 seconds, then hold Ctrl+Z (in hope of undoing making these additional layers) 3) Fatality! To those who think the scenario above is far too unusual to cause any real trouble, here is the simpliest possible way to shoot yourself in the leg with no intention to do it: 1) Draw a background and hide it 2) Create a drawing on a layer with opacity around 5% and rendering mode other than default 3) Ctrl+Shift+C the nearly-transparent drawing 4) Delete the now-useless drawing layer, display the background layer, then repeatedly hit Ctrl+Shift+V until everything looks as planned 5) Realize that the final result is totally unacceptable (either because it really is, or because of someone else's bleeding eyes) 6) Hit the Ctrl+Z pedal to the floor, to unwind those 10 or 15 new layers 7) All your unsaved work is gone... Attack the wall with own head, I suppose, unless your auto-saving instinct is on a level when you hit Ctrl+S before drawing a line, after drawing it, before zooming out to check how it looks in a big picture, and after zooming back in. PS. The same thing often occurs in similar scenarios involving adding or removing layers too quickly (You may use Ctrl+M, for example) No problems here. I held Control + Shift + V for 20 sec (Created 28 layers), then held Control + Z to return back to beginning. It didn't even break a sweat..... Tried it again creating 86 layers and control +Z back to beginning, no problems at all. You may have insufficient RAM or are you using a 32-bit OS? Edited February 1, 2015 by racerx Quote Link to comment Share on other sites More sharing options...
BoltBait Posted February 1, 2015 Share Posted February 1, 2015 We're going to have to see the actual crash report. Quote Download: BoltBait's Plugin Pack | CodeLab | and a Free Computer Dominos Game Link to comment Share on other sites More sharing options...
thehx Posted February 2, 2015 Author Share Posted February 2, 2015 Win7-64.pro @ Dell Precision M6800 (16GB RAM, half of which are free when I start Paint.NET to reproduce the issue). Strangely enough, I couldn't find (or, more precisely, couldn't "find | grep pdncrash\.log" in a git bash window) the crash log at all. When paint.net crashed, I only observed the standard Windows message saying "The program is going to terminate, you may try debugging it...". I searched the whole users folder (which is, %appdata%/../..) for it via find|grep, since I don't quite trust the windows search. In case it could be of help, here is the full list of plugins I am using (although Paint.NET crashes even when I do not use any of them): Effects: MakeTransparent.dll (I am using it since Paint.NET 3.0) FileTypes: IcoCur.dll, AnimatedGifLibrary.dll PS. Usually, when a plugin crashes, Paint.NET offers to save whatever I've been working on. In this case, it just dies, no questions asked, leaving me watching all the unsaved changes sailing to the land of eternal spring. PPS. ..or is there an autosave plugin? Quote Link to comment Share on other sites More sharing options...
Pixey Posted February 2, 2015 Share Posted February 2, 2015 Hi @thehx. I too cannot reproduce what you're experiencing and I downloaded a couple of the plugins you are using, so it can't be them. Sometimes Paint crashes on me for no apparent reason and doesn't leave a crash log. But, when it does, it can be found by clicking on the 'cog' in the upper right hand side of your screen and choose daignostics where you can then click on the crash log - if you are using v.4. Quote How I made Jennifer & Halle in Paint.net My Gallery | My Deviant Art "Rescuing one animal may not change the world, but for that animal their world is changed forever!" anon. Link to comment Share on other sites More sharing options...
thehx Posted February 2, 2015 Author Share Posted February 2, 2015 Strangely enough, the logs folder is empty. Here is what exactly the fox says: Signature: Event: APPCRASH Application: PaintDotNet.exe Version: 4.5.5454.39504 Application timestamp: 5484cd44 Error module: MSVCR120.dll Error module version: 12.0.21005.1 Error module timestamp: 524f83ff Exception code: c0000005 Exception offset: 000000000003c3f9 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1049 Additional info 1: ad75 Additional info 2: ad7539a1050cd947e7161d5ea2ce0e0a Additional info 3: 7b38 Additional info 4: 7b38baf94350760d182377a53254f518 Quote Link to comment Share on other sites More sharing options...
thehx Posted February 2, 2015 Author Share Posted February 2, 2015 If this can help, below is the extraction from Windows Event Log. Quote Link to comment Share on other sites More sharing options...
Rick Brewster Posted February 3, 2015 Share Posted February 3, 2015 No I just need better repro steps. Instructions like "draw a background and then hide it" are super vague. What does "hide it" mean? Please rephrase your repro steps by saying exactly what you clicked on in the UI. (for example ... "hide it" may mean that you unchecked the layer's visibility in the Layers window. or it could mean you did a Select All and then Edit -> Erase Selection) Quote The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html Link to comment Share on other sites More sharing options...
thehx Posted February 4, 2015 Author Share Posted February 4, 2015 First of all, the first scenario is sufficient [for me] to have Paint.NET crashed: To reproduce the bug, 1) create an empty image, 800x600 2) Ctrl+A, Ctrl+C, hold Ctrl+Shift+V for around 10 seconds, then hold Ctrl+Z (in hope of undoing making these additional layers) 3) Fatality! Second, yes, by "hide" I meant "uncheck layer visibility", sorry for not being clear enough. I believe the crashes happen due to a race condition occuring when the number of layers is decreasing rapidly... or I just can't make a better guess. Quote Link to comment Share on other sites More sharing options...
Revvilo Posted September 5, 2015 Share Posted September 5, 2015 (edited) I too am experiencing the exact problem, reinstalling didn't fix it eitherBasically to get it to crash 100% (For me) is: open any image > create a layer > delete the layer that was created > create and delete the same way a few times (3 - 4 works) > then click "Open Image" or "New Image" in the history and watch it crash It really sucks when im editing a texture and go "oh wait" and hold ctrl z, it then crashes and I realize I never saved it xD Really love using PDN and hope for this to be resolved Edited September 5, 2015 by Revvilo Quote Link to comment Share on other sites More sharing options...
pdnnoob Posted September 5, 2015 Share Posted September 5, 2015 Sounds very much like your computer is just unable to handle that many undo operations at once. Try undoing one thing at a time instead. I was also unable to reproduce the crash. Quote No, Paint.NET is not spyware...but, installing it is an IQ test. ~BoltBait Blend modes are like the filling in your sandwich. It's the filling that can change your experience of the sandwich. ~Ego Eram Reputo Link to comment Share on other sites More sharing options...
Revvilo Posted September 6, 2015 Share Posted September 6, 2015 (edited) Sounds very much like your computer is just unable to handle that many undo operations at once. Try undoing one thing at a time instead. I was also unable to reproduce the crash. How can Intel Core I7-4770 3.4GHz Cpu 64bit win7 16 giga Ram Nvidia GTX 760 Gpu not be enough? I mean whether i'm editing a 16x image or a 1024x image it acts exactly the same And could you explain what you mean by "that many undo operations"? undoing four sets of "Create layer" and "Delete Layer" isn't that many On crashing it says paint.net has stopped working with two buttons one "debug" the other "close program"; so it never creates a crash log Clicking debug just throws an "unhandled win32 exeption in PaintDotNet.exe [randomized numbers every crash]" Surely it has to be software or my pc not being configged right It just seems stange how none of you can reproduce it Heres whats in the Diagnostics tab Edited September 6, 2015 by Revvilo Quote Link to comment Share on other sites More sharing options...
Rick Brewster Posted September 6, 2015 Share Posted September 6, 2015 If you have a crash log then please post it. It's really difficult to diagnose without one. Quote The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html Link to comment Share on other sites More sharing options...
Revvilo Posted September 6, 2015 Share Posted September 6, 2015 (edited) On crashing it says paint.net has stopped working with two buttons one "debug" the other "close program"; so it never creates a crash log The crash log folder is empty Edited September 6, 2015 by Revvilo Quote Link to comment Share on other sites More sharing options...
skullbonz Posted September 7, 2015 Share Posted September 7, 2015 Sometimes it boggles my mind why people do some of the things they do with PDN that makes it crash, this is one of them. Maybe I'll go see if my van can jump the gorge. Quote http://forums.getpaint.net/index.php?/topic/21233-skullbonz-art-gallery Link to comment Share on other sites More sharing options...
Revvilo Posted September 7, 2015 Share Posted September 7, 2015 (edited) Lol wutI use layers, flatten, then realize that I've missed something - undo a few times, it crashes because of layers that have been deleted and created. And that isn't normal?? Edited September 8, 2015 by Revvilo Quote Link to comment Share on other sites More sharing options...
Rick Brewster Posted September 8, 2015 Share Posted September 8, 2015 No, it's not normal. I don't agree with skullbonz's comment. Crash logs. I need crash logs. I can't reproduce this on my systems. Quote The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.