JustCode crases if color identifiers are enabled

[Timo Pijnappel]

Hi, 

I'm using VS 2010 with JustCode and Productivity Power Tools installed as the only extensions. JustCode works fine until I enable the Color Identifiers option (which I'd really like to use). As soon as I save the preferences and open a C# document Visual Studio crashes.
I assumed this could be a conflict with the Pro Power Tools, so I tried disabling the extension, without any effect. I also tried uninstalling it, VS still crashes.

Thankful for any advice.

Here is the log:

SILENT 2010-08-03 08:29:55.864 : Server (3552): Trace: System.ServiceModel Error: 131075 : 

SILENT 2010-08-03 08:29:55.864 : Server (3552): Trace: <TraceRecord xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord" Severity="Error"><TraceIdentifier>http://msdn.microsoft.com/de-DE/library/System.ServiceModel.Diagnostics.ThrowingException.aspx</TraceIdentifier><Description>Throwing an exception.</Description><AppDomain>JustCodeAnalysis.NET4.exe</AppDomain><Exception><ExceptionType>System.IO.PipeException, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType><Message>There was an error reading from the pipe: Die Pipe wurde beendet. (109, 0x6d).</Message><StackTrace>   at System.ServiceModel.Channels.PipeConnection.OnAsyncReadComplete(Boolean haveResult, Int32 error, Int32 numBytes)

   at System.ServiceModel.Channels.OverlappedContext.CompleteCallback(UInt32 error, UInt32 numBytes, NativeOverlapped* nativeOverlapped)

   at System.Runtime.Fx.IOCompletionThunk.UnhandledExceptionFrame(UInt32 error, UInt32 bytesRead, NativeOverlapped* nativeOverlapped)

   at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)

</StackTrace><ExceptionString>System.IO.PipeException: There was an error reading from the pipe: Die Pipe wurde beendet. (109, 0x6d).</ExceptionString></Exception></TraceRecord>

SILENT 2010-08-03 08:29:55.866 : Server (3552): Trace: System.ServiceModel Error: 131075 : 

SILENT 2010-08-03 08:29:55.866 : Server (3552): Trace: <TraceRecord xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord" Severity="Error"><TraceIdentifier>http://msdn.microsoft.com/de-DE/library/System.ServiceModel.Diagnostics.ThrowingException.aspx</TraceIdentifier><Description>Throwing an exception.</Description><AppDomain>JustCodeAnalysis.NET4.exe</AppDomain><Exception><ExceptionType>System.ServiceModel.CommunicationException, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType><Message>There was an error reading from the pipe: Die Pipe wurde beendet. (109, 0x6d).</Message><StackTrace>   at System.ServiceModel.Channels.PipeConnection.OnAsyncReadComplete(Boolean haveResult, Int32 error, Int32 numBytes)

   at System.ServiceModel.Channels.OverlappedContext.CompleteCallback(UInt32 error, UInt32 numBytes, NativeOverlapped* nativeOverlapped)

   at System.Runtime.Fx.IOCompletionThunk.UnhandledExceptionFrame(UInt32 error, UInt32 bytesRead, NativeOverlapped* nativeOverlapped)

   at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)

</StackTrace><ExceptionString>System.ServiceModel.CommunicationException: There was an error reading from the pipe: Die Pipe wurde beendet. (109, 0x6d). ---&amp;gt; System.IO.PipeException: There was an error reading from the pipe: Die Pipe wurde beendet. (109, 0x6d).

   at System.ServiceModel.Channels.PipeConnection.OnAsyncReadComplete(Boolean haveResult, Int32 error, Int32 numBytes)

   --- End of inner exception stack trace ---</ExceptionString><InnerException><ExceptionType>System.IO.PipeException, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType><Message>There was an error reading from the pipe: Die Pipe wurde beendet. (109, 0x6d).</Message><StackTrace>   at System.ServiceModel.Channels.PipeConnection.OnAsyncReadComplete(Boolean haveResult, Int32 error, Int32 numBytes)</StackTrace><ExceptionString>System.IO.PipeException: There was an error reading from the pipe: Die Pipe wurde beendet. (109, 0x6d).

   at System.ServiceModel.Channels.PipeConnection.OnAsyncReadComplete(Boolean haveResult, Int32 error, Int32 numBytes)</ExceptionString></InnerException></Exception></TraceRecord>

SILENT 2010-08-03 08:29:55.866 : Server (3552): Trace: System.ServiceModel Error: 131075 : 

SILENT 2010-08-03 08:29:55.867 : Server (3552): Trace: <TraceRecord xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord" Severity="Error"><TraceIdentifier>http://msdn.microsoft.com/de-DE/library/System.ServiceModel.Diagnostics.ThrowingException.aspx</TraceIdentifier><Description>Throwing an exception.</Description><AppDomain>JustCodeAnalysis.NET4.exe</AppDomain><Exception><ExceptionType>System.ServiceModel.CommunicationException, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType><Message>There was an error reading from the pipe: Die Pipe wurde beendet. (109, 0x6d).</Message><StackTrace>   at System.ServiceModel.Channels.PipeConnection.OnAsyncReadComplete(Boolean haveResult, Int32 error, Int32 numBytes)</StackTrace><ExceptionString>System.ServiceModel.CommunicationException: There was an error reading from the pipe: Die Pipe wurde beendet. (109, 0x6d). ---&amp;gt; System.IO.PipeException: There was an error reading from the pipe: Die Pipe wurde beendet. (109, 0x6d).

   at System.ServiceModel.Channels.PipeConnection.OnAsyncReadComplete(Boolean haveResult, Int32 error, Int32 numBytes)

   --- End of inner exception stack trace ---

   at System.ServiceModel.Channels.PipeConnection.OnAsyncReadComplete(Boolean haveResult, Int32 error, Int32 numBytes)</ExceptionString><InnerException><ExceptionType>System.IO.PipeException, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType><Message>There was an error reading from the pipe: Die Pipe wurde beendet. (109, 0x6d).</Message><StackTrace>   at System.ServiceModel.Channels.PipeConnection.OnAsyncReadComplete(Boolean haveResult, Int32 error, Int32 numBytes)</StackTrace><ExceptionString>System.IO.PipeException: There was an error reading from the pipe: Die Pipe wurde beendet. (109, 0x6d).

   at System.ServiceModel.Channels.PipeConnection.OnAsyncReadComplete(Boolean haveResult, Int32 error, Int32 numBytes)</ExceptionString></InnerException></Exception></TraceRecord>

SILENT 2010-08-03 08:29:55.867 : Server (3552): Trace: System.ServiceModel Error: 131075 : 

SILENT 2010-08-03 08:29:55.867 : Server (3552): Trace: <TraceRecord xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord" Severity="Error"><TraceIdentifier>http://msdn.microsoft.com/de-DE/library/System.ServiceModel.Diagnostics.ThrowingException.aspx</TraceIdentifier><Description>Throwing an exception.</Description><AppDomain>JustCodeAnalysis.NET4.exe</AppDomain><Exception><ExceptionType>System.ServiceModel.CommunicationException, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType><Message>There was an error reading from the pipe: Die Pipe wurde beendet. (109, 0x6d).</Message><StackTrace>   at System.ServiceModel.Channels.PipeConnection.EndRead()

   at System.ServiceModel.Channels.DelegatingConnection.EndRead()

   at System.ServiceModel.Channels.SessionConnectionReader.OnAsyncReadComplete(Object state)</StackTrace><ExceptionString>System.ServiceModel.CommunicationException: There was an error reading from the pipe: Die Pipe wurde beendet. (109, 0x6d). ---&amp;gt; System.IO.PipeException: There was an error reading from the pipe: Die Pipe wurde beendet. (109, 0x6d).

   at System.ServiceModel.Channels.PipeConnection.OnAsyncReadComplete(Boolean haveResult, Int32 error, Int32 numBytes)

   --- End of inner exception stack trace ---

   at System.ServiceModel.Channels.PipeConnection.EndRead()

   at System.ServiceModel.Channels.DelegatingConnection.EndRead()

   at System.ServiceModel.Channels.SessionConnectionReader.OnAsyncReadComplete(Object state)</ExceptionString><DataItems><Data><Key>System.ServiceModel.Diagnostics.ExceptionUtility.ExceptionStackAsString</Key><Value>throw

   at System.ServiceModel.Channels.PipeConnection.OnAsyncReadComplete(Boolean haveResult, Int32 error, Int32 numBytes)

catch

</Value></Data></DataItems><InnerException><ExceptionType>System.IO.PipeException, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType><Message>There was an error reading from the pipe: Die Pipe wurde beendet. (109, 0x6d).</Message><StackTrace>   at System.ServiceModel.Channels.PipeConnection.OnAsyncReadComplete(Boolean haveResult, Int32 error, Int32 numBytes)</StackTrace><ExceptionString>System.IO.PipeException: There was an error reading from the pipe: Die Pipe wurde beendet. (109, 0x6d).

   at System.ServiceModel.Channels.PipeConnection.OnAsyncReadComplete(Boolean haveResult, Int32 error, Int32 numBytes)</ExceptionString></InnerException></Exception></TraceRecord>

SILENT 2010-08-03 08:29:55.868 : Server (3552): Trace: System.ServiceModel Warning: 524299 : 

SILENT 2010-08-03 08:29:55.868 : Server (3552): Trace: <TraceRecord xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord" Severity="Warning"><TraceIdentifier>http://msdn.microsoft.com/de-DE/library/System.ServiceModel.CommunicationObjectFaulted.aspx</TraceIdentifier><Description>Faulted System.ServiceModel.Channels.ServerSessionPreambleConnectionReader+ServerFramingDuplexSessionChannel</Description><AppDomain>JustCodeAnalysis.NET4.exe</AppDomain><Source>System.ServiceModel.Channels.ServerSessionPreambleConnectionReader+ServerFramingDuplexSessionChannel/34817906</Source></TraceRecord>

SILENT 2010-08-03 08:29:55.868 : Server (3552): Trace: System.ServiceModel Warning: 524299 : 

SILENT 2010-08-03 08:29:55.868 : Server (3552): Trace: <TraceRecord xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord" Severity="Warning"><TraceIdentifier>http://msdn.microsoft.com/de-DE/library/System.ServiceModel.CommunicationObjectFaulted.aspx</TraceIdentifier><Description>Faulted System.ServiceModel.Channels.ServiceChannel</Description><AppDomain>JustCodeAnalysis.NET4.exe</AppDomain><Source>System.ServiceModel.Channels.ServiceChannel/8140213</Source></TraceRecord>

SILENT 2010-08-03 08:29:55.868 : Server (3552): Callback channel faulted. Exiting server.

[Hans Kratz]

Hi Timo,

thanks for the feedback.

Unfortunately the log only shows that the CodeAnalysisServer process lost the connection to Visual Studio, most likely because the Visual Studio process crashed/exited.

Could you please check the Windows Application Log? There should be an entry for devenv.exe or .NET framework logged there each time VS crashes like this and that information will probably help us to find out what is going wrong.

BTW: You are the first to report this problem. Does it also happen if you have "Color Identifiers" enabled and create a new ConsoleApplication? Or does it only happen on the C# files in a particular project?

Regards,
Hans Kratz
the Telerik team

[Timo Pijnappel]

This also happens for new console projects.
In my Windows Error Log there was only a message from Windows error reporting:

Problemsignatur:

P1: devenv.exe

P2: 10.0.30319.1

P3: 4ba1fab3

P4: PresentationCore

P5: 4.0.0.0

P6: 4ba1f865

P7: e06

P8: 147

P9: System.IO.FileFormatException

P10: 

[Hans Kratz]

Hello Timo,

Interesting.

Does every crash of VS with "Color identifiers" enabled produce an exception like that?

Do you use a custom editor font? It can be set in the Environment > Fonts and Colors section of the Visual Studio Preferences Dialog. The default is "Consolas" and if it is not set to "Consolas" could you try with "Consolas" and see if that resolves the problem?

Sincerely yours,
Hans Kratz
the Telerik team

[Timo Pijnappel]

That's it! I used the DejaVu font (from http://dejavu-fonts.org/wiki/Main_Page). As soon as I switched to Consolas everything worked again. I could reproduce the error by switching back to DejaVu. Immediately after clicking the OK button VS crashed.

Thanks, great support! 

[Hans Kratz]

Hi Timo,

Good to hear that fixes it for you.

JustCode uses the bold style for identifier colorization. VS might have a general problem with rendering the bold styles of the DejaVu Mono font. If it is important to you could try to follow up on this with Microsoft or the creators for the DejaVu fonts.

Kind regards,
Hans Kratz
the Telerik team