I am using Chrome to debug an app. Usualy I get a complete stacktrace when profiling my app.
But recently the stack just disappeared. It only shows the layering, drawing and native events, but no longer the JavaScript executions.
In the settings I have uncheckt the "Disable JavaScript samples" and tested all other preferences regarding the performance tab. Nothing helped.
Other sites (like stackoverflow) won't work eighther. Chromium has the same problem.
I am running this on Ubuntu 18.04.4 LTS.
Anyone else has a clue how to fix this?
I'm affected by this as well. I filed an issue at https://bugs.chromium.org/p/chromium/issues/detail?id=1071961. Perhaps you could add more detail so the Chrome team can fix it faster.
Are you using an Intel CPU or an AMD one? I'm using one of the latest AMD Threadrippers. Wondering if that may be the cause.
Related
I got a bug report in my electron app. It looks like below~
We can't find a way to reproduce this.
I believe it's some kind of visual memory corruption, but I don't know how it happens...
It turns out to be a bug in Apple's latest 16' MacBook pro. Likely to happen when the system is recovered from sleep mode.
It's also happening in chrome/chromium.
Here is the issue track link:
https://bugs.chromium.org/p/chromium/issues/detail?id=1068170
I have an acer switch alpha, and both Ubuntu and Debian worked flawlessly with the stylus. But I cannot get it to work at all on Fedora which is my preferred OS.
What works:
Hovering
Clicking on anything related to the gnome-shell (settings, activity bar, title bar) But nothing inside windows aside from the settings application so far.
Very odd behavior, am I missing some libraries?
Honestly the amount of time I waste debugging Fedora over the last few years is a bit much. Never had as many problems on Ubuntu or Debian will probably just swap considering how utterly unreliable Fedora has become.
As of Fedora 25, the distro defaults to booting into a Wayland-powered desktop. Pens are not well supported under Wayland at the moment; only native GTK3 applications such as the shell and GNOME Control Center will react to pen input (many applications either still use GTK2 or another toolkit like Qt).
Until the situation improves, I would recommend using the "gear" icon on the login screen to change your session from "GNOME" to "GNOME on Xorg". The pen should return to functioning as it has in the past.
I am developing my first extension for Chrome and as I am working on Ubuntu, I've encountered two awful bugs.
The first thing is that chrome.i18n.getUILanguage is not supported! (console gives me an error about unsupported method). The thing is that this problem is not listed on any WIKI page, which may become tricky for beginners. Anyone had similar issue? For now, I am using window.navigator.language.
The second bug is about rich notifications that are not supported (anyone knows when it will be released?). As far as I know, when the app will be about to send a notification, the scripts will stop due to the error (similar to the first bug). I am not sure if there is possibility to develop different packages for different platforms, but if I want my extension to be truly multi-platform, I will have to give up development of this feature.
Any suggestions or thoughts?
Thanks,
As i said earlier in a comment, it seems to be not supported with linux mint either where i'm developing the chrome extension.
In this link a member of the chrome team said that they submitted it... but this is not true.
Thanks for the window.navigator.language alternative.
I've picked up the discover meteor ebook earlier today and have been following the steps. It's been a great experience and I hope I can contribute to this community once I have a more thorough understanding of the technology. All is going well and I was using firefox as my browser. I decided to install chrome since that is the browser I use on my host machine on a day to day basis. However when I load the project up in chrome its a blank screen. The console reports the following(pastebin)
http://pastebin.com/wvEaVNPv
Has anyone else experienced this issue?
YES! It comes and goes with time or development, and you will get different results in different browsers (ubuntu). I currently am getting
Uncaught ReferenceError: Package is not defined meteor.js:21
Uncaught ReferenceError: Package is not defined standard-app-packages.js:21
Uncaught ReferenceError: Package is not defined random.js:21
etc
A few weeks ago, chrome canary was bad but release chrome not. It may be some subtle code issue triggers things because as I developed madly but checked intermittently that problem came and went maybe three times, and once another browser gave me a clue on something it didn't like, which also cured chrome.
I don't have any tools/concepts to debug this further. I initially got through Discover Meteor using chrome about 2 months ago.
Check your accounts-ui-bootstrap-dropdown. If you are using bootstrap-3 you'll need accounts-ui-bootstrap-3. I found this as one possible cause when I went back.
I have a web server running Windows Server R2 Standard, and am experiencing the issue described in this blog post: http://www.hanselman.com/blog/BugAndFixASPNETFailsToDetectIE10CausingDoPostBackIsUndefinedJavaScriptErrorOrMaintainFF5ScrollbarPosition.aspx
In short, .Net is failing to recognise IE10 and is treating it as a downlevel browser without javascript support - if I understand the issue correctly.
I tried the following popular solutions:
Installed both hotfixes for .Net 2 and 4.
Manually updated the browser definition files in the .Net framework config folder and ran aspnet_regbrowsers.exe.
Put the new browser definition files in the App_Browsers directory.
Finally I upgraded to .Net 4.5 which solved the issue for .Net 4 sites running on the server, however .Net 2 sites are still experiencing the issue.
Because this is a live web server it has a lot of windows updates that have not been installed. I thought maybe there was an update that would address the issue. So I've taken a look at the updates but none of the descriptions seem to address the issue, so I cannot justify installing them and potentially causing more problems.
Does anyone have any other solutions or possible reasons why this issue just won't go away?
I have the same problem, and I haven't been able to figure out why none of the fixes work. However, I did find a workaround that might work for you: Setting the Page.ClientTarget attribute to "uplevel" overrides .NET's browser capability detection. Have a look at http://msdn.microsoft.com/en-us/library/system.web.ui.page.clienttarget.aspx for more information.
Have come through many microsoft hot fixes, they were working in local environment, but in the live server there was no result.
Setting up Page.ClientTarget = "uplevel" (preferably in a header or footer page) has really solved the issue. I think this the best solution, as your .net application may not detect any other browser in future. But then we may have to wait and see, if this fix has any side effects.