11–20 of 22 posts
the thing that sucks about jetbrains is that you need to keep updating license keys on your own end every year, even though you're paying a yearly fee. they really need to make this much easier. the end user shouldn't have to do anything.
the thing that sucks about jetbrains is that you need to keep updating license keys on your own end every year, even though you're paying a yearly fee. they really need to make this much easier. the end user shouldn't have to do anything.
the thing that sucks about jetbrains is that you need to keep updating license keys on your own end every year, even though you're paying a yearly fee. they really need to make this much easier. the end user shouldn't have to do anything.
No? Just login to your JetBrains Account and it should just work in my experience? No need to fiddle around with license keys.
(Bug report mentions PHPstorm but it manifests on CLion, GoLand, and others.) This is clearly an Apple bug as well as possibly a bug in Jetbrains' UI or other native libraries or maybe upstream in the JVM. It's an Apple bug because it can bring down the whole system, sometimes with an absolute hardest possible crash that generates no debug logs! Sometimes it also just crashes the JVM. Sometimes it's a softer crash wi…
(Bug report mentions PHPstorm but it manifests on CLion, GoLand, and others.) This is clearly an Apple bug as well as possibly a bug in Jetbrains' UI or other native libraries or maybe upstream in the JVM. It's an Apple bug because it can bring down the whole system, sometimes with an absolute hardest possible crash that generates no debug logs! Sometimes it also just crashes the JVM. Sometimes it's a softer crash wi…
That's not true. It's pretty easy to crash Finder, and when Finder crashes, the whole system goes with it. For example, Time Machine has a tendency to crash my devices. It takes down finder, and from there, it's impossible to do anything.
Heavy resource usage isn't usually what causes these kinds of crashes on macOS, from what I've seen (unless there's an underlying hardware issue).
But yes, I'd agree this one is probably on Apple.
> Drawing attention on social media is the new way to get tech support focused on an issue -- "blue checkmark service" as it's called on Twitter.
You're right, sadly.
> Edit: I bet there is a security vulnerability here given that it brings down the whole OS. Any security researchers in the audience?
Possibly, but crashes are a dime a dozen. Actually getting something useful out of that information can be difficult. Hopefully this will be fixed long before anyone is able to get that far.
(Bug report mentions PHPstorm but it manifests on CLion, GoLand, and others.) This is clearly an Apple bug as well as possibly a bug in Jetbrains' UI or other native libraries or maybe upstream in the JVM. It's an Apple bug because it can bring down the whole system, sometimes with an absolute hardest possible crash that generates no debug logs! Sometimes it also just crashes the JVM. Sometimes it's a softer crash wi…
> Absolutely nothing else does this That's not true. It's pretty easy to crash Finder, and when Finder crashes, the whole system goes with it. For example, Time Machine has a tendency to crash my devices. It takes down finder, and from there, it's impossible to do anything. Heavy resource usage isn't usually what causes these kinds of crashes on macOS, from what I've seen (unless there's an underlying hardware issue)…
(Bug report mentions PHPstorm but it manifests on CLion, GoLand, and others.) This is clearly an Apple bug as well as possibly a bug in Jetbrains' UI or other native libraries or maybe upstream in the JVM. It's an Apple bug because it can bring down the whole system, sometimes with an absolute hardest possible crash that generates no debug logs! Sometimes it also just crashes the JVM. Sometimes it's a softer crash wi…
Earlier quoted context omitted.
Or possibly an Intel/hardware problem.
It'd be an extremely esoteric one if these products crash it and literally nothing else does including: - Hours of CPU and RAM burn - Multiple concurrent VMs running different OSes (Windows 10 and Linux). - "make -j8" on a large C++ code base - Visual Studio Code and other large Electron apps that also run under a JIT. - I ran a 3D graphics demo to stress test the GPU, no issues. Zero crashes of any kind, then I laun…
Look like it has something to do with the AMD dGPU and Catalina so again probably a GPU driver: https://mrmacintosh.com/10-15-4-update-wake-from-sleep-kerne...
Then you have another fun one probably related like it spinning up the fans and the GPU consuming double power when you run the built in display and an external monitor, but not with just external monitors: https://forums.macrumors.com/threads/16-is-hot-noisy-with-an...
Of course the problem with Apple is zero communication even acknowledging an issue leads to all sorts of wild goose chases usually involving reset pram or whatever.