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

Méven <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|ASSIGNED                    |RESOLVED
      Latest Commit|                            |https://invent.kde.org/syst
                   |                            |em/dolphin/-/commit/f57ff70
                   |                            |e85e331b08049e8c8cc677fb10d
                   |                            |2fd5fe

--- Comment #7 from Méven <[email protected]> ---
Git commit f57ff70e85e331b08049e8c8cc677fb10d2fd5fe by Méven Car.
Committed on 07/11/2026 at 09:57.
Pushed by meven into branch 'master'.

Keep the state of a tab within what a session file holds

A session keeps the state of a tab in one entry of an ini file, and KConfig
reads back at most 1.5 MB
of one entry. The state carries the selected items and the expanded folders of
every view of the tab,
which are as many urls as the folder holds items. Selecting all of a folder of
a hundred thousand
files wrote a state of several megabytes, and what came back was cut short,
with a parse error per
line KConfig had to invent, and a session Dolphin could not start from.

A view now writes its selection, and its set of expanded folders, only while
they stay under a share
of that limit, and a state that reads back short is dropped rather than
applied.

The state also said which of the two views of a tab was the active one, and a
state cut short before
that said the secondary one. Restoring it then set the active view on a split
view that is not there,
which is the crash this report is about.

M  +27   -3    src/dolphintabpage.cpp
M  +5    -0    src/tests/CMakeLists.txt
A  +104  -0    src/tests/dolphintabpagetest.cpp     [License: GPL(v2.0+)]
M  +43   -8    src/views/dolphinview.cpp

https://invent.kde.org/system/dolphin/-/commit/f57ff70e85e331b08049e8c8cc677fb10d2fd5fe

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

Reply via email to