Open sjmonson opened 2 years ago
@scrufulufugus thanks for the report - I've reproduced the problem locally now.
It looks like the failure is on an error path, the original problem relates to the number of samples being different between the two metrics in the expression. The crash is a cascading error because something is not correctly setup when we're logging the original error. I'll keep digging to understand why these things have happened, but should have a fix before too long since I can easily reproduce it anyway.
Description
We are using the grafana-pcp plugin to query timeseries data from PCP. Querying for a derived field, such as
mem.util.active{hostname == "$hostname"} / mem.physmem{hostname == "$hostname"}
, causes pmproxy to segfault.Segfaults are:
pmproxy[924651]: segfault at 19d0e3 ip 00005647510e2a76 sp 00007ffd0c982bb0 error 4 in pmproxy[5647510d1000+1f000]
Or occasionally:pmproxy[929076] general protection fault ip:558b5b6c6a76 sp:7ffdba257e30 error:0 in pmproxy[558b5b6b5000+1f000]
Versions
Stack Trace