![]() This is strange because if I don’t use File > Exit and just kill the process taking up more RAM then Discord does close (both processes die). Then I kill the process taking up less RAM (when killing in Terminal sometimes I have to do this twice for the process to die!) and Discord closes. If I kill the process taking up more RAM, the window that wasn’t blank goes blank (File > Exit in either window still does nothing). If I kill the process taking up less RAM (via System Monitor, for example), the program ends. At this point, using File > Exit in either window doesn’t kill any processes. If I go File > Exit, it seems to kill the process that’s taking up the most RAM but leaves the other one alive - this results in Discord reloading (a new process with a new PID (called Discord) that takes up significant RAM is created) and also having a separate blank window. The PIDs I’m killing are for two Discord processes. reloadingįeature redeclared is this a duplicate flag? voice_sound_stop_loopįeature redeclared is this a duplicate flag? voice_relative_soundsįeature redeclared is this a duplicate flag? voice_panningįeature redeclared is this a duplicate flag? voice_multiple_connectionsįeature redeclared is this a duplicate flag? media_devicesįeature redeclared is this a duplicate flag? media_video I also get this in Terminal when I try to close Discord (strange, the other time I tested this the Terminal exited back to where I could type in it (leaving Discord running) rather than leaving me in the program’s Terminal output): Failed to generate minidump. * adjust program to not access do we adjust Discord to do that? Log: apparmor="DENIED" operation="open" profile="" name="/proc/3818/cmdline" pid=6220 comm="Discord" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Seems the repeated lines are: apparmor="DENIED" operation="ptrace" profile="" pid=6220 comm="Discord" requested_mask="trace" denied_mask="trace" peer="unconfined"
0 Comments
Leave a Reply. |