Javascript 传入的推送器消息使Visual Studio 2015崩溃-从管道读取时出错：无法识别的错误109（0x6d）

我使用Pusher在web API和网站之间进行通信。收到消息Visual Studio崩溃后，如果我正在使用Internet Explorer 11进行调试。在Chrome中调试时，一切正常

示例消息：

"NOBRACG9GLGDGFWM5GFWAYB070BOWAIAHGJ4IWC2APTEJOVHGNMADIWB51T9MJNADJJJGCsATHZ4AYJAVEVACQADGJJJGZ2KOLLFncKGRIDB/ABOUCISYDK7GNY7UdK7G7G7UdK4AEZUK4RFQA55LGX8FB4ALJESAJXAKJAKJAKJAKZ2BJJ2BJ2BJZ2BJ2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2K2KERNEQ9DDOPHBAC2C2SEKHVER1BRAKRGJUW062WAUKMHRICATIU8AGRMSL+C5XEZPAGWYOWZTMZQVAQGKCSRAYGOADUKBCECO4RBGXHLVDLCOAHUAHUAJCPTXPJEYNQCFQKJOTP54CLJDPYDW9QABZ5TQBXUML2UO87OQKCRFL9GQEKAXWAUKA==”

我发送的信息如下：

var myMessage = LZString.compressToBase64(myJsonObject);
var pusher = new Pusher(appId, appKey, appSecret, new PusherOptions { Encrypted = true, Cluster = cluster });
pusher.Trigger(channel, event, myMessage);

var pusher = new Pusher(AppKey, {
    authEndpoint: myAuthEndPointUrl,
    cluster: cluster,
    encrypted: true
});

var myChannel = pusher.subscribe(channel);
myChannel.bind(event, function (data) {
    debugger;
});

这样接受：

var myMessage = LZString.compressToBase64(myJsonObject);
var pusher = new Pusher(appId, appKey, appSecret, new PusherOptions { Encrypted = true, Cluster = cluster });
pusher.Trigger(channel, event, myMessage);

var pusher = new Pusher(AppKey, {
    authEndpoint: myAuthEndPointUrl,
    cluster: cluster,
    encrypted: true
});

var myChannel = pusher.subscribe(channel);
myChannel.bind(event, function (data) {
    debugger;
});

收到消息Visual Studio崩溃后，事件日志中出现以下错误：

Error Handler Exception: System.ServiceModel.CommunicationException: There was an error reading from the pipe: Unrecognized error 109 (0x6d). ---> System.IO.IOException: The read operation failed, see inner exception. ---> System.ServiceModel.CommunicationException: There was an error reading from the pipe: Unrecognized error 109 (0x6d). ---> System.IO.PipeException: There was an error reading from the pipe: Unrecognized error 109 (0x6d).
   at System.ServiceModel.Channels.PipeConnection.OnAsyncReadComplete(Boolean haveResult, Int32 error, Int32 numBytes)
   --- End of inner exception stack trace ---
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.ConnectionStream.EndRead(IAsyncResult asyncResult)
   at System.Net.FixedSizeReader.ReadCallback(IAsyncResult transportResult)
   --- End of inner exception stack trace ---
   at System.Net.Security.NegotiateStream.EndRead(IAsyncResult asyncResult)
   at System.ServiceModel.Channels.StreamConnection.EndRead()
   --- End of inner exception stack trace ---
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.TransportDuplexSessionChannel.EndTryReceive(IAsyncResult result, Message& message)
   at System.ServiceModel.Dispatcher.DuplexChannelBinder.EndTryReceive(IAsyncResult result, RequestContext& requestContext)
   at System.ServiceModel.Dispatcher.ErrorHandlingReceiver.EndTryReceive(IAsyncResult result, RequestContext& requestContext) \r\n    at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.TransportDuplexSessionChannel.EndTryReceive(IAsyncResult result, Message& message)
   at System.ServiceModel.Dispatcher.DuplexChannelBinder.EndTryReceive(IAsyncResult result, RequestContext& requestContext)
   at System.ServiceModel.Dispatcher.ErrorHandlingReceiver.EndTryReceive(IAsyncResult result, RequestContext& requestContext)

及