I am using Chrome Developer Tools under Windows 7 to record runtime performance (Chrome 67.0.3396.62 (64-bit)). I am able to click DevTools' Record button to start capturing performance metrics, but when I click its Stop button, the following Loading profile... prompt appears and never changes:
I tried exiting and reloading Chrome, but this problem persists across restarts. How do I resolve this problem?
It turns out that just exiting and reloading Chrome may not stop all of Chrome's background processes. For example, here is a screenshot of Windows Process Explorer showing multiple instances of chrome.exe still present after I exited Chrome:
Once I manually killed each of these processes (by clicking on the process and then pressing my Delete key), Chrome Developer Tools' record runtime performance capability was restored.
Related
If I run flutter --profile, then I can profile my app in android studio. But when I start with flutter --release command, Android Studio does not show me a device for profiling. Andoird studio then tells me "No debuggable processes".
Can I force Android studio to also profile my app in release mode? (I'm only interested in CPU and memory usage).
The purpose of profile mode is to let you check on those things specifically. (CPU and memory usage as well as other things). if you check the flutter docs they say:
profile mode is similar to release mode, with the following differences:
Some service extensions, such as the one that enables the performance overlay, are enabled.
Tracing is enabled, and tools supporting source-level debugging (such as DevTools) can connect to the process.
In other words profile is running as close to release as possible while still giving you the ability to check performance metrics/ find out what is causing performance issues.
If you really need the exact cpu and memory then you can run the app in release mode through xcode. Here are the steps to do that:
open Runner.xcworkspace
In the top bar, click Runner > edit scheme. This should open up a new window
In the new window, click Run > info > Build Configuration > Release
Close the window and run the app on your device by clicking the Play button
You can see the CPU and Memory in the left side bar under the Debug tab (It looks like an aerosol can to me)
Every time I refresh the page Google Chrome Dev Tools switches to Sources tab which is getting very annoying. There is no breakpoint and there is no error so showing me random source files is pretty useless and damn irritating. It does not always do this for all web sites. If I have Console tab selected, how can I force it to stay on Console when refreshing? (67.0.3396.99 (Official Build) (64-bit))
Well a windows 10 update broke sleep, the computer went to sleep with the emulator open and now that's broken. When I run an app to launch in the emulator it will boot the emulator but won't install just time out. When I try and run an app into a running emulator instance Studio says:
com.android.ddmlib.AdbCommandRejectedException: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Error while Installing APK
I've followed some of the other threads here. I've tried changing
the environmental variable in control panel, but in fact I think it
pointed to the right place originally, where the sdks are these
days.
I've tried restarting the PC. I did try deleting a couple of
adb files, that didn't work.
I've tried deleting all the sdks and
downloading them again.
I've tried uninstalling and updating Android
Studio, several times. Now on AS 3.1, still not working.
Bit of a nightmare really.
How do I set the vendor keys? Using AS console commands? Can anyone point me to a dummies guide, this is a bit of a tangent for me, wish I could fix it from the GUI.
The working fix for this particular issue is to enable Developer options on your emulator and enable "USB Debugging".
OK so eventually downloading a nexus 4 x86 image android 27, with no play store worked. Sorry if this is repetition. Long live working emulators
Combining answers from here and there gives an answer that also worked for me in IntelliJ IDEA. I assume the issue is the same, since the emulator and AVD is the same.
Option 1:
Restart the emulator from AVD
Option 2:
Wipe the emulator data
Option 3: Stop the emulator. Then make sure it is up to date and try again.
If it still does not work, restart the adb server and retry.
adb kill-server && adb start-server
If it still does not work, perhaps your adb is out of date... somehow. This was the case for me. Running the following fixed that for me.
adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
emulator-5554 device
If it is now working for some emulators but not newly created ones, take note of the message in the emulator selection box: "Press Ok in the Allow USB Debugging Dialog"
Sadly, there is no such dialog. So go and enable Developer Mode in the settings of your emulated OS by tapping the Build Number several times. Then go to the Developer Settings and enable USB debugging.
After recent upgrades of emulator, the virtual device*) stays unauthorized. When I cold boot the emulator, sometimes I see the expected confirmation dialog, but this dialog goes away immediately, leaving no chance to click 'OK'.
We're aware of this problem and plan to fix it soon.
* Here, I was running x86 with API 28 and Google Play on Windows 10. I don't know which other scenarios are effected.
For anyone who might encounter this in the future -- I mean the ultimate issue of receiving the error, "This adb server's $ADB_VENDOR_KEYS is not set" despite not having any (or any sufficient) opportunity to click OK...
Resolution: In the Developer Settings, select the option to, "Remove existing authorized adb keys on device." Repeat the previous action -- the prompt will once again appear, as if the very first time.
-Mike
Go to developer options in your device and click on 'Revoke USB debugging authorizations'. Disconnect and reconnect your device. You'll get a prompt on your device to authorize your computer to connect to your device. click on 'OK' and your set.
Basically, the authorization key has gone out of date or it's no longer present. So, we just have to set a new autorization key and revoke the old ones.
I want to package and launch my BlackBerry Hello World application for WebWorks. For developement, I am using the Ripple emulator. The Ripple simulator says:
The build and deploy services are not currently running, would you like to start them?
After pressing the button Start Services nothing happens and no errors are in the error console.and i also did below steps as i have searched and get this result:
There are two reasons this might be happening. The first is that Chrome is preventing this from happening.
Open the Tools --> Extensions screen in Chrome
Enable 'Developer Mode' checkbox if it isn't already
Are you running Chrome in Incognito mode? If so enable the 'Allow in Incognito' checkbox
The other options is that nodejs is being blocked. If you're on windows, I'd suggest making sure that all user permissisons are enabled to allow you to run Chrome in a way that it can launch external processes.
And After doing all when ever i refresh page it says
The build and deploy services are currently running at localhost:9910. and after loading that page this message not visible but
The build and deploy services are not currently running, would you like to start them? message still there! please explain what's wrong here?
Thanks
This issue is solved by removing Ripple extension version 0.9.15 and installing version 0.9.16 (latest as of this posting), and restarting Chrome. When you click the 'Start Services' button, the console should appear displaying a build service start up message.
http://developer.blackberry.com/bbos/html5/download/
Install the latest beta and it should work!
I'm working on an app and I've been able to successfully debug it using the device. I have a crudely working version of the app and I wanted to test it out on the phone, show it to friends and get opinions. The problem is, after doing adb install I now have the icon on my phone but when I try to launch it, it gives me the "Waiting For Debugger the process is waiting for the debugger to attach" message. I have removed the 'debug=true' flag in the application manifest and also turned off usb debugging on the phone. Why is the application thinking I'm still debugging it? What do I need to do to be able to run it without having debugger on eclipse attached?
First, Set debug="false" in manifest.xml, and uninstall application from your device and reinstall it. It will work
just restart the device, not power off, choose restart
If all the above doesn't work, start the application in debug mode.
1) In eclipse -> go to the debug perspective
2) When the app is running -> press the "Disconnect" button (next to the "stop")
3) Turn off your phone.
4) Remove the battery for 30 sec
All should be back normal