AppArmor message spam about Discord snap in my kernel ring buffer

So I was trying to debug some stuff, and noticed that my snap installation of Discord seems to fill my kernel ring buffer with the same request which is being "DENIED" by the AppArmor. Message in question:

[ 1044.201470] audit: type=1400 audit(1732616387.440:44954): apparmor="DENIED" operation="ptrace" class="ptrace" profile="snap.discord.discord" pid=5626 comm="Utils" requested_mask="read" denied_mask="read" peer="unconfined"
[ 1044.201478] audit: type=1400 audit(1732616387.440:44955): apparmor="DENIED" operation="ptrace" class="ptrace" profile="snap.discord.discord" pid=5626 comm="Utils" requested_mask="read" denied_mask="read" peer="unconfined"
[ 1044.201491] audit: type=1400 audit(1732616387.440:44956): apparmor="DENIED" operation="ptrace" class="ptrace" profile="snap.discord.discord" pid=5626 comm="Utils" requested_mask="read" denied_mask="read" peer="unconfined"
[ 1044.201499] audit: type=1400 audit(1732616387.440:44957): apparmor="DENIED" operation="ptrace" class="ptrace" profile="snap.discord.discord" pid=5626 comm="Utils" requested_mask="read" denied_mask="read" peer="unconfined"
[ 1044.201514] audit: type=1400 audit(1732616387.440:44958): apparmor="DENIED" operation="ptrace" class="ptrace" profile="snap.discord.discord" pid=5626 comm="Utils" requested_mask="read" denied_mask="read" peer="unconfined"
[ 1044.201522] audit: type=1400 audit(1732616387.440:44959): apparmor="DENIED" operation="ptrace" class="ptrace" profile="snap.discord.discord" pid=5626 comm="Utils" requested_mask="read" denied_mask="read" peer="unconfined"
[ 1044.201535] audit: type=1400 audit(1732616387.440:44960): apparmor="DENIED" operation="ptrace" class="ptrace" profile="snap.discord.discord" pid=5626 comm="Utils" requested_mask="read" denied_mask="read" peer="unconfined"

(the spam is at a point where its very difficult to find any message which isn't this one...) I was wondering if people know what might cause this, and if this is harmful behaviour I should seek to fix (my machine has been a bit unstable, but I'm still unsure if that's a hardware or a software issue...)