我试图使用命名管道在windows服务和wpf应用程序之间进行通信，这两个应用程序都是用vb.net编写的。Windows服务始终在运行。
但是，在运行wpf应用程序几个小时后，将抛出aStackOverflowException。
wpf应用程序中的PipeServerThread()是发生异常时在托管堆栈中重复调用的唯一函数（我使用WinDbg对此进行了跟踪）。
服务包含NamedPipeClientStream，应用程序包含NamedPipeServerStream。
当客户机和服务器通信时，服务器在几次检查之后读取最终的客户机响应，然后将clientstring传递给代码中其他地方的函数。
然后刷新、关闭并释放pipeserver。
然后再次调用PipeServerThread()以创建另一个用于通信的管道服务器。注意，此pipeserverthread（）被重复调用。
有没有人能说明代码中的什么最终导致了StackOverflowException的发生？
PipeServer：
Dim PipeServers(1) As Thread
PipeServers(1) = New Thread(AddressOf PipeServerThread)
PipeServers(1).IsBackground = True
PipeServers(1).Start()
Private Sub PipeServerThread()
Dim ps = New System.IO.Pipes.PipeSecurity
Try
ps.AddAccessRule(New System.IO.Pipes.PipeAccessRule("Users", System.IO.Pipes.PipeAccessRights.FullControl, System.Security.AccessControl.AccessControlType.Allow))
ps.AddAccessRule(New System.IO.Pipes.PipeAccessRule("CREATOR OWNER", System.IO.Pipes.PipeAccessRights.FullControl, System.Security.AccessControl.AccessControlType.Allow))
ps.AddAccessRule(New System.IO.Pipes.PipeAccessRule("SYSTEM", System.IO.Pipes.PipeAccessRights.FullControl, System.Security.AccessControl.AccessControlType.Allow))
Dim pipeserver = New System.IO.Pipes.NamedPipeServerStream("testpipe", Pipes.PipeDirection.InOut, 10, Pipes.PipeTransmissionMode.Byte, Pipes.PipeOptions.None, 4024, 4024, ps)
Debug.WriteLine("Pipeserver waiting for connection")
pipeserver.WaitForConnection()
Try
'Debug.WriteLine("Pipeserver now within Try block.")
Dim ss As New StreamString(pipeserver)
'This server writes to pipe immediately on connection
Debug.WriteLine("Server now writing to Pipe")
ss.WriteString("Hello Client. Who are you?") 'Action 1 - server writes to Pipe
'Response from client is read
Dim ClientName As String = ss.ReadString 'Action 4 - server reads from Pipe
Debug.WriteLine("Client's name is: " & ClientName)
If ClientName = "PipeWriterService" Then
'The client is the PipeWriterService
'Tell it what state is being requested
ss.WriteString(RequestedCommState) 'Action 5 (if) - server writes to Pipe
Else
'The client is someting else
ss.WriteString("wrong client") 'Action 5 (else) - server writes to Pipe
End If
Dim ClientResponse As String = ss.ReadString()
Debug.WriteLine("Server has read client Response as: " & ClientResponse) 'Action 8 - server reads from Pipe
DeviceInfo.Dispatcher.BeginInvoke(Windows.Threading.DispatcherPriority.Normal, New OneArgDelegate3(AddressOf ProcessPipeString), ClientResponse)
Catch ex As Exception
Debug.WriteLine("Error is Server Try block: " & ex.Message)
End Try
pipeserver.Flush()
pipeserver.Close() 'Action 9 - server closes Pipe
pipeserver.Dispose()
Debug.WriteLine("PipeServer now closed")
Catch ex As Exception
End Try
Call PipeServerThread()
End Sub
PipeClient：
Private Sub PipeWriter(StringToWrite As String)
Dim pipeClient As New NamedPipeClientStream(".", "testpipe", PipeDirection.InOut, PipeOptions.None)
Try
pipeClient.Connect(50)
Dim ss As New StreamString(pipeClient)
'Once a connection is established, Server will write to pipe first
'This is read by the client in the line below
Debug.WriteLine("First string from Server: " & ss.ReadString()) 'Action 2: Client Reads from Pipe
'Server is now waiting. This client responds with its name
ss.WriteString("PipeWriterService") 'Action 3: Client Writes to Pipe
'Server will respond again
'This is read by the client in the line below
RequestedCommState = ss.ReadString() 'Action 6: Client reads from Pipe
Debug.WriteLine("Second string from Server: " & RequestedCommState)
'This response contains the desired 3G comm status from the server
'Server is now waiting. This client responds with whatever it wants to say to server
ss.WriteString(StringToWrite) 'Action 7: Client writes to Pipe
Catch ex As Exception
Debug.WriteLine("Error in PipeWriter. Error is: " & ex.Message)
End Try
End Sub
最佳答案
可能你已经解决了这个问题。
无论如何，问题是在pipeserverthread（）上重新递归调用。每次调用它时，堆栈的大小都会被提升以容纳本地变量和函数的返回地址。
必须去掉递归调用，并将函数体放入循环中。