Out of the Blue

I doubt anyone can help me with this, but it's worth a shot. My Discord client crashes a lot. And by a lot, I mean constantly. Dozens of times a day, and sometimes five times in 30 seconds. My repeated troubleshooting efforts have gotten me nowhere. Following tips online I've deleted the app and manually removed its data a dozen times or more, turned off hardware acceleration, and run it as administrator. But it still just quits repeatedly. It does not give an error message and leaves no trace in the Event Viewer. Lots of users seem to have to deal with one-off issues, but I can't seem to find references to anyone else having a chronic problem like this. As I say, I'm not sure what I'm hoping for, but if anyone has a suggestion on how to troubleshoot an app misbehaving this badly, I'd sure appreciate hearing it.

Obituary: Joe Flaherty, 'SCTV' and 'Freaks and Geeks' Star, Dies at 82.

Discordant Round-up
Thanks Ant and Neutronbeam.

Science
Thanks Max.

Media

Creature Features

Follow-up

The Funnies

View : : :
10.
 
Re: OotB: Discordant
Apr 2, 2024, 13:47
10.
Re: OotB: Discordant Apr 2, 2024, 13:47
Apr 2, 2024, 13:47
 
TFabris wrote on Apr 2, 2024, 13:24:
Weird idea, but, do you have any automation tools running which are designed to send or modify keystrokes or other commands to applications? Maybe discord isn't crashing, but rather, being closed down by some other process. You said that no error messages are appearing and there's nothing in the event viewer to indicate a crash. For example, on my systems, I would often have event-driven or timed scripts which would deliberately stop certain processes that I didn't want running because they interfered with other things. Maybe something like that is being overzealous. Maybe something as simple as an antivirus program detecting malicious activity, either as a false alarm or valid detection.

As mentioned elsewhere in the comments already: Windows has some developer-level features which are intended to trap crashes of applications, and write a crash/debug dump file. These fall under the general heading of "post-mortem debugging". If Discord is genuinely crashing, you should be able to configure Windows to trap that and then open the dump file in a debugger. The debugger can be daunting, but you don't need to actually diagnose the bug, just find enough info to point you in the right direction.
Years ago a Microsoft Windows Software Engineer wrote an article about troubleshooting his mother’s computer while he was visiting her over a long weekend. Now normally he would have just saved her data and reinstalled the OS, but his high school friends were razzing him about being a hoity toity “software engineer” and teased him about fixing it the easy way. So he thought he’d show them, after all he did have the know how, access to the latest tools and extensive on the job experience.
He spent most of the three day weekend going through all the logs and debugging files just to find the issues,
that could have been rectified in an afternoon by a format and reinstall.
“We’ve arranged a society on science and technology in which nobody understands anything about science and technology, and this combustible mixture of ignorance and power sooner or later is going to blow up in our faces." Carl Sagan
Avatar 58135
Date
Subject
Author
1.
Apr 2, 12:32Apr 2 12:32
2.
Apr 2, 12:40Apr 2 12:40
3.
Apr 2, 12:44Apr 2 12:44
6.
Apr 2, 12:50Apr 2 12:50
8.
Apr 2, 13:04Apr 2 13:04
17.
Apr 2, 15:02Apr 2 15:02
4.
Apr 2, 12:47Apr 2 12:47
5.
Apr 2, 12:47Apr 2 12:47
7.
Apr 2, 12:56Apr 2 12:56
11.
Apr 2, 14:02Apr 2 14:02
9.
Apr 2, 13:24Apr 2 13:24
 10.
Apr 2, 13:47Apr 2 13:47
 Re: OotB: Discordant
12.
Apr 2, 14:14Apr 2 14:14
13.
Apr 2, 14:29Apr 2 14:29
19.
Apr 2, 15:16Apr 2 15:16
22.
Apr 2, 17:01Apr 2 17:01
14.
Apr 2, 14:30Apr 2 14:30
15.
Apr 2, 14:36Apr 2 14:36
16.
Apr 2, 15:01Apr 2 15:01
18.
Apr 2, 15:05Apr 2 15:05
20.
Apr 2, 16:15Apr 2 16:15
21.
Apr 2, 16:38Apr 2 16:38
23.
Apr 2, 17:43Apr 2 17:43
24.
Apr 2, 18:24Apr 2 18:24
25.
Apr 2, 19:30Apr 2 19:30
28.
Apr 2, 21:12Apr 2 21:12
26.
Apr 2, 19:33Apr 2 19:33
27.
Apr 2, 20:19Apr 2 20:19
29.
Apr 2, 22:39Apr 2 22:39
30.
Apr 2, 23:11Apr 2 23:11
31.
Apr 2, 23:20Apr 2 23:20
32.
Apr 2, 23:25Apr 2 23:25
33.
Apr 2, 23:30Apr 2 23:30
34.
Apr 2, 23:57Apr 2 23:57
35.
Apr 3, 01:17Apr 3 01:17
36.
Apr 3, 03:38Apr 3 03:38
37.
Apr 3, 03:48Apr 3 03:48
38.
Apr 3, 10:22Apr 3 10:22
39.
Apr 3, 11:43Apr 3 11:43
40.
Apr 3, 13:13Apr 3 13:13