This is most fascinating. I looked at your procmaps and spotted a possible pattern. I think in actuality only two copies of gedit are running at once and what you have is a runaway call definition somewhere between the mainbus -- the partnership of the CPU and the core hardware systems embedded in your machine -- and direct memory allocation.
080d8000 r-xp 00000000 08:02 119485 /usr/bin/gedit 080d8000-080dc000 rw-p 0008f000 08:02 119485 /usr/bin/gedit --> This is what I'm talking about. Nothing should be getting deleted or moved at SYSV 0 if I'm not mistaken. --> 080dc000-08600000 rw-p 080dc000 00:00 0 [heap] b4954000-b4955000 ---p b4954000 00:00 0 b4955000-b5155000 rw-p b4955000 00:00 0 b5155000-b51b5000 rw-s 00000000 00:08 1769493 /SYSV00000000 (deleted) b51b5000-b52b9000 rw-p b51b5000 00:00 0 [snip] b5340000-b536c000 rw-p b5340000 00:00 0 b536c000-b53cc000 rw-s 00000000 00:08 1736723 /SYSV00000000 (deleted) <-- Can you show me the procmap commands you run and perhaps provide a snapshot of your system monitor when gedit is running? You may have hardware issues, Ramiro. <-- -- gedit open in all workspaces https://bugs.launchpad.net/bugs/269986 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
