Beaker: CPU usage of Beaker is very high

Created on 6 Jun 2018  路  7Comments  路  Source: beakerbrowser/beaker

Operation System: MacOS 10.13.4
Beaker version: Beaker v0.8.0-prerelease.6
Computer: MacBook Pro (Retina, 15-inch)

CPU usage is peaking into the 90%+, even when Beaker is in the background and not being used.

This is what top shows:

screen shot 2018-06-06 at 09 45 10

bug

Most helpful comment

Can you give some info about what leads up to this? Such as:

  • Did it start after the device slept while Beaker was open?
  • Do you have any large dats?
  • Are you syncing any large folders to a dat (your "local sync" folder)?

All 7 comments

Can you give some info about what leads up to this? Such as:

  • Did it start after the device slept while Beaker was open?
  • Do you have any large dats?
  • Are you syncing any large folders to a dat (your "local sync" folder)?

(Also: sorry for the problem and thanks for reporting!)

  • _Did it start after the device slept while Beaker was open?_
    No, it was like that from the moment I started Beaker.

  • _Do you have any large dats?_
    I share one dat file, namely dat://harmvandendorpel.com/

  • _Are you syncing any large folders to a dat (your "local sync" folder)?_
    As far as I understand correctly, dat://harmvandendorpel.com/ is the only dat I'm syncing.

There is only one tab open.

top looks like this, CPU percentage of process 46439 jumping around from 10% - 90%.

screen shot 2018-06-06 at 19 36 08

I'm fairly certain the cause is that your archive has a lot of history-data. The next version of Dat has performance improvements that should help with this sort of thing, but for now I suggest you create a new archive with the same content and replace it.

Same on windows
capture

@jraspiprojects that looks very much like a memory leak, or some kind of runaway memory usage. There was a fix in the latest build which fixed runaway memory usage when accessing historic versions of archives, which Fritter happened to do a lot. It might be something like that.

If you're able to reproduce it and can run a custom build, electron supports attaching chrome's remote debugger and it'd be really useful if you could isolate where that memory is getting used.

(The memory leak can lead to heavy CPU usage due to frequent GCs)

Was this page helpful?
0 / 5 - 0 ratings

Related issues

msfeldstein picture msfeldstein  路  3Comments

flpvsk picture flpvsk  路  4Comments

dasanchez picture dasanchez  路  3Comments

aaronshaf picture aaronshaf  路  4Comments

LWFlouisa picture LWFlouisa  路  4Comments