Olivia Also, as FillerArc mentioned, the Chapter tab must be the foreground tab. The moment you switch it to background, the CPU spike disappears entirely. So try testing this out as well.

    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.

        17Sphynx17 It's also the reason why I opened a threat nearly 2 weeks ago about Webnovel using too much CPU (https://forum.webnovel.com/d/8226-website-needing-enormeous-amount-cpu), but unfortunately the only response I got there is from the one who opened this thread, so I added all the information I acquired by testing the page here...

        I really don't mind the amount of RAM it uses for me, because I know browser is fully capable of unloading the page, or parts of it anyway. Sure, it will take a while to open and load, it might also become slightly laggy, but that would be true for that page only, maybe also a bit for the browser, but not the whole device/tablet the way overloading CPU does.

        Hence CPU is the only real issue I have with Webnovel as well.

          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

                Olivia Well, that's interesting.
                My processor is: Intel i7-6600U

                Which means it isn't manufacturer specific but there might be something else at work here… Unfortunately I'm also at a loss…

                Also tested with Intel Core 2 Duo E8400. An older processor. The same problem applies here as well, which means that your Intel processor might be an exception...

                  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.

                      Olivia i also had these high ram usage issues on android 4.4. while using the app.
                      After reading a while and letting the tablet sit for a few hours, the app uses so much resources that the whole tablet had short freezes and the app was unusable.
                      Only after unlocking bootloader and flashing a newer version (7.1) the app runs smooth now.
                      So I dont think its the educational versions of windows causing it.
                      My guess is also a problem with the implementation of comments/reviews which loads in the background.
                      Why it isnt happening on every system/device is strange though

                        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.

                            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 Yeah the screenshot comes from Edge. Chrome is not that high in CPU usage, it is on average around 4% and can go up to 40% when the page is rendering (which is not that high considering it is temporary) on this computer.

                              The thing is that I don't fully trust Edge dev tools. At least they aren't as user friendly as the ones in FF or Chrome. So it might be hard to pin point what is causing this in Edge :/.

                                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...

                                  7 days later

                                  ArdentAngel So we get the same result :'). I've also found that script as one cause for the high cpu percentage. If I'm right, it seems that a js function is re-rendering the comments/reviews every x.xx seconds and this function is called for each comment/review which is leading to a high cpu usage.
                                  What is still bothering me is the difference in behavior between chrome and Edge when encountering the script. It might be due to how V8 works.

                                    akuma06 If you ask me, Chrome is allowing far less freedom for everything needing resources. Hence it is lagging even when I'm just scrolling down the page using touch. It isn't as much of a problem when using mouse/trackpad, but scrolling one screen-height down without a momentary freeze of around half a second is nearly impossible when I'm reading novels on any website.

                                    It's the reason I love MS Edge for reading so much.

                                    This creates an illusion that it needs less resources, but in truth it just compensates for them in other ways. At least that's my take on things, so don't hold me accountable for my opinion. There is no technical proof for any of it, merely my experiences when using both browsers (each dedicated for a different use - Edge for reading, Chrome for research/extreme multi tabbing).

                                      15 days later

                                      ArdentAngel Sorry for that, We found It's a bit complicated, recently our fe team members are focusing on the mobile lite. Now that the new version is released, We will manage to solve this. Thanks for reminding us.

                                        5 days later

                                        MasterRabbink I was frustrated due to not hearing from him for a month without any notice about them even looking into the issue... Now that dapenggaofei clearly stated his reasons and plausible timeframe, it's OK.

                                        I mean, all we got was a short "We will find what's the problem." from dapenggaofei and even that was for the issue with RAM. And another short acknowledgement of a possible of an issue upon my report.

                                        I just hate it when I can't read using MS Edge, because it gives me the smoothest experience when reading novels online...without my computer burning my legs while having it in my lap.

                                        Maybe I just expected something like, "We are looking into this issue right now." or something. Now that I know what the problem for this late reply of when they'll look into it is, I'm contend. For a time, at least. :P

                                          I hibernate every app before reading on phone 😉

                                            8 days later

                                            ArdentAngel Do not be frustrated...We are still working on this issue. We will have a small release for some enhancement to fix this issue. But as i analysed, this issue may caused by the interaction of several reasons, it's a little bit complicated. I will notify you if this release is done, and i hope it can help.

                                            ArdentAngel I understand you, resolving a bug (when you have multiple platform with different code base to support) can take a long time. Really, a month is not that long depending on the workflow (versioning, commits, branch, ...). I'm just saying this because I often see people (not you particularly) asking to resolve a bug and hoping it disappeared the next week. Generally, even if the bug is simple to resolve (a forgotten parentheses for exemple), you still need time to push it on the main branch and then upload it to the server (testing time for example).

                                            renjialelele The cpu usage for Edge on my end seems to be in a normal range. 3 to 7 percent while doing nothing or moving the mouse on the page. Around 10-12 percent while scrolling. However it seems Edge is a bit hungry (overall on websites) when scrolling (tested on some random websites), so it seems the bug is no more.

                                              renjialelele It is a lot better, at least my machine isn't overheating anymore, but there is still a spike.

                                              When in Library (I have 12 tabs opened while testing this while only a single tab is Webnovel website) CPU usage ranges 1-5%, while when I open a chapter it spikes to 7-13%.

                                              For information, while in the Webnovel forum (this thread), CPU usage fluctuates between 4-9%.

                                              You did manage to lower it to manageable margin though, so I won't really complain anymore. But if you do manage to lower it some more, I'll surely be even happier. ;-)

                                              PS:
                                              My tests are always based on not moving the mouse, scrolling, or anything at all while having that particular tab active in Edge and having Task Manager opened (as an active window) while monitoring CPU usage - unlike how akuma06 made his tests.

                                              akuma06 I agree, for some tasks Edge might be slightly hungrier, but it's its smooth operation which compels me to use it for reading purposes nearly exclusively in the first place, hence I'm not complaining about it's greediness while operating with the website but only for when everything is idle (and I always wait for cca. a minute for CPU consumption to stabilize as much is it is going to before taking my measurements).

                                                akuma06

                                                ArdentAngel OK, thanks a lot ! This release is the first step to improve the performance on Edge. If we have further release we will let you know~

                                                  2 months later

                                                  rainsmith Product placement - Are you being paid to do this or are you a living advisement?

                                                    3 years later

                                                    looks like this bug is still alive, 3 opened tabs with novels and it already uses 7-12 out of 16 GB RAM. and whole pc is lagging.

                                                      Write a Reply...
                                                      Web Novel Novel Ask