firefox-devtools / firefox-devtools/profiler
Can't record audio workloads for a long time
- Dominant language
- TypeScript
- Stars
- 1.5k
- Forks
- 491
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 30
Description
I'm using Firefox 99.0.1 .
Right now I have the problem that I can’t record profiles for a long time in Firefox (< 10s) anymore, when recording audio workload. It used to work better in the past (I think).
When I try, I get the following error when the FF Profiler opens:
> Error: DataCloneError: JSWindowActorParent.sendAsyncMessage: JSWindowActorParent serialization error: data too large, in actor 'WebChannel'
In his blog post [Profiling real-time audio workloads in Firefox](https://blog.paul.cx/post/profiling-firefox-real-time-media-workloads/) padenot mentioned that his configuration of the FF Profiler allows to record for a very long time. I also tested with karplus-stress-tester (https://jackschaedler.github.io/karplus-stress-tester/) like he did, but it doesn't work for me anymore.
Repro:
Open karplus-stress-teste
Select a high number of strings like 600
Click start audio
Click strum all
Start recording in Performance tab
Wait about 15 seconds
Capture recording
-> FF Profiler opens and shows the error message.
I configured the Profiler like it is described in the last video of the blog post. The options that are new since then I tried enabled and disabled, but it didn't show an effect for me.
It would be interesting if anyone else runs into this problem.
┆Issue is synchronized with this [Jira Task](https://mozilla-hub.atlassian.net/browse/FP-544)
Contributor guide
Research direction
Reproduce the failure in Firefox 99.0.1 using karplus-stress-tester with about 600 strings, then start recording from the Performance tab and capture after 15 seconds. Begin at the FF Profiler capture flow and the WebChannel DataCloneError; done means the recording opens in the profiler without the data-too-large error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100