[Bug 1817459] Re: gedit assert failure: corrupted size vs. prev_size

2019-03-06 Thread Launchpad Bug Tracker
This bug was fixed in the package gedit - 3.31.92-1 --- gedit (3.31.92-1) experimental; urgency=medium * New upstream release - Fix segfault in open document selector (lp: #1817459) -- Sebastien Bacher Tue, 05 Mar 2019 17:09:34 +0100 ** Changed in: gedit (Ubuntu)

[Bug 1817459] Re: gedit assert failure: corrupted size vs. prev_size

2019-02-27 Thread Sebastien Bacher
Ok, I found the issue and proposed a fix upstrfeam https://gitlab.gnome.org/GNOME/gedit/merge_requests/27 ** Changed in: gedit (Ubuntu) Status: New => In Progress ** Changed in: gedit (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) -- You received this bug notification

[Bug 1817459] Re: gedit assert failure: corrupted size vs. prev_size

2019-02-27 Thread Sebastien Bacher
Ok, I managed to trigger it, you need to pick documents for the "recent document" popdown, creating new ones or using ctrl+O to open files doesn't do it (the function from the valgrind log hinted that) -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1817459] Re: gedit assert failure: corrupted size vs. prev_size

2019-02-27 Thread Sebastien Bacher
Could you give details on what you do exactly? Is adding tabs enough? Or do you need to open existing documents? Do you save same or do editing without saving in a way that should trigger the 'do you want to save before exiting' dialog? -- You received this bug notification because you are a

[Bug 1817459] Re: gedit assert failure: corrupted size vs. prev_size

2019-02-27 Thread Sebastien Bacher
Thanks, that has the details of the error ==2494== 1 errors in context 1 of 1208: ==2494== Invalid free() / delete / delete[] / realloc() ==2494==at 0x483897B: free (in /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so) ==2494==by 0x4891CEF:

[Bug 1817459] Re: gedit assert failure: corrupted size vs. prev_size

2019-02-26 Thread Cliff Carson
Added the three debug ddebs and re-ran the test with valgrind. Just as a note calling gedit and only adding a single text file will also fail with a memory error. Have a second system also running 19.04 which also appears to fails the same way with gedit. ** Attachment added: "valgrind.log"

[Bug 1817459] Re: gedit assert failure: corrupted size vs. prev_size

2019-02-26 Thread Sebastien Bacher
Thanks, valgrind tend to avoid the segfault but does collect the errors still, your log has one ==18294== Invalid free() / delete / delete[] / realloc() ==18294==at 0x483897B: free (in /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so) ==18294==by 0x4891CEF: ??? (in

[Bug 1817459] Re: gedit assert failure: corrupted size vs. prev_size

2019-02-26 Thread Cliff Carson
Can get a consistent memory error by opening gedit from a command line and then adding 3 small text files (have three tabs open). Then using the window close terminating the gedit window. Get one of two error indications but no error processing. cliff@cliffps:~$ gedit malloc_consolidate():

[Bug 1817459] Re: gedit assert failure: corrupted size vs. prev_size

2019-02-25 Thread Sebastien Bacher
Thank you for your bug report. Do you have special plugins in use? Could you describe what you were doing when hitting the issue? Please also 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