I am manually testing the tags implemented using Dynamic tag manager.
I could see the Timing hit type which is not implemented by my developers.
For each page, i could see the time hit-type along with Pageview Hit type.
we are puzzled that i could see the unimplmented hit type only in my machine and that too in chrome browser only. But its not visible in anyone's machine.
Has anyone faced this issue? Let me know please!
If you cannot replicate the issue then it is environmental issue. i have faced the similar issue before
Because this is not an error, as i could see this unimplemented hit type only in my machine, i believe this is environment problem.
Un-installing and re-installing chrome has fixed the problem.
I am not able to find the timing hit type now.
Related
Have been experiencing a strange bug(?) with Chrome Dev Tools, where when I try to remove an item from Application > Local Storage tab, it no longer gives instant feedback (asin, the change is not reflected live). Likewise, when programmatically changes are made to Local Storage.
It requires me to close and reopen Dev Tools for me to see these changes reflected, which is highly inefficient for workflow.
I feel like this is likely not a bug, as I can't find it reported anywhere else online, perhaps a setting toggled by mistake unknown to me. Still, help much appreciated in reacquiring instant feedback. Thanks guys! Screen grab below:
EDIT: Just tried disabling all my extensions, and still the same problem.
This can be fixed with a reinstall of Chrome.
Since yesterday afternoon, I have not succeeded in using Folium to generate maps, even the most basic display function can not be completed, the network connection is normal, it is likely that there is a problem with the call of js.
I tried switching the network environment and trying to change computers, but it didn't work.
Failed to load resource: net::ERR_CERT_DATE_INVALID
leaflet.awesome-markers.js:17 Uncaught ReferenceError: L is not defined
at leaflet.awesome-markers.js:17
at leaflet.awesome-markers.js:122
leaflet.css:1 Failed to load resource: net::ERR_CERT_DATE_INVALID
map.html:39 Uncaught ReferenceError: L is not defined
at map.html:39
#This is the code for the most basic function I've tried.
import folium
m = folium.Map(location=[29.488869,106.571034],
zoom_start=16,
control_scale=True,
width='50%')
m.save('map.html')
I hope to generate map pages
I dont think there is any problem in your jupyter notebook/Python IDLE. Check with your browser. If you’ve determined that the ERR_CERT_DATE_INVALID is caused by an issue on your computer, try these steps to resolve it:
First things first, check the Date and Time set on your computer, if
these are wrong it probably explains how you got the
ERR_CERT_DATE_INVALID error.
Sometimes fixing this error is as simple as shutting down your
browser and then restarting it. Other times a system reboot may work.
However, there are a couple of instances where you’ll need to do a
little more work to set things straight.
Check your connection, if you’re connected to public WiFi or some
other public network there’s a chance that your browser is right and
you don’t actually have a secure connection. If that’s the case, stop
browsing and resume when you’re on a more secure setup.
Scan your computer with a trusted antivirus software, you may have
malware of some sort that is causing the issue. Unfortunately we
can’t provide you with info on how to fix every last piece of
malware, but if your antivirus can’t, someone on the internet
probably knows.
Disable any third-party plugins you have running on Chrome. Sometimes
these can cause unwanted problems.
Clear your browser cache on Chrome. Click the menu icon, open History
and select “clear browsing data.”
Delete and then re-install Chrome. Sometimes this helps.
There are a few other crazy fixes like bringing down your firewall or
modifying network settings. However I would not suggest this one since your PC then become susceptible to virus.
Hi I'm getting the error
Error creating WebGL context.
Uncaught TypeError: Cannot read property 'getExtension' of null
This is happening on google chrome 71 but I find it odd because if I open up dev tool and refresh the page it works perfectly fine I'm at a loss to what is causing this any idea's ?
It's worked perfectly fine untill today nothing has changed on the PC or browser. My drivers are all up to date, webgl is enabled...
if you have two GPU installed on your system you might want to try to enable
Override software rendering list
in chrome://flags/
I'll leave this here for anyone else apparently it's a browser and graphic card issue
mrdoob: The graphics card is only one of the reasons why the context
can't be created
https://github.com/mrdoob/three.js/issues/4927
This seems to be why unless anyone else has any other ideas...
The issue is on going and not fixed it would be interesting to know why this happens though and why opening dev tools and refreshing resolves the issue for me.
EDIT-
Apparently for me this was due to my graphic card being blacklisted because it's old.
The fix for me was manually enabling WebGL acceleration under Chrome’s feature flags: chrome://flags/
I have encountered this several times with THREE.js. It arises for me once memory resources are shared, abandoned, or overwhelmed, for example:
I have a good render loop but then I introduce long tasks.
I perform extensive, continuous testing. As I modify live settings in Chrome Inspector, THREE does not reflect all changes without fail. Memory may not be released until I restart.
I leave the program running overnight. The next morning the browser is froze, black, OOM...
I use multiple instances of a resource, for example
Web Audio and Magenta Music. The quality may perceptibly degrade and
throw its own errors, but... I will also encounter worse silent
errors. For example when I also steam music in another tab, or click
audio/video media on Twitter... frozen browser, black screen, WebGL
context loss.
I just wanted to comment that I saw this due to other unrelated errors in my app that got thrown first.
I updated my graphic drivers (NVIDIA) and didn't restart chrome nor the PC, and was having this issue.
I just restarted the PC and now it's fine.
This was resolved for me by simply installing the latest and restarting my browser - thought I'd add it here to hopefully save some future soul from wasting an hour like i did.
Error creating webGL Context in three.js.min ver 93
I had the same problem with Chrome version 104.5112.102 and managed to fix it by going to Chrome, Settings, and switching off the
Use hardware acceleration when available.
the graphics card is an old GE Force 8600 card running on Windows 10.
For me, I restarted my computer and the error did not appear again. You can try doing this before you do anything more complicated.
So i have the following problem.
Any time i click on a request to view the headers/payload/response
i receive a not responding window.
If i wait ~2 minutes it works.
So what i receive here is a developer tools not responsive status when working on local machine.
I tried to re-install chrome. Nothing changed.
Current Version is: Version 50.0.2661.102 m listed as up to date.
Is there any possibility to get some logs or did anyone faced the same problem?
I think it can be relevant if i show what extensions i have installed.
But i tried to enable/disable them and nothing changed.
And i get the same comportment in incognito mode too.
Later edit: I somehow identified the problem. Idea is that chrome is trying to display the cookie (request headers) which was 18k characters long and it looks like this is slowing a lot developer tools and sometimes make him crash.
I just saw that in Mozilla cookies are limited to a couple of characters (display perspective) and after that they show ...
I can't find any known issues regarding this crash, so here are a couple of steps you could take:
Use the Chrome Cleanup Tool and see if that helps.
Fully clean and re-install Chrome (including deleting user folders). If it works after that, you can slowly add extensions and plugins back and see if any reintroduce the problem.
I've searched the Internet like crazy, however "WTP freeze" or "Eclipse freeze" yields so many different results that it's virtually impossible to find the right one. I have the following issue.
In a HTML or CSS editor when I accidentally hover my mouse over an attribute value, Eclipse hangs for 3-4 seconds with CPU at 100% load before producing a tooltip message with some info on the tag and its attribute. I don't need those tips. Hell, I don't even need syntax coloring if that would prevent me from this hang.
I tried disabling all the autocomplete features, everything that seemed related, however that didn't change a bit. I looked for a setting to disable WTP completely without uninstalling it, however again - no luck.
I use Eclipse Helios. I have all the latest plugins. I'll supply any additional info, if that is needed.
Has anybody had a similar issue and was able to resolve it? This is really driving me crazy.
BOUNTY
The bounty will go to anyone who finds a way or a workaround that will make pop-up windows reasonably fast. I've had this issue in Eclipse in numerous places - like PyDev for example:
Eclipse PyDev completion hangs (yet again)
I have a strong programistic feeling that this is a general issue with pop ups and not so much with WTP/PyDev. Here are measures that I've already taken:
Installed the latest Eclipse from scratch
Installed the two problematic plugins on this clean installation (WTP/PyDev)
Made sure that Eclipse has more than enough memory
Made sure the appropriate JVM is chosen
My setup is Ubuntu Natty, Oracle Java 1.6 - latest version in the repos
Further findings
Ok, I've just found out that 99% of the time of the freeze is spent inside a call to org.eclipse.swt.internal.gtk.OS._gtk_widget_realize which doesn't seem right. Any clues?
I'd encourage everyone who has experienced this issue to vote for this bug on the Eclipse bug tracker.
You could try switching off all the Validators: Window > Preferences > Validation > Suspend all validators.
Another option is Window > Preferences > Java > Editor > Hovers, turn off 'Combined Hover'.
Wow, finally nailed it, thanks to one of the suggestions.
Hover messages can be disabled under Window > Preferences > General > Editors > Structured Text Editors > Hovers tab > Combined Hover.
Eclipse can be a labyrinth sometimes.
I had a similar issue where Eclipse would hang on tooltips for several seconds, and oftentimes crash. It got to the point where it would just plain crash even if I didn't do anyhting. Uninstalling it and reinstalling it got rid of the problem, though, so I suggest giving that a try if you haven't already.
How is your memory profile? Do you have more than enough?
We have run into many problems with Eclipse and wierd issues as we approached our memory limits. The current prevailing thought is that the swapping causes problems due to timing issues.
Eclipse sometimes downloads the the javadoc as requested, the hang your seeing may be the lag time it takes for that particular part of the javadoc to download.
The selected answer didn't work for me in Eclipse (Kepler) with PyDev.
For me the following worked best:
Show Docstrings should be disabled in preferences under Pydev/Editor/Hover.
This looks to be a gtk specific issue. In addition to the bug you mentioned there are other bugs opened as well e.g. https://bugs.eclipse.org/bugs/show_bug.cgi?id=345093.