Ok so this is really been a headache for me. I have been trying to develop a react native app but the Debug JS feature on chrome makes it run very very slowly. Each button click and transition takes almost a couple of minutes and sometimes longer making debugging close to impossible.
I have removed many of the unused console.log statements to try and speed things up. I have also pulled the debugging tab into its own separate window. But there no real change in speed. I have also tried to connect the phone over wifi to debug it. I am running the code on the hardware device and have already tried the suggestions given in the following posts
https://github.com/facebook/react-native/issues/10559
https://github.com/facebook/react-native/issues/5632
What is the best approach to make the debugging faster and more tolerable?
Check the clocks on your phone and your computer.
In my case, the lagging occurs when the phone's clock is behind the computer's clock for more than a second. The issue resolved when I changed the phone's clock to a few seconds ahead of the computer.
My solution was to turn off the react "React Developer Tools" extension for Chrome. Really made a big difference. Note: I use the "React Native Debugger".
Have you tried to deactivate the "Slow animation" option in the debug menu of the simulator?
I had the same issue and that did the trick when running my app in the ios simulator.
Try to disable "Dev Settings" -> "JS Dev Mode" -> Reload.
Hope it helps.
Unchecking Slow Animations in Debug option of Simulator does the trick! Very simple.
try to comment all console.log things on your project, then check the running speed. the remote debugging is load on your browser (chrome v8) and because of that the app loading is not gonna be to slow.
Using the debugger in Opera helped me quite a bit with performance in Debug mode. I also noticed that profiling temporarily fixes the performance in Chrome's devtools.
In React Native Debugger, right click -> just select 'Toggle React DevTools' and close react dev tools window
In my case, the lagging occurs when the phone's time is behind the
computer's time. when I
changed the phone's clock to a few seconds pr few minutes ahead of the computer.
It's really working super fast now.
Remove bundle location
Install the app again.
npx react-native run-android
or
yarn react-native start andoird
Open React native debugger
Open the dev Menu and select debugging
Related
All the functions starting with ui (uigetfile, uigetdir, etc...) fail to work (and return 0). They do not even pop up a Window to select files.
This happened on OSX Monterey 12.3 with MATLAB 2019b, 2020b, 2021b, 2022b.
I realized that when the MATLAB process hangs after a ui command, a new process is created for analytics and improvement. And this process apparently crashed. I tried to kill it but it did not help. I tried to disable in the preferences > Security > Privacy tab but was not able to (the GUI was not populating).
Eventually I rebooted and was able to disable Analytics and Improvements. After that MATLAB behaved fine.
Sorry you had experienced a problem.
The UI functions in MATLAB display native macOS open/save panels - native open/save panels run out-of-process and are controlled by various system services.
Therefore, if either the QuickLook or openAndSavePanel service crashed before the panel could start (or finish) displaying, instead of a crash, you may see nothing happening. It sounds like this is probably what happened.
If that's the case, this issue has nothing to do with analytics, as macOS analytics only come into play once something crashed. Rebooting the machine is likely the thing that made the issue go away, not the disabling of analytics.
To find the root cause of the issue, the best bet is to contact MathWorks tech support and provide diagnostics, such as unified system logs, spindumps, spotlight diagnostics, quicklook database cache, native crash reports, etc.
I hope this was helpful.
I have been developing this app for quite a long time, and have had little or no issues. But when I decided to test it without the debugger attached, it caused problems with the fast app switcher. Whenever I switch the app with fast app switcher (or by pressing Start button), it causes the app to crash.
I am using VS2015 and tried enabling break for all exceptions, but still nothing happens while debugging, so I can't understand what the actual problem is.
Any ideas how can I solve this??
P.S. There seem to be a solution for this in this thread: Fast App Resume crashing on WP8.1 when not attached to debugger, but it is intended for Windows Phone 8 and doesn't match with the 8.1 api. Any similar solutions for WP8.1??
have you tried to implement the NavigationHelpers in your app ?
http://mtaulty.com/CommunityServer/blogs/mike_taultys_blog/archive/2014/05/23/windows-phone-8-1-frame-page-navigationhelper-suspensionmanager.aspx
I think that may help you :)
When I debug a Cordova app what I constantly do is step through its code inside Chrome's WebInspector. In order to be able to do this, however, I have to wait for the device to become ready in chrome://inspect/#devices (only then can I click on the appearing link for the started app). But if I do this the inspector will not halt on breakpoints if I am not quick enough. How do experienced Cordova developer tackle this issue?
Additionally to frank's comment I just found GapDebug which offers instant debug and, thus, comes close to what I deserve.
I'm using xamarin studio and monotouch for developing iphone applications. When I set break points on my code and start debugging with the xamarin studio, the debugger breaks the codes on the break point correctly, but the problem is that when I trace the codes with debugger after some seconds ( maybe 30-40 sec) the debugger stops debugging, just like a crash. What should I do?
EDIT
I noticed that it is not because of the break point. Whenever I do not work with the phone after a few seconds the debugger disconnect and stop debugging. Is this really a bug? I think maybe there is a setting that if I change it then the issue will be fix.
Isn't this done by the iOS operating system??? doesn't it only give you ~30 seconds to return from the first event otherwise it kills the application process ? So if you sit in the debugger then it will kill that too?
If it's a bug, verify if there is a newer release and update you copy.
Otherwise, report it to the software providers for a solution.
I have this issue when debugging mobile apps on the emulator. When I press F5, the build starts, then the deploy, then the app pops up in the emulator.
Because this takes a minute or 2, I am checking my SO score and maybe ask a question while I wait, and the emulator is in the background. When I finally switch back to the emulator, it shows the start page, not my app.
I figured out that by pressing the back button I can bring the debugged application to the foreground, but still, I don't know what is pushing it into the background to begin with. Has anybody noticed this, and found a way to prevent it?
The default behavior in WinMo is that if the device has no activity for a certain period of time (set in Settings->Today->Items->Today Timeout), the Today screen will come to the fore. Check to see if that's what's happening (though I think the smallest interval is still larger than a couple minutes).