Automated compile possible issue?

[AScustomWorks]

I'm not sure about what to look for about this, so I'm asking for help:

Somehow the BPM clock module on AS modules from the automated compile is doing something strange for one Mac user(with OSX 10.8.5.)

When he sets the bpm clock value below 100 the display stops working, also the signature display settings are working strange.

Some other users tested it without any problems so I'm wondering if the automated compile + that particular combination of OS could cause the issue?

The same user tested the module with the compiled plugin I uploaded to github, everything worked fine.

This is the code running on the module, working fine since v0.5:

//initial value for tempo
 float tempo =120.0f;
//on step();
tempo = std::round(params[TEMPO_PARAM].value);

//BpmDisplayWidget drawing code
    float *value;
    std::stringstream to_display;   
    to_display << std::setw(3) << *value;
    nvgText(vg, textPos.x, textPos.y, to_display.str().c_str(), NULL);

//BpmDisplayWidget instantiation 
  BpmDisplayWidget *display = new BpmDisplayWidget();
  display->box.pos = Vec(23,45);
  display->box.size = Vec(45, 20);
  display->value = &module->tempo;
  addChild(display); 

Screenshot from the user showing the error(using the plugin downloaded from plugin manager):

My tests on Mac and Linux trying similar settings(Mac version tested with both local and pm compiles, Linux tested with local compile):