support array format of chrome event trace

[hardfist]

It seems profiler already support the following format of chrome event trace

{
  "traceEvents": [
  {
      "ph": "M",
      "pid": 1,
      "name": "thread_name",
      "tid": 0,
      "args": {
        "name": "tokio-13"
      }
    },
    {
      "ph": "b",
      "pid": 1,
      "ts": 41996.458,
      "name": "Compiler:build",
      "cat": "rspack",
      "tid": 0,
      "id": 1,
      ".file": "crates/rspack_core/src/compiler/mod.rs",
      ".line": 197
    },
]
}

but doesn't support array format(which is supported in other tools like perfetto)

 [
  {
      "ph": "M",
      "pid": 1,
      "name": "thread_name",
      "tid": 0,
      "args": {
        "name": "tokio-13"
      }
    },
    {
      "ph": "b",
      "pid": 1,
      "ts": 41996.458,
      "name": "Compiler:build",
      "cat": "rspack",
      "tid": 0,
      "id": 1,
      ".file": "crates/rspack_core/src/compiler/mod.rs",
      ".line": 197
    },
]

so I wonder whether profiler could support array format since it's more friendly when you combine multi trace file

┆Issue is synchronized with this Jira Task

[julienw]

My understanding is that we should support this too, see

profiler/src/profile-logic/import/chrome.js

Line 216 in 4765ae2

if (Array.isArray(json)) {

Do you have a profile example that we could take a peek at ? :-)

[hardfist]

@julienw trace.json this will throw following error but works fine in perfetto

[hardfist]

@julienw sorry to ping you again, do you need more extra info?

[julienw]

Thanks for reminding me.
I have a patch that makes this trace work.
@hardfist Would it be OK to include this trace or part of it in a test?

[hardfist]

Thanks for reminding me. I have a patch that makes this trace work. @hardfist Would it be OK to include this trace or part of it in a test?

thanks feel free to use it