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:

  1. Create a new Slidev project
  2. Run slidev --open
  3. 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

Most upvoted comments

A new version released. Hopefully, everything will be fine now.

Never use async inside watchEffect, especially when the async function is a DOM API 😭

My chrome kept crashing after 5 minutes for the past two days while trying to record for my Vite conf talk 🥲

image

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 …

image

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

// package.json
// I'm using pnpm
{
  "pnpm": {
    "overrides": {
      "@vueuse/core": "10.11.1",
      "@vueuse/math": "10.11.1"
    }
  },
  "packageManager": "pnpm@9.7.1+sha512.faf344af2d6ca65c4c5c8c2224ea77a81a5e8859cbc4e06b1511ddce2f0151512431dd19e6aff31f2c6a8f5f2aced9bd2273e1fed7dd4de1868984059d2c4247"
}
image

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.

It´s working again with v0.49.27. Thx for the fast fix! 😃

Update: I used it for an hour now and the same bug again.

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: 9a1e824

Thanks a lot for the information!

<del> Does the issue still happen after setting wakeLock: false in headmatter? </del>

I can confirm that this is caused by the wake lock. The minimal workaround should be setting wakeLock: false in the headmatter.

Also on macOS 14.5 (23F79), Chromium based browser. After opened the localhost (start the connection), a process named runningboardd will 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.