Web Viewer Core Plugin causes random high CPU usage resulting in Blue Screen

Steps to reproduce

  1. Activate Web Viewer
  2. Run Open a website in it and keep it running (For my case it was multiple Microsoft Word Sites)

Did you follow the troubleshooting guide? [Y]

Expected result

  • Web Viewer to run in background without any problems.

Actual result

  • In a duration of 1-3 hours - multiple moments of high cpu usage pop up from Obsidian (which can ultimately lead to blue screen).

Environment

SYSTEM INFO:
Obsidian version: v1.8.4
Installer version: v1.7.4
Operating system: Windows 11 Home 10.0.26120
Login status: not logged in
Language: en
Insider build toggle: off
Live preview: on
Base theme: adapt to system
Community theme: none
Snippets enabled: 0
Restricted mode: on

It should be noted that I can run the surfing plugin which achieves the same thing that the web viewer core plugin does with no problems whatsoever.
I came to post this bug to see if anyone else is experiencing something similar or if my machine is just feeling special.

RECOMMENDATIONS:
none


Additional information

Edition Windows 11 Home
Version 24H2
Installed on ‎11/‎3/‎2024
OS build 26120.2200
Experience Windows Feature Experience Pack 1000.26100.33.0
Processor 11th Gen Intel(R) Core™ i7-1165G7 @ 2.80GHz 2.80 GHz
Installed RAM 16.0 GB (15.8 GB usable)
Device ID 8C34DDB7-B928-4BF7-8648-819AA3203118
Product ID 00342-21968-87127-AAOEM
System type 64-bit operating system, x64-based processor
Pen and touch Pen support

This is pretty weird, and if your computer bluescreens there’s some problem at OS-level or hardware level.

If the problem was caused by Obsidian, like a memory leak, the OS would just kill Obsidian.

Anyway, let’s keep this bug report open and see if we gather feedback from other people.

1 Like

Yeah I found it so weird too. I suspected that it was my machine (maybe a new update or something). But it only happened when Web Viewer was active and running in background.

I might run deeper tests tomorrow and check system logs. But for now - I wanted to see if anyone else was running through the same problem or if its just a me problem.