[Flamechart] blacked out frames

[florianl]

Describe the issue

elastic/kibana#215697 added colors for Go frames. But instead of the Gopher-"Blue" frames are rendered in black and (with the black font color) frames becomes useless:

To Reproduce
Steps to reproduce the behavior:

• Run Universal Profiling with Go symbolization support (release 9.1+)
• Look for Go applications in the resulting flamechart

Expected behaviour

All frames in the flamechart are using their dedicated color (not black).

Screenshots

Version (please complete the following information):

• OS: Debian 12
• Browser: Google Chrome Version 135.0.7049.84 (Official Build) (64-bit)
• Kibana version: VERSION: 9.1.0, BUILD: 85765, COMMIT: 33993b7

Additional context
Add any other context about the problem here.

Errors in browser console

Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'report-sample' 'self'". Either the 'unsafe-inline' keyword, a hash ('sha256-Vf/5lhWIh6ub3ANk6a6rqRaf7x7HUixyrKDFs2axDL0='), or a nonce ('nonce-...') is required to enable inline execution.

core.entry.js:1 Fleet ConfigContext not initialized, using from plugin context
ut	@	core.entry.js:1

[GroupMarkerNotSet(crbug.com/242999)!:A0000202C4200000]Automatic fallback to software WebGL has been deprecated. Please use the --enable-unsafe-swiftshader flag to opt in to lower security guarantees for trusted content.

Kibana Cross Issues

The issue was first reported against kibana with elastic/kibana#218839. But investigation showed, that this is not a kibana but elastic-charts issue.

Also, investigation showed, that this bug is not reproducible on Mac OSX.

Checklist

• The proper chart type label has been added (e.g. :xy, :partition)
• The proper feature labels have been added (e.g. :interactions, :axis)
• Every related Kibana issue is listed under Kibana Cross Issues list and the kibana cross issue tag is applied

[markov00]

@florianl I've checked your PR and you are providing just 3 colors instead of 4 like in the rest of that map

[FrameType.DotNET]: [0x6c60e1, 0x8075e5, 0x948be9, 0xa8a0ed],
  [FrameType.Go]: [0x00add8, 0x31bee0, 0x68cce7],
  [FrameType.ErrorFlag]: [0x0, 0x0, 0x0, 0x0], // This is a special case, it's not a real frame type
  [FrameType.Error]: [0xfd8484, 0xfd9d9d, 0xfeb5b5, 0xfecece],
  [FrameType.Root]: [RED, RED, RED, RED],
  [FrameType.ProcessName]: [ORANGE, ORANGE, ORANGE, ORANGE],
  [FrameType.ThreadName]: [YELLOW, YELLOW, YELLOW, YELLOW],
};
export function frameTypeToRGB(frameType: FrameType, x: number): number {
  return FRAME_TYPE_COLOR_MAP[normalizeFrameType(frameType)][x % 4];
}

If that frameTypeToRGB is called with x === 3 then the resulting color is undefined and can cause probably that black color there

[florianl]

Great catch! I have opened elastic/kibana#219524 to fix this issue.