I am using the Instruments through XCode 6.4 (iOS 8.3, Swift 1.2) profiling to find memory-leaks in my app. This is what I find:
When I click on any of this, and click on the stack-trace on the right hand pane, I see that its coming from the init() of some of my implemented UIViewControllers. Eg. MyViewController.init(). However, I have not implemented init for any view controller.
When I double click that line, it shows assembly-code as details.
Eg.
+0x27b callq "DYLD-STUB$$objc_msgSendSuper2"
All the tutorials about finding memory leaks through Xcode say that I would find the line of code in Xcode, but thats not happening. How do I find the cause so that I can fix these leaks?
Related
When I try to find usages (Alt F7 or Mouse-Click with CTRL-Button down on the method name at the declaration) of a Java method or field in Android Studio (Version 3.5.3) I am often receiving the message "No usages found in all places" although the method/field is definitely used - often even in the same class.
Is there some kind of index which needs to be updated?
Or any other idea, why obviously existing usages are sometimes not found.
Found it: There is a menu entry "File->Invalidate Caches/Restart ...".
After trying that, everything worked fine again.
Hope this helps others when running into the same problem.
BTW: Pretty dangerous if one relies on the wrong usage information and starts to delete unused methods...
I have updated my Android Studio to version 3.3.1, but now breakpoints are executing very slowly? First breakpoint take around 5 minutes to execute.
Can anyone please tell me what can I do to make it work like it was in the previous version?
I faced the same issue when I installed android studio 3.3.2. Any time I'd try to debug my app, it would run crazily slow. But finally got the solution as described below:
Go to the debugger and select view breakpoints
Make sure the Java method Breakpoint is unchecked.
It's often easy to add method breakpoints accidentally and That's usually the main reason behind the significant slowness of the debugging speed.
Follow the few steps below if that the case:
just remove all breakup points in your android studio.then automatically android debug will be fast.
remove all breakpoint step:
go to debugger then select red button it will pop up all debugger break point and then remove.
I have made a form (GUI) in Visual C++ & while debugging it step by step, I got the following error, which stopped further debugging of the code.
The screenshot of the error is shown below.
How to solve this?
Good chance further debugging is in fact not stopped - seems you tried to step into a system function (implemented in wuser32.dll), and you can't debug this without matching symbols. You can post a screenshot of the stack window at this point to help us verify.
First, try to just continue (F5 or Shift+F11 to step out).
If for some reason you must view at least function names at this location - check the 'microsoft symbol server' at the screen you show. and click load. After a brief download pause, you should be able to see at least a disassembly window, and hopefully a meaningful name for the current stack frame.
So I recently upgraded to QtCreator 2.3 (and want to keep it for its QtQuick support) and initially debugger performance slowed to an unusable crawl (though I could still see QString contents). Googling around led me to install gdb 7.3.1, the latest stable release at this time, and that happily brought debugger stepping speed back up to usable levels. But now the debugger won't display the contents of a QString, just the address of the char array, and a lot of private members that don't tell me anything informative. Anybody know how I can get the debugger to display string contents again? I'm on Ubuntu 10.04.
Check this
http://developer.qt.nokia.com/forums/viewthread/6323
Edit: The page isn't available anymore, the domain is currently parked.
#gshep Please replace the link if you can remember the title of the page and find another instance of it.
I have VS2010 Premium RTM version on Windows 7 Ultimate x64.
In the documentation they refer to the Memory 1-4 windows, supposedly under Debug->Windows->Memory.
I have "Enable address-level debugging" enabled in VS (Options->Debugging).
The problem is that I have no Memory menu item under Debug->Windows during debug of a c++ program.
Under Debug->Windows I have only:
Breakpoints
Parallel Tasks
Parallel Stacks
Watch ->
Locals
Call Stack
Threads
Have anyone else experienced this (and hopefully solved it)?
During the first run of VS after installation it asks you which "mode" it should run in, depending on your selection it shows or hides various menu items etc. Maybe you selected an option that hid those windows? This is described at this page.
I think you can use the information on this page to change those settings.
You might also be able to just run Devenv /ResetSettings to reset them, but not sure exactly what you'd end up with then...
Go to command Window and type in memory. It will show the Memory 1 watch window. I had to do that because I still can't find the debug command for it under customize even.
You can switch to expert mode by checking :
Tools > Settings > Expert Settings
Now you can show up Registers Window and much more other windows
The Memory window is available only if address-level debugging is enabled in the Options dialog box, Debugging node. The Memory window is not available for Script or SQL, which are languages that do not recognize the concept of memory.
or go here for other details:
http://msdn.microsoft.com/en-us/library/s3aw423e.aspx