Wednesday, October 18, 2017
Frames dropped issue
After leaving spicy run overnight on the 3D Helvetica Clock animation, it was consuming about 1.87GB of memory. In that particular scenario, it is definitely accumulated frames, since Spicy is presently about 4 hours late!
channel-display-gst.c:214: [58469336 62257.418151] gst_schedule_frame_warning: Rendering too late by 16065622 ms (ts: 427024879, mmtime: 443090501), droppingchannel-display-gst.c:214: [58469346 62257.418195] gst_schedule_frame_warning: Rendering too late by 16065605 ms (ts: 427024896, mmtime: 443090501), dropping channel-display-gst.c:214: [58469356 62257.418208] gst_schedule_frame_warning: Rendering too late by 16065590 ms (ts: 427024911, mmtime: 443090501), dropping
Flight recorder
Added long-wanted support for a slider that can send values to the targetted process in real-time.
Added a a better way to compute the graph scale when there are large values, so that it is rounded, but not too much:
Added error logging for various error cases, e.g. mmap() error.
Added usage information and -h option.
Activated logging for errors and warnings. So now I get something like:
../recorder.c:1118: [18 0.000189] recorders_error: Unable to open /tmp/recorder_share for reading: No such file or directory (2) Unable to open recorder shared memory '/tmp/recorder_share'
Misc
Interview with candidate.