Some tabs became freezed

[tjapro]

Tangram version

Tangram - Browser for your pinned tabs

          ID: re.sonny.Tangram
         Ref: app/re.sonny.Tangram/x86_64/stable
        Arch: x86_64
      Branch: stable
     Version: 1.4.0
     License: GPL-3.0+
      Origin: flathub
  Collection: org.flathub.Stable
Installation: system
   Installed: 158,7 kB
     Runtime: org.gnome.Platform/x86_64/42
         Sdk: org.gnome.Sdk/x86_64/42

      Commit: 35b1a223b0a36ec47155d878fe0c1ba650ce2d9e3ec351531171e63bc2368b1b
      Parent: d8b20c341e20588a33c86d154d918c48d28c88691fe76297615dda0dd1b5b648
     Subject: Update GNOME runtime to 42 (#18) (5f547083)
        Date: 2022-03-24 19:04:39 +0000

Linux distribution

Fedora 35

Flatpak version

Flatpak 1.12.7

Desktop environment

OS	- Fedora Linux 35 (Workstation Edition) x86_64 
DE	- GNOME 41.4 
WM	- Mutter  
Kernel	- 5.16.17-200.fc35.x86_64 

Summary

This has been happening a lot lately. I use Whatsapp a lot, but for some reason (I do not have a pattern or action to point to) the page became unresponsible. The only solution when this occurs is close and reopen Tangram.

[sonnyp]

Please try to reproduce with GNOME Web / Epiphany flatpak.

If you can - file a bug report on WebkitGTK

There is nothing I can do about this here.

[tjapro]

@sonnyp

Please try to reproduce with GNOME Web

I tried and the problem seems with the Gnome Web and/or Whatsapp itself, but there is a enhancement we can do:

After a while, if a webpage do not respond, the Gnome Web shows a pop-up/small window:

This window/pop-up do not appear in Tangram. If it appears we could reload the webpage (or tab, in Tangram case), without closing and re-opening the Tangram itself.

[sonnyp]

@tjapro you already got the help you need here https://bugs.webkit.org/show_bug.cgi?id=249844#c18

You need the -m parameter

[tjapro]

You need the -m parameter

Thanks for your help, and checking coredumpctl list there isn't any crash from Tangram, because it will not crash ... This is why coredumpctl didn't catch anything.

Lets see what is the result of the Webkit issue ...
Webkit team has resolved this issue, but "the change is not in TP yet". We have to wait ...