o not a particularly satisfying outcome, but the problem is probably
(possibly?) solved. Anyone have any thoughts on either the fix or my
friend's theory?
On Thursday, November 3, 2022 at 4:13:25 AM UTC-5 Konstantin Khomoutov
wrote:
> On Mon, Oct 31, 2022 at 09:32:21AM -0700, Steven Sokol
to figure out how to generate a core dump.
>
> When you go process dies does the system function as normal?
>
> On Oct 31, 2022, at 11:52 AM, Steven Sokol wrote:
>
> Ok, here's what perf shows:
>
>
>
> root@pi4cm1(rw):/# perf record -a -g sleep 5
> Reading /p
all that means. Any thoughts?
On Monday, October 31, 2022 at 11:32:21 AM UTC-5 Steven Sokol wrote:
> I tried sending SIGABRT, but the process did not respond - continued
> running in the runaway state. I can kill it with SIGKILL but that doesn't
> generate a core. Can you suggest
wrote:
> I would simply use kill to send a signal that generates a core dump and
> exits. Make sure you have the shell and security settings setup to all this
> to happen.
>
> On Oct 31, 2022, at 9:55 AM, Steven Sokol wrote:
>
> I tried doing that and it did not seem to
I tried doing that and it did not seem to work:
root@pi4cm1(rw):/# gcore -o ~/lockup.core 22022
Unable to attach: program exited with code 1.
You can't do that without a process to debug.
The program is not being run.
gcore: failed to create /root/lockup.core.22022
The attempt somehow killed the
Typo. 1.19.1
On Wednesday, October 26, 2022 at 8:52:16 AM UTC-5 Jan Mercl wrote:
> On Wed, Oct 26, 2022 at 3:28 PM Steven Sokol
> wrote:
>
> > Currently running go 1.9.1, but I've been having this same issue since I
> started working on this project about two years
://www.google.com/profiles/eric.hubbard
>
>
> On Tue, Oct 25, 2022 at 5:28 PM Steven Sokol
> wrote:
>
>> I don't think so. I don't have it capped in the systemd configuration and
>> it's not using very much memory even in the runaway state. Here's a
nal clues.
>
> On Oct 25, 2022, at 7:28 PM, Steven Sokol wrote:
>
> I don't think so. I don't have it capped in the systemd configuration and
> it's not using very much memory even in the runaway state. Here's a
> screenshot of htop - check out t
785991-a8a9691b-4499-4e7a-b0c5-557ef2924514.png
On Tuesday, October 25, 2022 at 6:42:14 PM UTC-5 ren...@ix.netcom.com wrote:
> Are you certain you haven’t capped the memory and all of the GC threads
> are spinning trying to claim/allocate memory?
>
> On Oct 25, 2022, at 4:49 PM, Steve
Weird one. I have a go application that, on occasion, will suddenly jump
from some very low CPU usage (1% - 10%) to 400% (4 core system). I run this
app at a heightened priority and it can nearly lock the machine (Pi CM4) up.
I can kill it with SIGKILL and I'm able to get a stack trace by sendin
10 matches
Mail list logo
