This is a migrated thread and some comments may be shown as answers.

Crash on startup (v. Q1-2013)

5 Answers 25 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Tasos
Top achievements
Rank 1
Tasos asked on 01 Jun 2013, 08:11 AM
Hello after upgrading to the latest build (v. Q1-2013) the program always crashes on start-up with the following message:

***
Problem Signature 05:    4.0.0.0
  Problem Signature 06:    50484bd7
  Problem Signature 07:    3fda
  Problem Signature 08:    105
  Problem Signature 09:    System.IO.DirectoryNotFound
  OS Version:    6.1.7601.2.1.0.256.1
  Locale ID:    1032
  Additional Information 1:    0a9e
  Additional Information 2:    0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:    0a9e
  Additional Information 4:    0a9e372d3b4ad19135b953a78882e789
***

any advice please.

(My system is Win7_64bit)

5 Answers, 1 is accepted

Sort by
0
Tsviatko Yovtchev
Telerik team
answered on 12 Jun 2013, 12:44 PM
Hi,

I beg your pardon about the delay. Your ticket slipped through and went unnoticed for a while.

I e-mailed you the latest release of JustDecompile. Please, give that a try and let us know whether it exhibits the same problem.

Once again, sorry about the delay.

Regards,
Tsviatko Yovtchev
Telerik
Tell us what you think about JustDecompile. Your opinion matters! You can use our forum, or our JustDecompile UserVoice website for feature requests.
0
Henrico
Top achievements
Rank 1
answered on 17 Jun 2013, 06:06 AM
Hi,

I have the same issue. Can I get also a new build or is there something else I can do?

OS: Windows 7 64-bit SP1
Telerik JustDecompile Version: 2013.2.613.0

Thanks!

Application: JustDecompile.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.DirectoryNotFoundException
Stack:
   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Threading.Dispatcher.Run()
   at System.Windows.Application.RunDispatcher(System.Object)
   at System.Windows.Application.RunInternal(System.Windows.Window)
   at System.Windows.Application.Run(System.Windows.Window)
   at System.Windows.Application.Run()
   at JustDecompile.App.Main()
0
Nikolay G Rusev
Telerik team
answered on 17 Jun 2013, 11:50 AM
Hi Henrico,

 Can you archive and delete the %appdata%\JustDecompile\ folder? If this fixes your problem, can you send us the archive, so that we can investigate the issue further?

Regards,
Nikolay G Rusev
Telerik
Tell us what you think about JustDecompile. Your opinion matters! You can use our forum, or our JustDecompile UserVoice website for feature requests.
0
Henrico
Top achievements
Rank 1
answered on 17 Jun 2013, 12:04 PM
Hi,

Thanks for your reply! I just debugged JustDecompile.exe with Visual Studio and the problem was the Reflexil plug-in, or actually the automatic update of the Reflexil plug-in. The folder 'C:\Program Files (x86)\Telerik\JustDecompile\Libraries\Plugins\Reflexil' did not exist. After I created the folder manually, I could start JustDecompile successfully again.

Because the problem was already solved, I haven't deleted the AppData folder. Do you still need the %APPDATA%\JustDecompile folder?
0
Nikolay G Rusev
Telerik team
answered on 17 Jun 2013, 01:00 PM
Hi,

 Since you've managed to fix the issue, there is no need to delete the AppData folder. 
Also, thanks for the additional info. Now that we know what caused the problem, we'll be able to investigate it properly.

Regards,
Nikolay G Rusev
Telerik
Tell us what you think about JustDecompile. Your opinion matters! You can use our forum, or our JustDecompile UserVoice website for feature requests.
Tags
General Discussions
Asked by
Tasos
Top achievements
Rank 1
Answers by
Tsviatko Yovtchev
Telerik team
Henrico
Top achievements
Rank 1
Nikolay G Rusev
Telerik team
Share this question
or