Closed gnufied closed 10 years ago
when i trigger gc, i get gc_ends_s
before gc_start
.
wowser!!
@iffyuva have you seen timestamp
on those events btw? I think, timestamp should still be correct.
This seems to be a bug indeed in rbkit
, rather than one in Qt app. I was able to reproduce the problem with pure Ruby app. Wondering, if this because of zmq
I've also seen that sometimes zmq doesn't flush messages unless there is enough data in the buffer. But this happened very randomly.
Tested this on #41 and the issue seems to have disappeared because we now aggregate messages and send them every second instead for every obj trace event. The client should get enough time to pick up messages from the zmq queue now.
This is fixed now.
I noticed that, sometimes when I am profiling and trigger the GC manually using our Qt client, no
gc_end_s
ever gets received. We need to find out why is that. It does not happen always but sometimes.