https://bugs.kde.org/show_bug.cgi?id=517595

            Bug ID: 517595
           Summary: Falkon 25.08.3 segfaults on Alpine when loading
                    SillyTavern; disabling renderer accessibility avoids
                    crash
    Classification: Applications
           Product: Falkon
      Version First 25.08.3
       Reported In:
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

Product: Falkon
Component: general
Version: 25.08.3
Platform: Alpine Linux x86_64

Summary
Falkon crashes reproducibly on Alpine Linux when loading a local SillyTavern
page. The crash reproduces with a fresh Falkon profile and appears to occur in
QtWebEngine accessibility registration. Passing
`--disable-renderer-accessibility` prevents the crash.

Environment
- Falkon: 25.08.3-r0
- qt6-qtbase: 6.10.1-r0
- qt6-qtwebengine: 6.10.1-r0
- OS: Alpine Linux x86_64
- Graphics stack: X11
- Repro URL: `http://127.0.0.1:8001/` (local SillyTavern instance)

Reproduction
1. Start a local SillyTavern instance on `http://127.0.0.1:8001/`.
2. Launch Falkon with a fresh profile, for example:
   `falkon -p case_fresh -r --new-window http://127.0.0.1:8001/`
3. Wait for the page to finish loading.
4. Falkon segfaults.

Observed result
- Falkon exits with signal 11 / exit code 139.
- The page loads first; the crash happens after load.
- The crash reproduces with:
  - a fresh profile
  - a copied default-style profile
  - GreaseMonkey disabled
  - user stylesheet disabled
- Disabling adblock / clearing cache / clearing cookies / optimizing DB did not
fix it.

Expected result
- Falkon should remain open after the page loads.

Backtrace (core dump)
Top frames from `gdb -batch -ex 'bt 12' /usr/bin/falkon /tmp/core`:

```
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007feb21bcdd2c in
QAccessible::registerAccessibleInterface(QAccessibleInterface*) () from
/usr/lib/libQt6Gui.so.6
#1  0x00007feb22a026dd in ??? () at /usr/lib/libQt6WebEngineCore.so.6
#3  0x00007feb28fb320b in ??? () at /usr/lib/libQt6WebEngineCore.so.6
#6  0x00007feb21f03328 in vtable for QAccessibleEvent () at
/usr/lib/libQt6Gui.so.6
#8  0x00007feb2e31a080 in ??? () at /usr/lib/libQt6WebEngineCore.so.6
#9  0x00007feb295f8690 in ??? () at /usr/lib/libQt6WebEngineCore.so.6
#11 0x00007feb28f78d56 in ??? () at /usr/lib/libQt6WebEngineCore.so.6
```

Workaround
Launching Falkon with Chromium accessibility disabled prevents the crash in
local testing:

`QTWEBENGINE_CHROMIUM_FLAGS='--disable-renderer-accessibility' falkon
http://127.0.0.1:8001/`

With that flag, Falkon survived repeated 25-second observation windows on both
fresh and default-style profiles.

Notes
- This does not look like a Falkon profile corruption issue.
- It may belong upstream in QtWebEngine / Qt accessibility, but Falkon is the
user-visible crashing application.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to