Bug report did not close due to bug watch
Initial reports were about GNOME 2 version of gedit
Upstream issue closed "RESOLVED OBSOLETE" on 2020-11-24
No reply to comment #10 after almost 4 years so closing
** Changed in: gedit (Ubuntu)
Status: Incomplete => Invalid
** Changed in: gedit (Ub
** Tags added: intrepid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/305927
Title:
gedit leaks memory
To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/305927/+
Does this still occur on Ubuntu 18.10 "Cosmic Cuttlefish" with gedit
3.30.2-0ubuntu0.18.10.2?
Several memory leaks were fixed in gedit 3.14.0-3.
** Changed in: gedit (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bu
** Changed in: gedit
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/305927
Title:
gedit leaks memory
To manage notifications about this bug go to:
https://bugs.laun
** Changed in: gedit
Importance: Unknown => Critical
--
gedit leaks memory
https://bugs.launchpad.net/bugs/305927
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://li
Note that the memory usage appears related to the text highlighting.
I loaded a moderately large (~100MB) XML file. Once the initial load
finishes, CPU usage stays high while highlighting is proceeding. Memory
usage skyrockets during this time (in my case, eventually hitting 1.2GB
resident). Cl
I've got a git checkout and rand valgrind, the leaks that are definite
according to valgrind:
libio (from glib)
launchpadintegration bug #483610
glibc nns (g_option_context_parse)
libfontconfig in a call of FcConfigParseAndLoad XML_ParseBuffer
from g_type_create_instance into fontconfig
g_object_
** Changed in: gedit
Status: Unknown => New
--
gedit leaks memory
https://bugs.launchpad.net/bugs/305927
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.u
Thank you for sending the bug to GNOME
** Changed in: gedit (Ubuntu)
Status: New => Triaged
** Bug watch added: GNOME Bug Tracker #568558
http://bugzilla.gnome.org/show_bug.cgi?id=568558
** Also affects: gedit via
http://bugzilla.gnome.org/show_bug.cgi?id=568558
Importance: Unkno
yes i've sent it upstream this is the bug number 568558
--
gedit leaks memory
https://bugs.launchpad.net/bugs/305927
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://li
did you sent it upstream ? may you tell us the bug number or should we
close this report?
--
gedit leaks memory
https://bugs.launchpad.net/bugs/305927
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
deskto
those logs have no real leaks, should be sent to bugzilla.gnome.org by
somebody having the issue though
--
gedit leaks memory
https://bugs.launchpad.net/bugs/305927
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs maili
** Changed in: gedit (Ubuntu)
Status: Incomplete => New
--
gedit leaks memory
https://bugs.launchpad.net/bugs/305927
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
htt
and this is by opening the same file only one time and then closing it
(while the previous one was opening closing opening closing)
** Attachment added: "valgrid log"
http://launchpadlibrarian.net/20322813/valgrind2.log
--
gedit leaks memory
https://bugs.launchpad.net/bugs/305927
You received
This is by opening a 7mb file (this time) two times
** Attachment added: "valgrind log"
http://launchpadlibrarian.net/20322812/valgrind.log
--
gedit leaks memory
https://bugs.launchpad.net/bugs/305927
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a valgrind log following the
instructions at https://wiki.ubuntu.com/Valgrind and attach the file to
the bug report. This will greatly help us in tracking down your problem.
** Changed in: gedi
16 matches
Mail list logo
