If a crash can be easily replicated and you file a bug with google, they will address the problem quickly because that problem could affect advertising revenue.
If a problem is not deemed critical such as not being able to fully restore bookmarks by importing a correctly generated bookmarks.html file, you may have to wait a year or so.
Sounds like a bug in KDE wayland or Chrome, but Chrome works fine on F44 Workstation.
I suggest starting by checking the journal logs when the freeze happens. You can see the recent logs with a command like: journalctl --since "5 minutes ago"
May 04 08:37:40 fedora plasmashell[2435]: "/home/deepak/.local/share/applications/google-chrome.desktop" contains supported protocol>
May 04 08:37:40 fedora systemd[1968]: Started app-google\x2dchrome@235fcc9434d04d67b1095fdef8e824cd.service - Google Chrome - Web Br>
May 04 08:37:41 fedora kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 234
May 04 08:37:41 fedora kernel: NVRM: GPU 0000:01:00.0 is already bound to nouveau.
May 04 08:37:41 fedora kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
May 04 08:37:41 fedora kernel: NVRM: This can occur when another driver was loaded and
NVRM: obtained ownership of the NVIDIA device(s).
May 04 08:37:41 fedora kernel: NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
May 04 08:37:41 fedora kernel: NVRM: No NVIDIA devices probed.
May 04 08:37:41 fedora kernel: nvidia-nvlink: Unregistered Nvlink Core, major device number 234
May 04 08:37:41 fedora systemd[1968]: Started app-com.google.Chrome-112075.scope.
May 04 08:37:44 fedora google-chrome-stable[112080]: [112075:112112:0504/083744.858313:ERROR:content/browser/browser_main_loop.cc:27>
May 04 08:37:44 fedora chrome[112075]: QThreadStorage: entry 2 destroyed before end of thread 0x25ac005a6700
May 04 08:37:44 fedora chrome[112075]: QThreadStorage: entry 1 destroyed before end of thread 0x25ac005a6700
May 04 08:37:44 fedora systemd[1968]: app-com.google.Chrome-112075.scope: Consumed 736ms CPU time over 3.194s wall clock time, 64.4M>
May 04 08:37:44 fedora systemd[1968]: app-google\x2dchrome@235fcc9434d04d67b1095fdef8e824cd.service: Consumed 1.779s CPU time over 4>
May 04 08:37:59 fedora plasmashell[2435]: "/home/deepak/.local/share/applications/google-chrome.desktop" contains supported protocol>
May 04 08:37:59 fedora plasmashell[2435]: qrc:/qt/qml/plasma/applet/org/kde/plasma/taskmanager/ToolTipDelegate.qml:63: TypeError: Ca>
May 04 08:37:59 fedora systemd[1968]: Started app-google\x2dchrome@7091faa33586441eb5e8e39efcae11f9.service - Google Chrome - Web Br>
May 04 08:38:00 fedora kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 234
May 04 08:38:00 fedora kernel: NVRM: GPU 0000:01:00.0 is already bound to nouveau.
May 04 08:38:00 fedora kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
May 04 08:38:00 fedora kernel: NVRM: This can occur when another driver was loaded and
NVRM: obtained ownership of the NVIDIA device(s).
May 04 08:38:00 fedora kernel: NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.