slidev: Chromium based browsers crash without warning
Describe the bug
When running a Slidev presentation in a chromium-based browser (I tried Arc and Chrome), the browser will close without warning after an indeterminate amount of time. When restarting Arc I get the “Arc quit unexpectedly” error with the ability to report, but Chrome provides no error. Safari appears to be working.
Minimal reproduction
Steps to reproduce the behavior:
- Create a new Slidev project
- Run
slidev --open - Wait until the browser crashes (thus far hasn’t taken longer than 20 minutes)
Environment
- Slidev version: 0.49.26
- Browser: Chrome Version 127.0.6533.120 (Official Build) (arm64)
- OS: Mac OSX 14.5
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 16 (9 by maintainers)
Commits related to this issue
- :bug: downgrade slidev because of high CPU usage https://github.com/slidevjs/slidev/issues/1826 — committed to ras0q/iosdc2024 by ras0q 2 years ago
A new version released. Hopefully, everything will be fine now.
My chrome kept crashing after 5 minutes for the past two days while trying to record for my Vite conf talk 🥲
I’m on version
0.49.29, used QuickTime Player for screen recording with slide’v builtin camera mode (so heavy CPU and memory usage).My final successful attempt was
wakeLock: false.There may be a correlation with lock screen time as well …
I’m happy to help and triage further if you can tell me what to look for. I don’t want the next person to have Chrome crashing 😅
Not sure if this is benefical, but I override vueuse (
@vueuse/core,@vueuse/math) versions from v11 to v10 and it seems stable after 30 minutes of startup.relevant commit: https://github.com/slidevjs/slidev/commit/9a1e824eb78827f9a3a68029a809dd989ecd6a75
The problem continues even with version 0.49.27. I’m not sure why, but it worked for about 45 minutes before it stopped again, even after restarting the system.
Update: I used it for an hour now and the same bug again.
Thanks a lot for the information!
<del> Does the issue still happen after setting
wakeLock: falsein headmatter? </del>I can confirm that this is caused by the wake lock. The minimal workaround should be setting
wakeLock: falsein the headmatter.Also on macOS 14.5 (23F79), Chromium based browser. After opened the localhost (start the connection), a process named
runningboarddwill immediately take up 100%+ CPU usage. It will be fine once disconnected.@ChrisLaRocque I can confirm that after pinning the slidev cli version to 0.49.24 works. Will it also solve your problem? I guess it should be an upstream problem introduced in https://github.com/slidevjs/slidev/commit/72a9285eec820cd720f2a1925b21874846f05635.