AndrewDavid
-
Posts
1,592 -
Joined
-
Last visited
-
Days Won
28
Posts posted by AndrewDavid
-
-
If I'm not mistaken, this crash is due to the plugin
SpoilerThis text file was created because paint.net crashed. Please e-mail this to crashlog4@getpaint.net so we can diagnose and fix the problem.
Application version: paint.net 4.3 (β 4.300.7933.28357)
Time of crash: 9/20/2021 8:48:43 PM
Application uptime: 00:34:39.1885882
Application state: Running
Working set: 261,428 KiB
Handles and threads: 971 handles, 41 threads, 189 gdi, 212 user
Install type: Classic
Application directory: C:\Program Files\paint.net
Current directory: C:\Program Files\paint.net
Install directory: C:\Program Files\paint.net
OS Version: Windows 10 Home 10.0.19044.0 x64
.NET version: .NET 5.0.10 x64
Processor: "Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz" @ ~3193MHz (4C/4T, SSE, SSE2, SSE3, SSSE3, SSE4_1, SSE4_2, AVX, AVX2)
Physical memory: 8143 MB
Video card: NVIDIA GeForce GT 720 (v:10DE, d:1286, r:161), Microsoft Basic Render Driver (v:1414, d:8C, r:0)
Hardware acceleration: True (default: True)
Pointers: none
UI animations: True
UI DPI: 96 dpi (1.00x scale)
UI theme: VisualStyleClass=Aero, EffectiveTheme=Aero, DWM=yes, AeroColorScheme=Dark, ThemeFileName=Aero.msstyles
Updates: True, 9/20/2021
Locale: pdnr.c: en-US, hklm: en-US, hkcu: en-US, cc: en-US, cuic: en-US
Flags:Exception details:
System.DivideByZeroException: Attempted to divide by zero.
at DrawGridEffect.DrawGridEffectPlugin.Render(Surface dst, Surface src, Rectangle rect)
at DrawGridEffect.DrawGridEffectPlugin.OnRender(Rectangle[] rois, Int32 startIndex, Int32 length)
at PaintDotNet.Effects.Effect`1.Render(EffectConfigToken parameters, RenderArgs dstArgs, RenderArgs srcArgs, Rectangle[] rois, Int32 startIndex, Int32 length) in D:\src\pdn\src\Effects\Effect`1.cs:line 99
at PaintDotNet.Effects.BackgroundEffectRenderer.RenderWithClipMask(Effect effect, EffectConfigToken token, RenderArgs dstArgs, RenderArgs srcArgs, RectInt32[] rois, Result`1 lazyClipMaskRenderer) in D:\src\pdn\src\PaintDotNet\Effects\BackgroundEffectRenderer.cs:line 253
at PaintDotNet.Effects.BackgroundEffectRenderer.RendererContext.RenderTile(EffectConfigToken token, Int32 tileIndex) in D:\src\pdn\src\PaintDotNet\Effects\BackgroundEffectRenderer.cs:line 169
at PaintDotNet.Effects.BackgroundEffectRenderer.RendererContext.RenderNextTile(EffectConfigToken token) in D:\src\pdn\src\PaintDotNet\Effects\BackgroundEffectRenderer.cs:line 150
at PaintDotNet.Effects.BackgroundEffectRenderer.RendererContext.RenderNextTileProc(Object token) in D:\src\pdn\src\PaintDotNet\Effects\BackgroundEffectRenderer.cs:line 144
at PaintDotNet.Effects.EffectRendererWorkItemQueue.OnExecuteNextWorkItem() in D:\src\pdn\src\PaintDotNet\Effects\EffectRendererWorkItemQueue.cs:line 142
at PaintDotNet.Threading.MultithreadedWorkItemDispatcher.WorkThreadProc(Object context) in D:\src\pdn\src\Core\Threading\MultithreadedWorkItemDispatcher.cs:line 495
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart(Object obj)Such a small plugin, this is one I am attempting to re-write.
It is the original one that crashed - not the one I attempting to build. To repo move slider all the way to 1000 then move it back to 0.
-
And while I'm waiting for it to install I have a question.
If a plugin is designed in codelab and I decompile it and bring it into Visual Studio, can you explain why there are so many errors? Is it to be expected because it was built in Codelab and not exported for Visual Studio through codelab.
Installation complete.
Success. I moved the bar 20 times and no errors. Job well done.
-
1
-
-
Think of a house on a foundation. Net Core 5.0 is the foundation. 4.3 is the House Paint.Net is built in.. That's my understanding.
From @Rick Brewster
Major version bumps like that are good for when there are new features, UI redesigns, etc. This update is primarily a technology upgrade and performance optimization release, and there aren't really any new end-user features.
-
So the switch was to try and get it to generate a crash log? If so, it didn't.
-
I managed to get the trace with the switch. You can read the trace. Paint did not exit, only disappeared. Here's the trace
-
Just installed this one for the first time
Move the slider 3 - 5 times and Paint just crashes - no crash file.
https://forums.getpaint.net/topic/116703-mathlatex-plugin/-
1
-
-
@Ego Eram Reputo's code is failing
However the code in @toe_head2001,s Plugin Browser works. My code crashes paint.net.
-
Silly me. Ever since you changed the plugin folder, I forgot to set exclusions for them. Look at the difference.NewAlpha.zip
-
Challenges - Update to Visual Studio yesterday that resolved 1 bug that I saw - followed by an update to windows while working with an Alpha version of Paint.Net. Today I figured out another problem. Don't have Paint open before you open Visual Studio. Seems OK if you open after. I was trying to open form designer, but kept getting an error. It was because Paint.Net was running in the background and put locks on the assemblies VS was trying to use.
PS I remember those cards. Long before anyone heard of DOS. 😊
-
Thanks @midora You just lit the lightbulb. In the dialogue box (Base Output Path) in properties.
I thought that was for where I wanted the plug to go. Now the "Copy Path" makes sense to me.
6 hours ago, AndrewDavid said:This may be a noobie question
And it was! 😊
-
I'm getting the plugin copied to Effects. I'm asking about all the folders VS is creating.
-
One of the features you introduced was loading sub folders (I thought you said one) as part of the load process. I just want to know if this is correct. Should only one load or all sub-folders? All sub-folders are being loaded.
I have been looking for an answer to this question for a few days. When I build my project in Visual Studio 2022 (Preview), regardless of whether its debug or release, VS creates sub-folders to the effect folder titled "Debug" and "Release". Inside the "Debug" folder is a complete copy of all the references of my project. I noticed this back when I was doing the trace commands, and removed them prior to running the command. You can imagine the load time it takes if I don't remove them.
Am I missing something? This may be a noobie question. Is there a way to prevent these folders from being created? Is this just normal behavior?
Seems overkill to me. Your help is appreciated.
-
@NinthDesertDude Issue resolved.
-
1
-
-
When I click on the link, this is what I see;
The only thing I have done on Google is Create 1 Google Doc.
-
Just use the Rectangle Selection - fill with your color, then Move Selection to another area, fill with color, repeat until you are done.
Hope this helps.
-
-
@Rick Brewster Success this time. New video driver installed, then rebooted.
My Effects are too big (I know that). Tried sorting them into 3 zip files. Still too big. G'Mic and PSD files and 550 plugins make for a big load. This trace should show you how long it took to load. Don't think I'm complaining. You have the other trace for second load and the difference is incredible.
-
14 minutes ago, AndrewDavid said:
Opening a 15 MB (VS Walkthrough) just now was pretty slow.
Did it again and took about 3 seconds including plugins.
-
I am running into upload size limit restrictions. Grab those so I can delete them and try to upload Effects in three separate files.
1 for the main directory
1 for G'Mic and PS files (8BF's)
1 for 3 other SubFolders
-
5 hours ago, Rick Brewster said:
You were running it for 2 hours this morning, without issues, using 4.3 alpha build 7921?
Yes
It only happened when I tried to do the trace. I had problems figuring out the proper syntax for the trace command and ended up using this:
paintdotnet.exe /enableTracing:c:\Users\Andrew\Documents\Test\pdn.trace
I was in the paint.net directory and had to add the .exe for the command to work.
5 hours ago, Rick Brewster said:Has it ever hung when tracing was not enabled?
Opening a 15 MB (VS Walkthrough) just now was pretty slow. The computer was idle for about 3 hours.
5 hours ago, Rick Brewster said:ZIP up your plugin directories (Effects, FileTypes, and Shapes)
-
1 hour ago, Greast said:
It could be false
It is.
-
2
-
-
OK - back in business. Current Beta installed.
This trace is after opening Paint the second time.
Attempting to do a trace the first time (after reboot) causes the app to hang (Program not responding). Closed through task manager this time. Because it wasn't shut down through exit - it won't record the trace. Just a corrupted file is found. 5 minutes of hanging was too long.
-
@Rick Brewster Now I am having big trouble getting paint to run. I was using it all morning (at least 2 hours). When you asked for the trace, I rebooted to get a fresh start.
After searching for the trace command, I had trouble getting it to work. It finally took - started paint, but all I saw was the little blue circle, and the app not responding message. I was able to close it clicking on the X button. Got the normal program not responding/report to Microsoft message and cancelled out back to the desktop.
Rebooted - Tried to restart paint - no luck - just the blue circle after clicking on effects.
Uninstalled and installed previous beta version - still no luck - just the blue circle after clicking on effects.
Now I have uninstalled that version and debating what to do next.
I do recall having trouble getting that trace to work. I know its just a switch and shouldn't damage the installation, but something corrupted something.
I'll do a SFC and get back to you.
-
@Rick Brewster Somethings wrong
paint.net 4.3 beta build 7929
in Preview Center
Posted · Edited by AndrewDavid
@midora Perhaps the author thought setting the value to "0" when designing a grid would create only rows or only columns.