Webnovel.Forum

akuma06 I doubt it's google. If it were Google, then the problem wouldn't be this page specific. I use Edge a lot and this is the only website I am experiencing this issue with.

ArdentAngel Yup. I am aware of certain ways Windows Allocates available memory.

But, after a few days of testing, I found it was actually keeping webnovel open that forcibly causes that tablet (Asus t100 running windows 10 with 2gb of RAM) to just crash and turn off (no bluescreen error).

It is processor related issue.

Since then, i only peek at Webnovel to check or read my chapter for comments and close it. I never keep it open anymore. It's really is less of a RAM issue and more of Processor usage by Webnovel which is odd.

I can run everything else Discord, Youtube and other tabs on Edge with no issue of a crash (Simulataneously at that) while using word.

But if I run just any other page while webnovel is running in the background as I type on word, it will just shut off my tablet unexpectedly. At first I thought I ruined my processor since it is already 6 years old anyway. But after just closing Webnovel everytime, it never crashed, even when I left Youtube playing in the background with 3hour videos of instrumentals playing.

ArdentAngel Thanks for your hard work. It's really a big issue.

ArdentAngel
Uh, sorry. I am unable to test it out on that specific laptop because it was a school laptop. But I think it was the Dell Latitude 5590? not quite sure. I can try to see what happens to some of my friend's laptops tomorrow when I only open webnovel. (everyone is given the same laptop)

Olivia I kind of doubt it is laptop specific... But yes, please try.
If anything, it might be connected to the CPU provider/manufacturer (Intel or AMD), since I only have an Intel processor (and all my PCs have Intel processors, so I can't verify using any with AMD).

ArdentAngel Okay, tried and tested. The laptops did have Intel processors but I also tried with one of my personal laptops with AMD processor.

I only opened and loaded all 7 chapters of the novel from my original screenshot. (same laptop model) But that was a few % difference, between having it as a foreground and background tab. there was not a difference between the results from my original and the new results.

But It became really interesting when I tried with one of my other laptops (with the AMD processor)
(I only opened the novel and this forum post)

I loaded the entire novel and kept it as a foreground tab.
When I swicthed to background it settled at around .5%
It hit 50% when I was loading the entire novel. This is a screen snip from the settings.

So yes, it is very likely processor related but I know nothing about stuff like that and I need a larger sample size/ more knowledge before I conclude anything. summoning smart people

dapenggaofei I just noticed that another page seems to be having the same problem. It isn't merely the Chapter reading page, it is also novel's info/details page which causes the same CPU spike. It might really have something to do with Comments, since similar system is present on both pages (though it is reviews in the case of novel's details).

ArdentAngel

Could it be the OS? The laptop the original Screenshot is taken from had an education version of windows, just like my friends. The AMD has the normal home version. I can try with an Enterprise and Education version later if daddy is giving me access.

One of my computer is on Windows 10 Pro, another personal on Home edition and both have this bug on Edge when I tested last time.

ArdentAngel It's just a search result when I quickly looked into it.
I confirm that the page: https://www.webnovel.com/book/8334291405006505 also have the bug (cpu around 50% on my personal computer).

Plus it seems @ArdentAngel is right. After another lookup on the page mentioned just above, the review system eats a lot of cpu.
According to my performance analysis, something is reloading the dom disposition of the reviews every 240ms. This is causing 50% of the cpu usage and the more there are reviews and the more it is cpu consuming.

Every cpu pick in the analysis is a disposition with the same profile when expanding.

I still run Windows 7 on my desktop which is running 8gb of Ram and an i5-2400.

For this desktop, the CPU usage of the Webnovel page is 5-7% compared to just 2% for other chrome tabs (even compared to youtube)

on the Apple Ipad and Android App, prolonged reading also causes it to be taxed by the Webnovel App so something is definitely eating up resources on the devices, other than just memory which is processor related.

So we have the issue on IOS, Android, Win 7 and even Win 10. We just dont have a sample from OSX (Safari) but it is basically that Webnovel itself is eating up the processor power of every device we use on it.

akuma06 https://www.webnovel.com/book/8334291405006505 this page cost nearly 0% CPU of my chrome 67 of OSX. I will check the CPU cost in Edge of windows.

dapenggaofei It is not immediately visible, but to me it seems that CPU fluctuations are bigger. Without this tab it fluctuate 3-5%, while with this tab it fluctuates between 3.5-10%.

Again, I'm testing this with 20 tabs open, which means it might be slightly inaccurate, but that't my impression. I agree that the spike on Novel's Details is lesser than Chapter page.

dapenggaofei According to my analysis using MS Edge Performance tool, 77% of the CPU usage is due to a function called from: https://www.yueimg.com/en/js/common/utils/raven.62118.js to a function from the following script: https://pagead2.googlesyndication.com/pagead/js/r20180627/r20180604/osd.js

What this function does, ultimately (and most time consuming), is utilizing a browser built-in function to get clientWidth on a Timer. Whether the problem is in the way you periodically call this function or something else entirely is not easy to tell without the original source (since minimization makes the code barely readable), but it'd be great to hear from the official response on the progress of their investigation… So we know we aren't the only ones investigating this...