Segmentation fault when entering and exiting container details view about pods

[SoMuchForSubtlety]

I'll try to get the native build working to get a proper stack trace with debug symbols and open a bug report upstream.

[marhkb]

This might be a tough one. I'm not 100% sure but the segmentation fault seems like a hint that we hit a bug in one of the underlying libraries. Unfortunately, I'm not able to reproduce.
Do you use flatpak or a native build?
Could you post the output of journalctl _COMM=pods

[SoMuchForSubtlety]

Do you use flatpak or a native build?

Flatpak build. Native build fails because fedora doesn't ship gtk >= 4.5 yet.

Could you post the output of journalctl _COMM=pods

Apr 06 21:24:05 honestmistake pods[184642]: GtkApplication<Application>::startup
Apr 06 21:24:05 honestmistake pods[184642]: GtkApplication<Application>::activate
Apr 06 21:24:06 honestmistake pods[184642]: Error on inspecting image '53017d7a7e2f9a1768a2fc77d42e4520399fc5f9a3050ff6583f69bc9896e14a': error 404 Not Found - failed to find image 53017d7a7e2f9a1768a2fc77d42e4520399fc5f9a3050ff6583f69bc9896e14a: could not find image instance sha256:48d031e265650d5eed9fe702e340da1b5103bf487a54e28695b5e93376a16ab4 of manifest list 53017d7a7e2f9a1768a2fc77d42e4520399fc5f9a3050ff6583f69bc9896e14a in local containers storage: image not known: image not known
Apr 06 21:24:14 honestmistake audit[184642]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=184642 comm="pods" exe="/app/bin/pods" sig=11 res=1

[marhkb]

Does this happen with all containers, or just a specific container?

[SoMuchForSubtlety]

I narrowed it down to containers with a huge amount of logs. The crash is only triggered if the logs are still scrolling to the bottom when I go back to the containers overview. If I wait for the logs to finish scrolling, going back works.

[marhkb]

Good job. What image do you use for the container that produce so many log entries? Some standard image from a repo or do you have a docker file for building the image.
Would be nice if we could build a test case here.

[SoMuchForSubtlety]

Good job. What image do you use for the container that produce so many log entries?

A Postgres container that's been running for a long time and spitting out lots of errors 😄

This should do the trick

podman run alpine sh -c "while :; do echo 'spam'; done"

[SoMuchForSubtlety]

ABRT reports the following kernel error

traps: pods[216768] general protection fault ip:7f35d4528b6a sp:7fff64ac0ec0 error:0 in libgobject-2.0.so.0.7200.0[7f35d44fc000+35000]

[marhkb]

Yes. I can reproduce now. Really seems like a bug in the underlying glib2 library, and I'm not sure how easy that is to debug.
There is #139 that includes the request to not fetch the whole log at once. I hope that will mitigate the issue.

[marhkb]

@SoMuchForSubtlety

Can you still reproduce this on the latest revision?

[SoMuchForSubtlety]

Yes, same crash still happens.

[marhkb]

Is this still an issue?

[SoMuchForSubtlety]

Seems to be fixed