search

pothosware / PothosCore

The Pothos data-flow framework
https://github.com/pothosware/PothosCore/wiki
Boost Software License 1.0
302 stars 48 forks source link

Strange error with one source to meany Message Printers #122

Open ashley-b opened 7 years ago

ashley-b commented 7 years ago

If i set up a message source or noise source -> stream to packet -> two or more Message Printers, the topology runs and then stops randomly. It only does this when running in the GUI and when both Message Printers are set std::cout or std::cerr (works if loging to poco). This does not seam to happen from PothosUtil commandline. I get the following error [03:23:05.704846] PothosGui.TopologyEval: Failed to commit: I/O error: RemoteProxyEnvironment::transact(): connection inactive [03:23:05.705632] PothosGui.EnvironmentEval: zone[]: I/O error: RemoteProxyEnvironment::transact(): connection inactive - Remote environment crashed [03:23:05.786087] Pothos.Topology: Topology destructor threw: I/O error: RemoteProxyEnvironment::transact(): connection inactive This is using current master 894b5cb2b898ebf7d33f1c96e7fd141a395fd196 Guessing some sort of race with redirection of std io into the GUI

guruofquality commented 7 years ago

Just to comment. I have seen this happen, the process producing the logging message has died. Probably due to overloading some logging buffer. The difference with the GUI is that there is some syslog forwarding setup between the executing process and the GUI, which is done through poco. I cant say yet if its a bug in poco syslog forwarding or something else.