Search results for

LLDB crash

30,300 results found

Post

Replies

Boosts

Views

Activity

Reply to why mapkit js does not have LookAroundSceneRequest
Ed Ford,  DTS Engineer Your reply does not help. I have look at the sample code thousands times before I ask this question here. The sample code, and document api does not mention how to update coordinate for the look around object. I need constantly change the look around scene coordinate, the sample code only create look around object based on one coordinate. If I need to update coordinate to a different location for this look around object, can you share the sample code to do this job here for everyone that is interested? This is my code, it destroy everytime before create a new one. It works, but it can crash browser webGL if user change coordinate 16 times and above , then it cause apple base map blank. ` // // --- --- apple look around --- // var lookAround var is_lookAround_load_complete = false var is_first_time_lookAround = true // only for 1st time load function create_apple_look_around(lookAround_lat, lookAround_lng){ /* no way to update coordinate of existing look around object, have to
Topic: App & System Services SubTopic: Maps & Location Tags:
3w
Reply to iOS 26 WKWebView STScreenTimeConfigurationObserver KVO Crash
What is happening This crash is happening because the update queue utilized for STScreenTimeConfigurationObserver in WebKit is concurrent instead of serial. See the highlighted line introduced in WebKit. How to fix (suggestions) a) The quick path is for WebKit to utilize the main queue or a private serial one instead of a global concurrent. b) Additionally the ScreenTime framework should either not allow concurrent queues to be utilized in STScreenTimeConfiugurationObserver.init(updateQueue:) or support concurrent queues. Why is this happening TL;DR [STScreenTimeConfigurationObserver setConfiguration:] is getting called multiple times at once and the KVO code is not thread safe. The Details The Automatic KVO implementation for STScreenTimeConfigurationObserver is not thread safe. While STScreenTimeConfiguration is. This issue can be reproduced by concurrently setting the private method [STScreenTimeConfigurationObserver setConfiguration: configuration] to a new configuration. In the implementation of
Topic: UI Frameworks SubTopic: UIKit Tags:
3w
Reply to SpriteKit scene used as SCNView.overlaySKScene crashes due to SKShapeNode
Ok, so just to make things clear, is it expected that whenever I want to change the SpriteKit scene and also avoid concurrently accessing objects that may be changed in the current thread, I have to queue the SpriteKit changes by capturing all the needed state? It's just surprising to me that this is needed when SpriteKit is used as an overlay in SceneKit, but when running SpriteKit alone, it doesn't seem to be needed. I filed at least one feedback recently about crashes happening only when SpriteKit is used as SCNView.overlaySKScene. Is it expected that one has to use this... boilerplate code when embedded in SceneKit? Couldn't one do without it by simply overlaying a SkView on top of SCNView? class SceneController { private var shapeNode: SKShapeNode! func main() { let shapePath = CGPath(rect: CGRect(x: 0, y: 0, width: 10, height: 10), transform: nil) GameViewController.shared.updateSpriteKit { [shapeNode, shapePath] in shapeNode!.path = shapePath shapeNode!.fillColor = .systemRed } } } class GameV
Topic: Graphics & Games SubTopic: SpriteKit Tags:
3w
Reply to Hardware Memory Tag (MIE) enforcement outside of debugger
I sat down tonight and ran through this. Thanks for the super clear instructions! Good news: it works, and also works in my original app. Once I knew exactly what the MTE simulated crash report looked like I found two examples lurking among the dozens of crash reports from when I was testing a couple of weeks ago. This doesn't entirely make sense. I would have expected to see heaps more of them, and it's strange that real memory corruption crash reports vastly outnumber the MTE simulated ones. I like to think there was more to this than PEBKAC but at this point who could say? 😁 Thanks again!
Topic: Privacy & Security SubTopic: General Tags:
3w
Having trouble catching a 'redirect' with URLSessionDownloadDelegate
I've implemented func urlSession(_ session: URLSession, task: URLSessionTask, willPerformHTTPRedirection response: HTTPURLResponse, newRequest request: URLRequest, completionHandler: @escaping (URLRequest?) -> Void) and func urlSession(_ session: URLSession, downloadTask: URLSessionDownloadTask, didWriteData bytesWritten: Int64, totalBytesWritten: Int64, totalBytesExpectedToWrite: Int64) I've put a breakpoint in each but the BP in willPerformHTTPRedirection never fires. When the didWriteData fires and I inspect downloadTask.originalRequest I see my original request URL When I inspect downloadTask.currentRequest the returned request contains a different URL. I'm the farthest thing from an HTTP wizard, but I had thought when originalRequest differs from currentRequest there had been some sort of server-side 'redirection'. Is there a way for my code to receive a callback when something like this happens? NOTE: my download code works fine, I'm just hoping to detect the case when currentRequest changes. any/all
Topic: App & System Services SubTopic: Networking Tags:
1
0
112
3w
Reply to SpriteKit scene used as SCNView.overlaySKScene crashes due to SKShapeNode
Yes, the crash report you posted shows only one thread accessing SpriteKit. However crash reports don't perfectly capture the state of every other thread at the instant of the crash because control needs to first return to the kernel - via sys call, pre-emption, etc - before thread state can be recorded for the crash report, by which point the other thread may have finished interacting with SpriteKit. My suggestion is to look through other crash reports for the same crash point. In my experience given a sufficiently large enough number of crash reports, one of them will end up capturing the other thread in the act of concurrently mutating whatever data - SpriteKit internals in this case - caused the crashing thread to crash. -- Justin
Topic: Graphics & Games SubTopic: SpriteKit Tags:
3w
Reply to SpriteKit scene used as SCNView.overlaySKScene crashes due to SKShapeNode
Hello The crash you posted is in SpriteKit code, not SceneKit code. However, I'm not certain this is a SpriteKit bug. A common cause of SpriteKit crashes is accessing/modifying SpriteKit objects outside of SpriteKit's update loop. Even calling methods or accessing properties that look like they don't modify anything (e.g, -frame) can trigger mutation to SpriteKit's internal data structures, which is unsafe if done from multiple threads. Indeed, while looking through past SpriteKit bugs I found one for the exact function shown in your crash report. The resolution of that bug was in the app, which was found to be updating SpriteKit objects from multiple threads. I suggest looking through each of the crash reports in the Xcode organizer. Look for reports where multiple thread backtraces contain SpriteKit methods/functions. That should point to locations your code is accessing/modifying SpriteKit objects where it should not be. -- Justin
Topic: Graphics & Games SubTopic: SpriteKit Tags:
3w
SpriteKit scene used as SCNView.overlaySKScene crashes due to SKShapeNode
I recently published my first game on the App Store. It uses SceneKit with a SpriteKit overlay. All crashes Xcode downloaded for it so far are related to some SpriteKit/SceneKit internals. The most common crash is caused by SKCShapeNode::_NEW_copyRenderPathData. What could cause such a crash? crash.crash While developing this game (and the BoardGameKit framework that appears in the crash log) over the years I experienced many crashes presumably caused by the SpriteKit overlay (I opened a post SceneKit app randomly crashes with EXC_BAD_ACCESS in jet_context::set_fragment_texture about such a crash in September 2024), and other people on the internet also mention that they experience crashes when using SpriteKit as a SceneKit overlay. Should I use a separate SKView and lay it on top of SCNView rather than setting SCNView.overlaySKScene? That seemed to solve the crashes for a guy on stackoverflow, but is it also encouraged by Apple?
Topic: Graphics & Games SubTopic: SpriteKit Tags:
4
0
656
3w
Reply to Horrible weird Window Server killing bug
Urgh, I think it's a divide by zero bug. So this can apparently crash the Window server: Path { path in path.move(to: pt(qdt.qx * -20, 0)) // DIV BY ZERO path.addLine(to: pt(qdt.qx * -20, qdt.qy * (sH)/cos(angle.radians))) } If cos(angle.radians) is 0, you get a simple but unrecoverable divide by zero error, and hey, that's on me. But I would expect the system to kick my program with a nice EDIVBYZERO, not take out the window server. My solution to this is this function, which works because I don't need perfect accuracy: func cosNZ(_ input: Double) -> Double { let x = cos(input) if x == 0.0 { return Double.leastNonzeroMagnitude } return x }
Topic: UI Frameworks SubTopic: SwiftUI
3w
Reply to Invalid parameter not satisfying: parentEnvironment != nil
Thanks for the crash report. I was able to uncover an internal bug that AFAICT is tracking the same issue (r. 154431813) [1]. Sadly, that remains unfixed and doesn’t offer any ideas as to how you might avoid it. My advice is that you file your own bug about this, attaching all the information you have available. Please post your bug number, just for the record. Also, you mentioned that you’re in touch with some users that can reproduce this. If so, could you ask them to file their own report about it in Feedback Assistant. That should capture a sysdiagnose log, which might help with the investigation. If that happens, ask them to send you their bug number and then post those here as well. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Much to my own surprise. Radar is a very big haystack (-:
Topic: UI Frameworks SubTopic: UIKit Tags:
3w
Xcode Metal Trace
Code is download from apple official metal4 sample [https://developer.apple.com/documentation/metal/drawing-a-triangle-with-metal-4?language=objc] enable metal gpu trace in macOS schema and trace a frame in Xcode. Xcode may show segment fault on App from some 'GTTrace' function when click trace button. When replay a .gputrace file, Xcode may crash , throw an internal error or a XPC error. The example code using old metal-renderer can trace without any problem and everything works fine. Test Environment: Xcode Version 26.2 (17C52) macOS 26.2 (25C56) M1 Pro 16GB A2442
Topic: Graphics & Games SubTopic: Metal Tags:
2
0
462
3w