InterviewSolution
| 1. |
Solve : Problems with Google Chrome? |
|
Answer» I do a lot of work on the internet so I'm pretty much always running multiple tabs. I just switched to Firefox because it seemed LIKE Chrome would lose its connection to the internet after a while of running multiple tabs. Has anyone else run into this problem? I ran all the necessary updates but it just randomly loses connection. Checked my wi-fi .. all good, and ran other browsers immediately after the error with no problems. Any info would be appreciated. Thanks!Approximately how many tabs are open when this happens? Is Chrome stable with a small number of tabs open? Have you observed any relationship to length of time online with Chrome? In addition to the former. Actually Google Chrome requires high internet speed.Define high internet speed. Quote from: garry6stephen on December 21, 2010, 10:46:46 PM I think when you open multiple tabs, Google chrome automatically works slowly,Non-sense. That's simply not true. I've never seen any documentation that Chrome needs any faster speed connection than any other browser. A lot of it depends on what tabs, or websites, are open, and if they do automatic updates. That will take up bandwidth and CPU cycles depending on how often they update. I use Firefox as my main choice, and Chrome as my second choice, and I have never seen any problems with either with multiple tabs open. Quote from: soybean on December 21, 2010, 10:54:29 PM Define high internet speed. One browser may load a webpage faster than other browser on same internet connection. But you can use any browser with any internet connection (as long as you can install it on your machine, that is)Quote from: 2x3i5x on December 22, 2010, 12:17:53 PM One browser may load a webpage faster than other browser on same internet connection.No. The only difference will be in rendering time, and those differences come at different prices. If you really wanted the fastest possible rendering then you'd find some skunk works "superspeedy browser" that parallelized the drawing of every single element into a set of threads and pegged the CPU(and all cores on that CPU) for however long it takes to finish rendering. No display would be shown until the results had been acquired- no progress load no nothing. The toolbar wouldn't even respond- after all, redrawing the button would mean taking precious power from rendering the page, which would *gasp* make it slower!, What people are comparing half the time when they say "Browser X is faster then browser Y" is perceived speed, not actual speed. Things don't SEEM to take as long when you know how long is remaining. There have been a number of experiments done in this regard for years; such as having a document re-paginate (back when it would take long enough to be usable in this test) and show a progress bar versus not showing any output; First they had a version of the program that pretty much pegged the CPU, showed no output, and quite literally tried to re-paginate that document as fast as possible. Then they used a version of the same program which was more "co-operative" with the system in that it yielded to other applications, it drew a progress-bar/% complete thing during the entire process, and so forth. Despite the new version taking almost 25% longer, users on AVERAGE reported a dramatic increase in the "speed" of the program. This is absolutely no different with browsers. All Browsers running on the same OS will download data at nearly the same rate. (They can provide bullet points like "streamlined download pipelining" but it's all a load of nonsense.*) Once those files are downloaded- and probably during - it renders the page. Some browsers render as elements are loaded, others try to "predict" where the elements will appear on the page (so there isn't a lot of stuff moving around during the load). Firefox waits a second or so to start rendering a page (the idea being that within a second there should be "enough" of the page for it not to be a confusing mess). Others wait longer, or don't even bother to render until after the entire thing is downloaded. All of this results in different perceptions about the speed that often do not coincide with the actual speed's in question. But Again, as has been reiterated so many times; it doesn't make a *censored* bit of difference what browser you use. People like to make these claims that "well, if a page loads on average a tenth of a second faster and you browse through a modest 500 pages a day, you're saving over 50 seconds! Then they do all sorts of statistical munging like saying "and that translates to over 5 hours of time you save by using this browser B!" Thing is you can take any obscenely small time savings and multiply it into larger time scales so that it seems relevant. If I have a pot-hole on the road that takes me an extra quarter second for me to go around, do you think the City would care that I waste 3 minutes a year doing so? Seems insignificant! but if I become a cyborg and live for 5 million years, that's over 28 years! well they'll have to do something then! This is made worse because often times the "statistics" that are being munged aren't even measured statistics, they'll be perceived statistics, so they'll go around and ask people "how much faster does browser A feel to you" and the people might say "feels about a good half second faster at least for each page" so of COURSE at this point it's important to note that sometimes the browser that "feels" slower is in fact measurably faster then the other, so the overinflated munged and contrived statistics are in fact completely meaningless. This no doubt finds it's way into even the most studious benchmarks, as the people performing the test are almost always biassed, so when they run their "preferred" implementation, they'll make sure to do stupid stuff like disabled all sorts of background processes and other tasks. But they won't often show the same care for the other side. Personally, unless somebody can quite literally produce a process Monitor log that quite clearly shows a time difference between browsers, it's all a bunch of opinions being held as fact. And even if somebody does measure it, who the *censored* cares? We also waste time eating and sleeping, should we try to shave precious tenths of a second off every sandwich we make? of course not. *I have quite literally toyed with this. I would ask some of my small set of computer savvy friends something like "did you know that Browser A has Deluxe TCP/IP channeling?" And either they'd pretend they knew or be genuinely curious and actually switch to that browser based entirely on a nonsense feature that I didn't even explain.I have had numerous problems with Google Chrome.... fortunately they are getting less... Less Flash Crashes, less freezes. One solution that solves a lot of Chrome problems is to clear the Cache regularly and Browsing history. When these get cluttered, chrome slows down! i don't think the number of open windows is the issue, but people like me who open a number of windows regularly also tend to build up a large cache and history files. I have two chrome problems that that seem to remain... and WOULD APPRECIATE HELP ON THESE! I also continue to have numerous problems with Firefox that persist on Windows 7. Firefox is slow to start or does not start at all .... cancel it in the task manager and try again.... Occasionally Chrome will not accept 'box input', eg a user name in a box... it will just return to say 'enter user name' or something. The other remaining problem is that it does not warn me that a site is trying to open a pop-up that I might like to see. Then it seems that the site is not working. I have learned to switch over to Firefox on these occasions.... try giving Chromeplus. It's a chrome based browser, and it has other features not coming with chrome directly (or can be added with extensions), including IE Tab. First unistall your browser and reinstall in your computer to recover the problem. |
|