'JustCodeAnalysis has stopped working' error for large solution

[Devin]

I just installed the latest internal build (8/23/2011) of JustCode.  It loads fine on smaller solutions, but when I try and load our full solution (100+ projects), I get the error "JustCodeAnalysis has stopped working" and it gives me the options to Debug or Close Program.  If I close Program, it just gives me the error again 10 seconds later.

I'm assuming this is because JustCode does solution-wide analysis by default (as opposed to Resharper's default setting of only analyzing the open class), so larger solutions cause it to crash.  Our solution isn't larger than other corporate solutions that I've worked with, so I'm wondering if there is a way that I can select how thorough the analysis is or if this is a known bug that is being fixed.  

[Blagoev]

Hi Devin,
Thanks for reporting this. It's critical. JustCode should support your scenario fine and should not in any case fail with unexpected errors. Its not caused by our solution wide analysis because its tested on very large projects. This must be some other kind of bug. Can you please try sending us the error reports logged in  %USERPROFILE%\AppData\Local\JustCode\Logs.
Also it would be great if you could tell us what information is logged in windows event log. To do that open Event Viewer and check if there is an entry for the JustCodeAnalysis process in the Event Viewer->Windows Logs->Application section.

We are taking this matters seriously and would like to fix your problem as soon as possible.

All the best,
Blagoev
the Telerik team

[Devin]

I tried submitting the error log via the "Report JustCode Problems" utility, but when I did it told me there was an error.  The log in AppData is now 388 KB, and your forum doesn't allow .txt attachments.  If you don't mind, I'd be happy to send it to you via email.  Here is the first error from the log:

ERROR 2011-08-25 08:23:51.293 : Server (1516): MetadataToCSConverter.CacheDll() - pe format error:C:\sd\Trunk\bin\debug\pdfnet11.dll
Telerik.JustCode.LanguageFrontend.Dotnet.Pereader.PEFormatException: Unexpected element type constant while parsing a TypeEntity: 10
   at Telerik.JustCode.LanguageFrontend.Dotnet.Pereader.PEMetadata.#iu(Int32 elementType, #8s context, StringBuilder targetBuf, Boolean allowVoid, Boolean processDoc, Int32 containingTypeDefRow, Int32 methodDefRow, #s5q arrayRanks, #9s& blobContext) in c:\B10\Manticore\Production2010_Release\Sources\PortableExecutableReader\PEMetadata.cs:line 3719
   at Telerik.JustCode.LanguageFrontend.Dotnet.Pereader.PEMetadata.#iu(Int32 elementType, #8s context, StringBuilder targetBuf, Boolean allowVoid, Boolean processDoc, Int32 containingTypeDefRow, Int32 methodDefRow, #s5q arrayRanks, #9s& blobContext) in c:\B10\Manticore\Production2010_Release\Sources\PortableExecutableReader\PEMetadata.cs:line 3598
   at Telerik.JustCode.LanguageFrontend.Dotnet.Pereader.PEMetadata.#iu(Int32 elementType, #8s context, StringBuilder targetBuf, Boolean allowVoid, Boolean processDoc, Int32 containingTypeDefRow, Int32 methodDefRow, #9s& blobContext) in c:\B10\Manticore\Production2010_Release\Sources\PortableExecutableReader\PEMetadata.cs:line 3484
   at Telerik.JustCode.LanguageFrontend.Dotnet.Pereader.PEMetadata.#fu(#8s context, Int32 typeDefRow, Int32 methodDefRowNo, StringBuilder targetBuf) in c:\B10\Manticore\Production2010_Release\Sources\PortableExecutableReader\PEMetadata.cs:line 3435
   at Telerik.JustCode.LanguageFrontend.Dotnet.Pereader.PEMetadata.#au(#8s context, Int32 typeDefTableIndex, Boolean isInterface, Boolean isStruct, Int32 methodRowNo, Int32 simpleTypeNameRef, Boolean includeSetterGetterMethods) in c:\B10\Manticore\Production2010_Release\Sources\PortableExecutableReader\PEMetadata.cs:line 3074
   at Telerik.JustCode.LanguageFrontend.Dotnet.Pereader.PEMetadata.#9t(Int32 typeDefTableIndex, Boolean isInterface, Boolean isStruct, Int64 simpleTypeNameRef, Int64 methodStartIndex, #8s context) in c:\B10\Manticore\Production2010_Release\Sources\PortableExecutableReader\PEMetadata.cs:line 2688
   at Telerik.JustCode.LanguageFrontend.Dotnet.Pereader.PEMetadata.#Lt(Int32 typeDefRowNo, #8s context, Boolean shouldBeNested) in c:\B10\Manticore\Production2010_Release\Sources\PortableExecutableReader\PEMetadata.cs:line 943
   at Telerik.JustCode.LanguageFrontend.Dotnet.Pereader.PEMetadata.#It(String filepath) in c:\B10\Manticore\Production2010_Release\Sources\PortableExecutableReader\PEMetadata.cs:line 438
   at Telerik.JustCode.LanguageFrontend.Dotnet.Pereader.PEMetadata.#iTi(String filepath) in c:\B10\Manticore\Production2010_Release\Sources\PortableExecutableReader\PEMetadata.cs:line 408
   at Telerik.JustCode.LanguageFrontend.Dotnet.Pereader.MetadataToCSConverter.#Et(String libFile, String dllFilepath) in c:\B10\Manticore\Production2010_Release\Sources\PortableExecutableReader\MetadataToCSConverter.cs:line 567

There are several different errors that follow.

As for the windows event log:

Faulting application name: JustCodeAnalysis.NET4.exe, version: 2011.2.816.0, time stamp: 0x4e4a38a2
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x00000000
Fault offset: 0x0546d328
Faulting process id: 0x5ec
Faulting application start time: 0x01cc63326d261258
Faulting application path: C:\Program Files (x86)\Telerik\JustCode\Libraries\JustCodeAnalysis.NET4.exe
Faulting module path: unknown
Report Id: dad1df90-cf25-11e0-976c-78ca39c07037

There were 4 more such errors that occurred over the next 3 minutes (varying by Fault Offset, process id and report id).

[Blagoev]

Hi Devin,
Thanks for the info. The problem with failing JustCodeAnalysis process has been fixed already. Expect the fix in the upcoming internal build next week. For the other issue we will need the dll you are using pdfnet11.dll. Seems to be an old version of a pdf library.

Greetings,
Blagoev
the Telerik team