[Bug gdb/25965] New: gdb consumes GBs RAM when attaching or running debug version of LibreOffice

[Bug gdb/25965] New: gdb consumes GBs RAM when attaching or running debug version of LibreOffice

[hi-angel at yandex dot ru]

https://sourceware.org/bugzilla/show_bug.cgi?id=25965

            Bug ID: 25965
           Summary: gdb consumes GBs RAM when attaching or running debug
                    version of LibreOffice
           Product: gdb
           Version: 9.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: hi-angel at yandex dot ru
  Target Milestone: ---

Created attachment 12523
  --> https://sourceware.org/bugzilla/attachment.cgi?id=12523&action=edit
autogen.sh without optimization and disabled building of various components

Attaching to debug version of LibreOffice makes gdb consume 2.1 GB of RAM (that
is despite LibreOffice itself consuming 35x MB). gdb is also very slow in
actual debugging session.

Alternative way to reproduce is to run `make debugrun` (gdb appears), set
breakpoint on `main`, then execute `run`. 2.1 GB gets consumed after executing
`run` and before stopping on `main`.

I disabled all auto-loading features I found, to no avail. So it's a problem
with the gdb itself rather than of some LO debugging script.

---------------------------

I understand building LO is too big of a venture, so if you got ideas to check,
it may be easier to make me check them for you.

# Steps to reproduce

1. run `git clone git://anongit.freedesktop.org/libreoffice/core libreOffice &&
cd libreoffice`
2. Download into current dir the attached `myautogen.sh` (it just disables
building of a bunch of components and disables optimizations)
3. Run `./myautogen.sh && make`, and make sure it finishes successfully
4. Launch built LO by executing `instdir/program/swriter`
5. Execute `gdb -nx -iex "set auto-load off" --pid=$(pidof soffice.bin)`
6. Look at the memory gdb takes (for example by executing `smem -kc "name user
pid pss"`)

## Expected

Some hundreds of MB I'd expect.

## Actual

It takes 2.1 GB or sometimes even 2.3 GB (it seems to take 2.3 at the beginning
and then drop down to 2.1).

-- 
You are receiving this mail because:
You are on the CC list for the bug.