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

--- Comment #6 from Claudio Cambra <claudio.cam...@gmail.com> ---
(In reply to James Beddek from comment #5)
> (In reply to Claudio Cambra from comment #4)
> > (In reply to James Beddek from comment #3)
> > > (In reply to Claudio Cambra from comment #2)
> > > > Was the maps feature enabled in the settings menu?
> > > 
> > > Yes, disabling that does not cause OOM
> > 
> > Right, there is a widespread issue with QML QtLocation maps causing these
> > crashes, hence the warning on the toggle in the settings and it being
> > disabled by default. This issue has been reported upstream but there is yet
> > to be a fix, unfortunately. For now, I can say that disabling maps should
> > prevent these crashes from happening
> 
> Thanks for the info. I did heed that warning, but in my view OOM is much
> more significant and not the same as segfault or other fatal signal (crash).
> Do you have a link to the bug report? Cheers

Here's my report, feel free to add your info on there too :)

https://bugreports.qt.io/browse/QTBUG-95638

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

Reply via email to