I've been working on a project from my laptop for the past few months. When webpack compiles my code, reloading the page takes around 1 second.
I've now moved to my desktop, and loading the page takes about 11 seconds in Chrome. I'm using the same version of node, webpack-dev-server and webpack on both machines (windows 10).
Chrome:
Edge:
Blazing fast in Chrome on my other machine:
I've also disabled all the extensions to no avail. I can't find a pattern, but this is not consistent on edge, it would load for the same 11 seconds there as well, but not always. Any ideas how i could address this?
This wasn't related to webpack at all, it just looked weird. The issue seems to have something to do with steam (or steamVR), and there was a bug report for chrome:
https://bugs.chromium.org/p/chromium/issues/detail?id=1202090#c38
Opening two tabs, and reloading them side by side would not suffer from this 11 second delay. Updating steam seems to have resolved the issue.
Related
I'm just curious - have any fellow Neo4j-ers ever encountered this behavior?
Right now, I've got 30 queries in the 'Saved Scripts' part of the Neo4j browser interface. When I try to save another, it will remain there until the the page is reloaded/refreshed - it then disappears.
I thought that 30 might be some soft limit determined in a Neo4j configuration file (/etc/neo4j/neo4.conf) but I can't find any statements in the file relating to this. If it's at all pertinent, I'm running x64 CentOS 7 as a VM - this is where my Neo4j has been configured. I've checked the debug logs and I don't see any warnings or errors relevant to this issue.
Is this behavior normal? If so, is there a way to change it?
I solved the problem. Just needed to reboot the VM apparently.
Still not sure what the root cause of this is - but rebooting was, in this case, the remedy.
I am building a static app with PouchDB on Google AppEngine.
When I open the site in a browser window, it is showing a version I uploaded several hours ago.
If I open the site in an incognito window, the updated version is displayed (therefore I don't think it is actually an error in the console).
I put a new version number in app.yaml
I have migrated all traffic to the new version.
I have cleared my cache, deleted cookies, checked my application data, everything. I even reinstalled Chrome and Firefox.
I updated my Python version and my Google AppEngine Launcher yesterday; the problem pre-dated that update.
Also: just discovered that if I go to the URL of the updated version
http://4.[app-id].appspot.com, it displays the correct, updated version.
This is happening in Chrome, Firefox, and Edge.
Edit: probably should have mentioned that my site uses Service Workers and IndexedDB. I assume my service workers are caching the previous version, but I would have thought that Ctrl + F5 would clear the cache and show the new version.
I think it must be the Service Workers caching the pages (which is, after all, what they are supposed to do). This is actually really annoying when you are developing though.
A guy called Rich Harris has documented this behaviour and some workarounds on a Github Gist.
Reloading the page doesn't behave as you'd expect
If you make a change to your service worker, then reloading the page
won't kill the old one and activate the new one (it detects the change
by requesting the service worker file each time and comparing the old
and the new byte-for-byte), leaving you somewhat confused as to why
your changes haven't taken effect. This is because the old window is
never actually closed, meaning there's never a time to swap them out –
you need to kill the tab completely then reopen it.
Or you can have the browser do that for you by going to the
Application tab in devtools (in Canary, not stable Chrome yet), going
to the Service Workers section, and checking 'Update on reload'.
UPDATE (13 Nov 2017): This functionality is now available in Chrome, so you don't even need to download Canary.
And here's which bits of the application cache to clear:
Extremely often, in all kinds of various MVC3/4 apps I debug in VS2012 on my home machine, after pressing F5 to start debugging and open the configured start page in Chrome, it can take several - up to ten - minutes before becoming active.
I have no long startup procedures that load caches or generate code etc. and the same app will start instantly on my office machine. Quite often it will do so on my home machine as well, but this slow starting seems to come about after some hours of debugging, and possibly certain operations. Restarting VS doesn't seem to help, neither does killing IIS Express.
We were faced with an identical scenario recently where attaching the application to the debugger resulted in each page load taking about 10 minutes each, but running without debugging or in the QA environment worked fine.
The problem turned out to be that log4net was configured to use a network path for storing log files, a path that was unavailable from our local setup. This resulted in multiple attempts at accessing a remote path (once for each class being set up with Spring .Net) that didn't exist (and hence log4net threw an exception in each case).
But this should impact you out of the box, and shouldn't increase with time..
I've setup MAMP on OSX 10.6 and the exact same symfony code takes over 6 seconds to run on localhost and 200ms on my server. My web debug bar says the time hit comes from processing the action. I've tried it the production mode on localhost and the speed boost was minor, time went to 3 seconds instead of 6. Still ridiculously slow compared to my server.
The strange thing is that non symfony php code runs correctly and fast.
You can try Xdebug profiler to find out precisely which part of symfony is so slow.
YayMyLife.com is my first Rails site. I am using Apache/2.2.8 (Ubuntu) Phusion_Passenger/2.2.2 .
The site works fine on Linux/Mac/Phones. However, it does not load on any browser on XP. This behavior is also found on other XP machines. The browser seems to wait for more content and it times out. I have checked headers with Live HTTPHeaders (the headers look okey) and also flushed DNS cache on XP box.
Can you please help me fix the problem?
Are you sure it doesn't work? I just tried it using IE7 and Firefox 3 within one of my Windows XP virtual machines and the site loads fine. I get a JavaScript error in IE but not in Firefox.
I got browser shots for those who are interested in solving this case:
http://browsershots.org/http://www.yaymylife.com/
This gentleman was on #rubyonrails previously and asked the same question, with little feedback
What is the error that you are getting? If you look at all the browsers, they haven't finished loading ... could it be excessive load on the server?
Have you tried getting a Windows machine and trying to test it? If so, what is the error (with screenshot and/or stack trace from your log).
If it was a problem with rails, it would not load on any browser, if it was a css problem it would give you crap on the screen.
This looks to be an excessive load problem and something that you should try and address by looking at the web server end at the amount of time it takes to load the page and whether you need some sort of template caching or to improve the performance of DB queries that are running.
I started using Mongrel instead of Passenger and this problem is fixed. Thanks to everybody who took interest; esp. Omar Qureshi