MacOS CATransaction synchronize warning

Processing Coding Questions
1

I have a color pattern generator, WaveSynth, that uses additive synthesis of sine waves to drive animation. It can store and load configuration data with JSON files. It’s intended for use in live performance.

Concurrency became a problem in WaveSynth when opening a JSON file to load new values. The file i/o is handled in its own thread while animation continues, which is desirable in a performance. Once a file is selected, there may be an ArrayIndexOutOfBoundsException – or maybe not. That seems to happen when the JSON data changes the size of an array precisely in the middle of the animation loop. My solution was to add the keyword synchronized so that the loop would complete before any variables were changed:

public synchronized void renderFrame(int frame) {
  // load variables with prepareAnimation() at start of animation loop
  if (frame == 0)
    prepareAnimation();
  // loop through the image/signal, calculating a value for each pixel/sample
  for (int i = 0; i < this.mapSize; i++) {
    this.colorSignal[i] = this.renderPixel(frame, i);
  }
  // write colorSignal's pixel color values to mapImage.pixels
  this.mapper.plantPixels(colorSignal, mapImage.pixels, 0, mapSize);
  this.mapImage.updatePixels();
  // set our internal step variable, just a tracker for now
  this.setStep(frame);
}

// render one pixel, return its RGB value
public int renderPixel(int frame, int pos) {
  float freqShift = 1.0f;
  for (int j = 0; j < dataLength; j++) {
    WaveData wd = waveDataList.get(j);
    if (wd.isMuted || wd.waveState == WaveData.WaveState.SUSPENDED)
      continue;
    float val = (wd.waveValue(frame, pos, freqShift, mapInc) + woff) * wscale + wd.dc;
    weights[j] = val * wd.amp * this.gain;
  }
  return this.weightedColor(waveColors, weights);
}

Now I am getting a warning in the console:

2024-08-02 10:49:57.739 java[39825:8591584] +[CATransaction synchronize] called within transaction

A little research reveals this to be a MacOS event from Core Animation. I am not sure is this is a problem or not. For the moment, everything seems to work as desired. Should I be concerned?