Re: lyx 2.4.4 has a memory leak?

Baris Erkus <[email protected]> Fri, 26 Dec 2025 16:26:01 +0300
Newsgroups gmane.editors.lyx.general,gmane.editors.lyx.devel
Message-ID <OL1P279MB08818391140446945363BD6EDEB0A@OL1P279MB0881.NORP279.PROD.OUTLOOK.COM>
On 12/26/2025 4:08 PM, Jürgen Spitzmüller wrote:
> Am Freitag, dem 26.12.2025 um 15:09 +0300 schrieb Baris Erkus:
>> This is exactly what was happening in my case. I was using a theme
>> where the OS (Windows 10)  background picture and colors change
>> automatically every 3 hrs. Initially, I could not figure out that the
>> freeze+memory leak is caused by the MS Windows background and color
>> changes. Then, just by chance, I was able reproduce the leak, when I
>> change the MS Windows theme color manually. I think you can also re-
>> generate it easily: Open LyX. Go to Windows settings. Go to Themes.
>> Change the color of the theme. Observe LyX and memory usage from Task
>> Manager.
> This probably happens in the wake of the QEvent::ThemeChange signal.
>
> I cannot test myself (not having windows), but reading a bit on it
> suggests that there could be memory leaks on Windows if QPalette's are
> not properly managed/deleted.
>
> It also suggests the attached. I really do not fully understand this
> (and the most elaborate information I got was AI generated), but it
> might be worth testing whether this helps.
>
> Another possibility is that the leak happens in refillToolbars().
>
> In any case, Baris, you could check whether the hypothesis
> (QEvent::ThemeChange being the cause) is true by setting Tools >
> Preferences > User Interface > Color Scheme from "System Default" to
> either "Dark Mode" or "Light Mode". This will cause the dignal to be
> ignored.


2.5.0 RC2: Indeed. When the color scheme is not selected as System 
Default in LyX, no leak occurs and vice versa.

2.4.4: The default LyX color scheme is always attached to the Windows 
color I guess. So the leak occurs always.

Note: The difference between 2.5.0 RC2 and 2.4.4 is that the on 2.5.0 
RC2, the leak stops after some time (10-20 secs) after dumping around 
1GB memory. In 2.4.4, however, memory dump never stops. I had to kill 
the process as the memory dump went upto 6GB in the tests...

-- 
lyx-users mailing list
[email protected]
https://lists.lyx.org/mailman/listinfo/lyx-users