mezziah Posted July 9, 2008 Share Posted July 9, 2008 Hello forum. I absolutely have no idea what's happening after my upgrade to the very latest version of PDN (3.35). My system is up-to-date, I already tried reinstalling the program, rebooting the machine and deleting the log. There aren't any plugins installed. Here's the crash log: Application version: Paint.NET v3.35 (Final Release Build 3.35.3106.20184) Time of crash: 09/07/2008 13:11:43 Application uptime: 00:00:00.9687500 OS Version: 5.1.2600.131072 Service Pack 2 Workstation x86 .NET Framework version: 2.0.50727.1433 x86 Processor: 1x "AMD Athlon(tm) 64 Processor 3200+" @ ~1999MHz (DEP, SSE, SSE2) Physical memory: 1023 MB UI DPI: 96,00 dpi (1,00x scale) Tablet PC: no Updates: true, 19/05/2008 Locale: pdnr.c: de, hklm: de, hkcu: n/a, cc: es-ES, cuic: es-ES Features log: UpdatesState(StartupState), SetTool(PaintDotNet.Tools.PaintBrushTool), UpdatesState(ReadyToCheckState), HM(NullHistoryMemento), ShowDialog(PaintDotNet.ToolsForm), ShowDialog(PaintDotNet.HistoryForm), ShowDialog(PaintDotNet.LayerForm), ShowDialog(PaintDotNet.MainForm) Loaded assemblies: mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 @ C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mscorlib.dll PaintDotNet, Version=3.35.3106.20184, Culture=neutral, PublicKeyToken=null @ D:\Aplicaciones\Paint.NET\PaintDotNet.exe System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 @ C:\WINDOWS\assembly\GAC_MSIL\System.Windows.Forms\2.0.0.0__b77a5c561934e089\System.Windows.Forms.dll System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 @ C:\WINDOWS\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a @ C:\WINDOWS\assembly\GAC_MSIL\System.Drawing\2.0.0.0__b03f5f7f11d50a3a\System.Drawing.dll PaintDotNet.Core, Version=3.35.3106.20179, Culture=neutral, PublicKeyToken=null @ D:\Aplicaciones\Paint.NET\PaintDotNet.Core.dll PaintDotNet.Base, Version=3.35.3106.20178, Culture=neutral, PublicKeyToken=null @ D:\Aplicaciones\Paint.NET\PaintDotNet.Base.dll PaintDotNet.SystemLayer, Version=3.35.3106.20178, Culture=neutral, PublicKeyToken=null @ D:\Aplicaciones\Paint.NET\PaintDotNet.SystemLayer.dll PaintDotNet.Resources, Version=3.35.3106.20179, Culture=neutral, PublicKeyToken=null @ D:\Aplicaciones\Paint.NET\PaintDotNet.Resources.dll PaintDotNet.Data, Version=3.35.3106.20180, Culture=neutral, PublicKeyToken=null @ D:\Aplicaciones\Paint.NET\PaintDotNet.Data.dll PaintDotNet.Effects, Version=3.35.3106.20181, Culture=neutral, PublicKeyToken=null @ D:\Aplicaciones\Paint.NET\PaintDotNet.Effects.dll mscorlib.resources, Version=2.0.0.0, Culture=es, PublicKeyToken=b77a5c561934e089 @ C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mscorlib.dll Exception details: System.AccessViolationException: Intento de leer o escribir en la memoria protegida. A menudo, esto indica que hay otra memoria dañada. en System.Drawing.SafeNativeMethods.Gdip.IntGdipDeleteFontFamily(HandleRef fontFamily) en System.Drawing.SafeNativeMethods.Gdip.GdipDeleteFontFamily(HandleRef fontFamily) en System.Drawing.FontFamily.Dispose(Boolean disposing) en System.Drawing.FontFamily.Dispose() en PaintDotNet.FontInfo.Dispose() en PaintDotNet.ToolConfigStrip.PopulateFonts() en PaintDotNet.ToolConfigStrip.PopulateFontsBackgroundThread() en PaintDotNet.ToolConfigStrip.PopulateFontsBackgroundThread(Object ignored) en System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state) en System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) en System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack) en System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state) Anyone can help me? Thanks in advance for any information on troubleshooting. Quote Link to comment Share on other sites More sharing options...
becauseilearn Posted July 9, 2008 Share Posted July 9, 2008 It looks like some process is trying to write to protected memory, based on my possible mistranslation of the error detail. Since the lines below it note a few instances where it is working with fonts, I suspect that there is a corrupt font package on your system. I could be completely wrong. If you recently placed some new fonts on your PC, you could remove them and see if the problem goes away. Quote 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.