I am on Xcode 9.2, OSX, Objective-C.
Since OSX High Sierra Update, i get a lot of error messages logged like this:
AppleEvents: received mach msg which wasn't complex type as expected in getMemoryReference.
I have two XPC Services handling apple events for me, both of them report this.
Any clue what this is? I found a discussion in the Apple developer forums but they are not any further: https://forums.developer.apple.com/thread/88126
ANY help or pointer in the right direction appreciated.
Major approach on that issue (after there happened nothing for a long time): Apple responded in the forum above - it will be hopefully removed within a future update - I'll follow up on this.
A developer was worried about this message and so they opened a DTS tech support incident to verify whether it’s harmful or not. I discovered the underlying cause of this message and I’m satisfied that it’s just log spam, that is, it’s annoying because it fills up the log with junk but it has no other deleterious effects.
There’s a bug on file (r. 33758979) requesting that we remove this log spam.
[UPDATE]: Removed in Xcode 12
Related
I am an automation + manual tester. I would like to understand the reason how understanding the logs of an application(which i am working on) help me in improving my testing skills.
By viewing logs you will get some ideas about the error, if it is data level fix you can release and fix directly without dev team help.
In Java some times Runtime exception will occur, it will not convey messages to you in the interface about the exact problem. By viewing log you can get some ideas about the Runtime exception.
You see, I am really new into android, but the reason logs are important is because they can help you track down issues, such as Java.NullPointerExceptions and can help you trace back to where the issues were. I think there is also a way to create an error dialogue in the log, which can tell you that an error occurred. This is particularly essential in debugging, where you need to solve a problem in your app. I hope this helps, and best of luck. I think you can search up how to write stuff into a log at certain areas. I think the way on how to Log is to access Log class. http://developer.android.com/reference/android/util/Log.html
Is there a list of the breaking API changes in Thundebird 24? So it is possible to easier find incompatibilities in addons.
The difficulty is that error console does not show any error or warning, so it is quite hard to locate the bug caused by the change of API.
I had the same headache.
Error console)
The Error Console is deprecated in Firefox, and is now only made
available if you set the devtools.errorconsole.enabled preference to
true.
In TB: File->Preferences->Advanced->General->Config editor...
Changes for TB 24)
This is not so clear but i found only this list.
I hope these hits will help you and trust me, I really know how you feel. I also felt this frustration when I had to rewrite parts of my code 1 day before the planned release. :)
I know there is a way to get crashes and hangs for all applications. These files are placed in "/Users/user/Library/Logs/DiagnosticReports". So I could get version, time and name of the app.
But how to get daemon/process crashes and hangs? I need to know which exactly daemon was crashed/hanged and time when it happened.
Also is there is a way to get some system(OSX) crash with the same info?
Also would be great to get some resource failures/warnings: out of memory or out of disk space.
I need to get it programatically.
On Windows we can do this using NotifyChangeEventLog () API. All these info we can gather using such method. Also it notifies if something happened.
For the daemons crash/hang report see the "/Library/Logs/DiagnosticReports" directory. According to this document you can also find there kernel panic reports (i.e. system crash).
Don't know about NotifyChangeEventLog-like API, but in situations like "out of memory" there will be an exception, so you just need to catch it. See Error Handling Programming Guide for details. Also take a look at Exception Programming Topics
Edit: for the information about Crash Reporter take a look at Chapter 5 of Levin's book "Mac OS X and iOS Internals: To the Apple's Core"
in 10.9 the activity monitor offers you two tools when you have a hang but no crash hence no crash report:
spindump - memory dump like crash report and
sys digs which produces a bundle of files
I've got an app that gets information from a SOAP web service and I want to display the results in a UITableView.
I had a previous version of this app and I'm creating a new version to basically clean things up and get rid of a bunch of legacy code that's deprecated and no longer used.
In the previous version, this worked well. In the new version, not so much.
Basically, the current scenario is returning 3 strings that I'm trying to use as the basis for the data in my UITableView.
I'm struggling with this issue because it's so stinkin' hard to track down EXC_BAD_ACCESS errors!
(Parenthetically, if someone has a way to make the debug experience more like Visual Studio, I'd love to hear it! It's so frustrating to not have any idea which line caused the error, and also to not be able to look through my local variables at the time of the crash to see what's what. I've already added in the exception breakpoint, but that doesn't seem to do much.)
Anyway, the line that's causing the error APPEARS to be:
return [[self Libraries] count];
It occurs in tableView:numberOfRowsInSection:.
The error message I get APPEARS to reference a string that should be stored in the NSMutableArray [self Libraries].
What's going on here?
I'm using ARC, so shouldn't all of my memory management be correctly handled?
I don't have any manual release statements in my code ANYWHERE!
Please help me fix this!
Set NSZombieEnabled, MallocStackLogging, and guard malloc in the debugger. Then, when your App crashes, type this in the gdb console:
(gdb) info malloc-history 0x543216
Replace 0x543216 with the address of the object that caused the crash, and you will get a much more useful stack trace and it should help you pinpoint the exact line in your code that is causing the problem.
See this article for more detailed instructions.
ARC relies on the Apple standard/recommended naming practices. Check that you are not violating any of them.
Just for starters, if "Libraries" is an instance there are are naming issues.
OK, so I feel a little bit silly, but I've got two production machines. On one of them, I had installed a copy of Xcode 4.2 beta alongside the final, production copy. I forgot to uninstall the beta copy and was using it to run my code. As soon as I cleared that up and ran my code against the final, released Xcode 4.2, all works fine again.
As I mentioned to Jonathan Grynspan above, I DO understand Obj-C memory management. For some reason, I was getting a retain/release/release (performed by ARC), and that bug is remedied in the final version.
Thanks for the help in tracking this down! At least I got a definitive answer to WHY the problem existed!
I wrote an entire app, and I was just about to submit it to the app store, and in my final testing, I went back and added a few releases to ensure proper memory management was observed. And since then, I keep getting these random crashes. I've tried removing some or all of the release calls, I've tried retaining objects. I cleaned the project. I used NSZombieEnabled and that also is not helping. All this to not avail.
Most of the time, the console says provides no help. Usually the app loads, I put NSLogs in viewDidLoad, viewDidAppear, and viewWillAppear, and they all show up in the console, then it crashes.
Sometimes I also get EXC_BAD_ACCESS (and I know what that means). But its occurring randomly. So this doesn't make sense to me. Thanks for any help possible. I've written this whole app, and spent months on it. So I'm really stuck. Thank you.
Have you tried Build --> Analyze? It will search your code for leaks and other useful things you might have missed. Try that and see if it finds anything for you.
I agree with Rudy. It sounds like you're releasing something that is still in use. I would go back to the version that was working and start adding the releases one at a time til it causes the crash. Slow but effective debugging.
When you say that you "sometimes" get EXC_BAD_ACCESS, what do you get the rest of the time? Where does the crash stack indicate you're crashing? What messages do you get?
Random crashes usually indicate a timing problem. A common cause is accessing things on multiple threads. Are you? It can also mean timing differences based on network traffic.
Make sure the console doesn't indicate an exception rather than a memory violation. Usually there's something in the console that will be useful.