[Qt-creator] [RPCC] CallNamedPipe

[Don Reynolds]

Jaco Naude <naude.jaco <at> gmail.com> writes:

> 
> 
> Hi
> 
> I've recently moved to MSVC compiler in Qt Creator. Not sure if its 
related but today I started noticing Creator getting unresponsive for a few 
seconds now and then while I'm running my app. Sometimes it recovers and 
sometimes it hangs completely. I've noticed a bunch of messages like the 
ones below in the "Application Output" pane.
> 
> [RPCC] CallNamedPipe "\\.\PIPE\XTIERRPC_{C9A3660F-1D04-4958-B432-
B1D2D7895D3B}" with 56 bytes failed; error 2.
> 
> [RPCC] CallNamedPipe "\\.\PIPE\XTIERRPC_{C9A3660F-1D04-4958-B432-
B1D2D7895D3B}" with 56 bytes failed; error 2.
> 
> [RPCC] CallNamedPipe "\\.\PIPE\XTIERRPC_{C9A3660F-1D04-4958-B432-
B1D2D7895D3B}" with 56 bytes failed; error 2.
> 
> [RPCC] CallNamedPipe "\\.\PIPE\XTIERRPC_{C9A3660F-1D04-4958-B432-
B1D2D7895D3B}" with 56 bytes failed; error 2.
> 
> I'm not sure if this is related to the hanging, but since its been 
happening I've seen these.
> 
> Any ideas what they might mean?
> 
> Thanks
> Jaco
> 
> 
> _______________________________________________
> Qt-creator mailing list
> Qt-creator <at> qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator
> 


Has anyone else experienced this debug output?

I've seen it after closing an app. The app GUI disappears, but the app 
hangs using 20% of the CPU indefinitely. If killed, the explorer.exe 
process will continue using 20% of the CPU indefinitely until you log off. 

I don't think the products listed below are involved. It's a custom VB6 
app, written in house. It is being run in a remote desktop (terminal 
server) environment. It only happens sporadically.

What causes those [RPCC] CallNamedPipe "\\.\PIPE\XTIERRPC_{C9A3660F-1D04-
4958-B432-B1D2D7895D3B}" with 56 bytes failed; error 2. messages to be sent 
as debug output? If I run DebugView they stream constantly when the problem 
occurs.

I've never heard of Qt-creator, but this is one of two places where an 
internet search for that debug message pops up. The other is a 
vulnerability in Novel Client. We do use Novel on our Network.

Any thoughts would be appreciated.

~ Don ~