I've been Googling around a bit, but I haven't found any references to what these warnings are:
2023-02-08 07:41:04.835 Electron[22682:539034] ASB: LNW <AtomApplication: 0x7ff416d1d5c0> (null) (null) (null)
2023-02-08 07:41:04.840 Electron[22682:539034] ASB: LNW <AtomApplication: 0x7ff416d1d5c0> (null) (null) (null)
2023-02-08 07:41:04.841 Electron[22682:539034] ASB: LNW <AtomApplication: 0x7ff416d1d5c0> (null) (null) (null)
2023-02-08 07:41:13.171 Electron[22682:539034] ASB: LNW <AtomApplication: 0x7ff416d1d5c0> (null) (null) (null)
Would someone explain please? I'm not sure how this relates to Atom.
Related
I got a high amount of crash reports for an app via XCode Organizer / Crashes tab
However the stack trace does not show any exception type, just point to a recursive method run in a background thread (via dispatch_async) (and no it's not infinite recursion, it's a search method with limited depth). I have no clue to figure out why this crash occurs. I try to reproduce the crash in real devices but cannot. Could this be an intensive cpu task and gets killed by the OS? How do I verify if that is the case? Any help would be appreciate!
#0 (null) in _TFC11MyAppFree17SearcherP33_D7BE9E167FAD2091BF2475359F0659466searchfS0_FTSi5aSi4bSi_Si ()
#1 (null) in _TFC11MyAppFree17SearcherP33_D7BE9E167FAD2091BF2475359F0659466searchfS0_FTSi5aSi4bSi_Si at Searcher.swift:115
#2 (null) in _TFC11MyAppFree17SearcherP33_D7BE9E167FAD2091BF2475359F0659466searchfS0_FTSi5aSi4bSi_Si at Searcher.swift:115
#3 (null) in _TFC11MyAppFree17SearcherP33_D7BE9E167FAD2091BF2475359F0659466searchfS0_FTSi5aSi4bSi_Si at Searcher.swift:115
#4 (null) in _TFC11MyAppFree17SearcherP33_D7BE9E167FAD2091BF2475359F0659466searchfS0_FTSi5aSi4bSi_Si at Searcher.swift:115
#5 (null) in _TFC11MyAppFree17SearcherP33_D7BE9E167FAD2091BF2475359F0659466searchfS0_FTSi5aSi4bSi_Si at Searcher.swift:115
#6 (null) in _TFC11MyAppFree17SearcherP33_D7BE9E167FAD2091BF2475359F0659466searchfS0_FTSi5aSi4bSi_Si at Searcher.swift:115
#7 (null) in _TFC11MyAppFree17SearcherP33_D7BE9E167FAD2091BF2475359F0659466searchfS0_FTSi5aSi4bSi_Si at Searcher.swift:115
#8 (null) in _TFC11MyAppFree17SearcherP33_D7BE9E167FAD2091BF2475359F0659466searchfS0_FTSi5aSi4bSi_Si at Searcher.swift:115
I am working with Card.io since long time but now it started to crash accidentally when i tap on camera button to scan card.
Below is the crash logs.
<Error>: *** Terminating app due to uncaught exception 'NSRangeException', reason: '-[NSTaggedPointerString getCharacters:range:]: Range {0, 7} out of bounds; string length 6'
*** First throw call stack:
(0x1845b5900 0x183c23f80 0x1845b5848 0x18459ce88 0x1844a7994 0x18459d634 0x100414aa8 0x1844eda04 0x1004147f4 0x1004153d4 0x10041557c 0x1003e8ea0 0x1892a80c0 0x1892a7cc4 0x189648930 0x189605930 0x189602340 0x189558b70 0x189566030 0x189299c24 0x18456c588 0x18456a32c 0x18456a75c 0x184499680 0x1859a8088 0x189310d90 0x10016de20 0x18403a8b8)
Feb 2 12:15:27 iPhone SpringBoard[54] <Warning>: HW kbd: Failed to set (null) as keyboard focus
Feb 2 12:15:27 iPhone SpringBoard[54] <Warning>: UNNotificationRegistrarConnectionListener connection invalidated
Feb 2 12:15:27 iPhone com.apple.xpc.launchd[1] (UIKitApplication:com.upperlife.instacare[0x4a0a][369]) <Notice>: Service exited due to signal: Abort trap: 6
Feb 2 12:15:27 iPhone SpringBoard[54] <Warning>: Application 'UIKitApplication:com.upperlife.instacare[0x4a0a]' crashed.
Feb 2 12:15:28 iPhone UserEventAgent[23] <Warning>: 215163172432: id=com.upperlife.instacare pid=369, state=0
As you are using old version of Card.io SDK for iOS, so that's the main reason why the crash for iOS 9 is occurring, it has been fixed in version 5.1.0 .
Issue already raised in github:-
https://github.com/card-io/card.io-iOS-SDK/issues/120
Resolved:-
https://github.com/card-io/card.io-iOS-source/commit/b9b3c0a329b75d048a20190f8843da4f247d755a
I was testing an App viewing the logs in Xcode > Window > Devices and I found this lines:
Apr 1 17:09:33 myIphone locationd[2763] <Error>: Fence: requestRegionState, com.myApp.demo/regionId, NOT FOUND
Apr 1 17:09:39 myIphone demo[3601] <Error>: CoreLocation: Fence: onClientEventRegionState, invalid state, 0
These logs don't appear in the console if I run the App from Xcode. Also, the App works fine, but it's disturbing.
Has anyone found similar logs? What's the meaning of these logs?
Thank you all.
I have seen this too in a Mac Catalyst app
2019-09-20 19:49:39.046086-0500 App[83029:4135201] [Generic_deprecated] Fence: CLClientRequestRegionState, unsupported fence type
2019-09-20 19:49:39.046548-0500 App[83029:4135201] [Generic_deprecated] Fence: CLClientRequestRegionState, unsupported fence type
2019-09-20 19:49:39.046922-0500 App[83029:4135201] [Generic_deprecated] Fence: CLClientRequestRegionState, unsupported fence type
I have a crash in my (deployed) iOS-App while starting. It looks like it happens in some lib-functions and I'm not sure how this could be. The console output says
Oct 15 17:05:42 iPadMiniR MyApp[260] <Warning>: INFO: downloading package data 5 of 5...
Oct 15 17:05:42 iPadMiniR ReportCrash[261] <Error>: task_set_exception_ports(B07, 400, D03, 0, 0) failed with error (4: (os/kern) invalid argument)
Oct 15 17:05:42 iPadMiniR ReportCrash[261] <Notice>: ReportCrash acting against PID 260
Oct 15 17:05:42 iPadMiniR diagnosticd[150] <Error>: error evaluating process info - pid: 260, punique: 260
Oct 15 17:05:42 iPadMiniR ReportCrash[261] <Notice>: Formulating crash report for process myApp[260]
so I analyzed the Crash Report:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000058
Triggered by Thread: 4
[...]
Thread 4 name: Dispatch queue: com.apple.root.default-qos
Thread 4 Crashed:
0 libobjc.A.dylib 0x00000001946d3bd0 objc_msgSend + 16
1 Foundation 0x0000000184ac884c -[NSSimpleRegularExpressionCheckingResult initWithRanges:count:regularExpression:] + 176
2 Foundation 0x0000000184aaf2a4 -[NSRegularExpression(NSMatching) enumerateMatchesInString:options:range:usingBlock:] + 1340
3 Foundation 0x0000000184ac8720 -[NSRegularExpression(NSMatching) matchesInString:options:range:] + 152
4 myApp [...]
I know what a Segfault is but I don't understand, why it can happen in a Library function. I already searched in Apple's developer documentation of NSRegularExpression (under enumerateMatchesInString:options:range:usingBlock: and matchesInString:options:range:) and googled for NSSimpleRegularExpressionCheckingResult, but I didn't find a thing that helps. In similar questions here on StackOverflow, the SIGSEGV occurs not in library functions but in the user's code.
My question is: How could a Segfault in this context occur? Doesn't the objective-C-Library-Functions check pointers? Or could it be that a pointer become dangled between the check and the usage (weak pointers, but I don't have any of them)?
I'm pretty new to iOS development, so thanks for any help :)
I use XCode 6.0.1 and iOS 8.0.2.
I have a app in which i play a splash video and have added some custom fonts.
The app works fine on ipad 3.2 but on 4.2 etc it crashes. The log says that i release something that i dint alloc. I have checked my code a hundred times and i dont do any such thing.
Either ways it works on the simulator and on the device(both 3.2)
any ideas?
EDIT:
<Error>: df(7903,0x3e3d7898) malloc: *** error for object 0x1a11b0: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
Wed Jan 19 20:35:38 unknown UIKitApplication:com..imagazine[0x9c7c][7903] <Notice>: def(7903,0x3e3d7898) malloc: *** error for object 0x1a11b0: pointer being freed was not allocated
Wed Jan 19 20:35:38 unknown UIKitApplication:com.imagazine[0x9c7c][7903] <Notice>: *** set a breakpoint in malloc_error_break to debug
Wed Jan 19 20:35:39 unknown ReportCrash[7905] <Notice>: Formulating crash report for process df[7903]
Wed Jan 19 20:35:39 unknown com.apple.launchd[1] <Warning>: (UIKitApplication:com.imagazine[0x9c7c]) Job appears to have crashed: Abort trap
Wed Jan 19 20:35:39 unknown SpringBoard[27] <Warning>: Application 'df' exited abnormally with signal 6: Abort trap
Wed Jan 19 20:35:39 unknown ReportCrash[7905] <Error>: Saved crashreport to /var/mobile/Library/Logs/CrashReporter/df_2011-01-19-203538_Sumas-iPad.plist using uid: 0 gid: 0, synthetic_euid: 501 egid: 0
SOLUTION:
First of all use the NSZombies and you will catch such errors.
The Problem: I had a timer setup for every 0.2sec and it was clearing a UIView and allocating it, not every 0.2secs but maybe once every 5secs.
I did a standard check:
if(vewCustom!= nil) {
[vewCustom removeFromSuperView];
[vewCustom release];
vewCustom = nil;
}
But the strange thing was i verified the code hundreds of times and I was not over releasing and either ways it worked on iOS4.2 for iPhone.
I removed the Timer but still it was crashing and then I removed the release and now it works fine.
Strange but it would be good if someone can explain what i was doing wrong.
You could try running the app in debug with zombies enabled. This way you'll get a stack trace on the overreleased object here's a link on how to set it up.
http://iosdevelopertips.com/debugging/tracking-down-exc_bad_access-errors-with-nszombieenabled.html
Assume that the log is true. The easiest way to find it is to enable Zombies and then exercise your application throughly. See here (tip #1):
http://loufranco.com/blog/files/debugging-memory-iphone.html
Another thing to do is a Build and Analyze and look at each thing it flags. In my experience there are very few false positives.
Just noticed this while looking for something else. The reason for the crash is that removeFromSuperview causes the superview to release the view. Thus, the release that follows is redundant (over-release). Won't be an issue with ARC, but could cause some confusion in other situations