Electron CPU usage

[Mykle1]

@djsunrise19 said in Electron CPU usage:

But a few days ago, there were an github update. Since that update my mirror is unusable. Why?

Since you are addressing me directly, I will answer, directly and plainly. I don’t know why your mirror is now unusable. I joined this topic because I was/am interested in determining why some people have this problem and others don’t. We have eliminated some possibilities but not all. I can sympathize with you, having struggled with problems of my own. There only seems to be a handful of people experiencing this problem. I am not one of them but I am trying to determine the cause using what little knowledge I have.

[djsunrise19]

@Mykle1 I’m sorry. There is nothing directly to you. I only try to write as much as I find out in that situation to know as much as we can. I’m very thankful that you’re trying to help (and didn’t have our transition problem).

[Mykle1]

@djsunrise19 said in Electron CPU usage:

I’m sorry. There is nothing directly to you.

No worries at all my friend. We’'ll just keep trying and maybe others will get involved and help us figure this out!
Peace!

[mibafz00]

I’m joing the discussion because I’ve exactly the same problem.
Complete new RPi3 + clean installation but CPU load up to 320%.

Hardware: BCM2835
Revision: a02082
Micro SD: SanDisk Ultra 16Gb

At the moment I can not bring any new hints but you’re not alone ;-)

[Mykle1]

@mibafz00 said in Electron CPU usage:

At the moment I can not bring any new hints but you’re not alone ;-)

The more people that share their information, the better able to diagnose the cause. So, thank you for your input.

Wait!

I have another idea. I will assume all risks.

I will buy one of the troubled Pi’s from someone in this topic. It has to be a:

• Pi 3 B
• Hardware: BCM2835
• Revision: a02082
• SD card, 8GB minimum
• Power supply

That’s right. I will pay you a fair price before you even ship it to me. I’m thinking PayPal. You’ll be paid with no risk to you at all.

So, if you are completely frustrated and you’ve had it with your current Pi (described above), sell it to me.

Does $25 US Dollars sound fair? I am buying something that has a problem, after all.

Who knows, I just might solve the CPU usage issue!

Why are you doing this, Mykle?

Because I like challenges and I like projects. I very well may wind up with a $25 brick, but the enjoyment I get from tinkering and troubleshooting is worth the cost to me, and you get something back. Just don’t send me an actual brick after I pay you. :^)

Anyone interested?

• Message me or post something here.

[pedroken]

Guys, same problem here.
Hardware : BCM2835
Revision : a22082

I just realized something. I’ve installed the MM in a clean Jessie. Results were:

I have an old backup from my first attempt with the MM, and the results (with same few modules) were:

But after 3 hours, look what happened:
A severe memory leakage. I tried with only the default modules, same thing happened. After sometime, the MM crashed. On screen log was showing free list.h:118 Memory corruption chromium.

I`m sure that the version of MM is different from one and another. Someone can tell me how can I see this? Thanks!

PS: Great initiative, @Mykle1 !

[Mykle1]

@pedroken said in Electron CPU usage:

PS: Great initiative, @Mykle1 !

I’m just trying to get to the root of this problem. I may never figure it out but I will certainly try.

Nothing ventured, nothing gained.

[roramirez]

@pedroken I think this can because the Electron version. Can you tell us what version is for two case.

You can see into the file node_modules/electron/dist/version

[Mykle1]

@roramirez said in Electron CPU usage:

I think this can because the Electron version.

Thanks for getting involved here. Just for reference purposes, my Electron version on my Pi 3 B is v1.4.15

[wtidwell]

@Mykle1
Sorry for the radio silence, it’s been busy lately.

I can see what electron version I’m running tomorrow night, and I’ll try and change it to the same version you seem to be getting good performance on and report back.