Menu ▾ ▴

PyDev extensions crashing w/ memory leak

David Hill
2008-06-16
2013-03-15
  • David Hill

    David Hill - 2008-06-16

    This posting references bug 1995546. Probably should have started here, but the buggy nature of the issue had me thinking I should start directly with a bug post.

    I'm about 5000 lines into a wxPython project and all has been well. Have begun experiencing repeatable system crashes associated with PyDev Extensions. Code contains this simple line:

    self.manager = wx.aui.AuiManager()

    Highlighting the characters "manager" (by whatever means, double click on the token or left-click drag) causes the eclipse process to immediately go from 120MB to 330MB, and CPU to 100%. Eclipse can be closed (sloooowly). This behavior is repeatable, and is only seen on this single wx.aui.AuiManager object. Highlighting this variable name anywhere in the code causes the same hang. There is no error log message. Problem goes away when the PyDev Extensions plugin is disabled.

    System information:
    Windows XP
    Memory: 1G
    PyDev/PyDev Extensions 1.3.15 and 1.3.17
    Eclipse 3.3.2
    wxPython 2.8.7.1

    Any Ideas?

     
    • Fabio Zadrozny

      Fabio Zadrozny - 2008-06-18

      Are you passing the -Xmx to the vm Eclipse is running on? (that 1GB is the amount of memory you have or the amount of memory allocated to eclipse?)

       
      • David Hill

        David Hill - 2008-06-18

        I was not using the -Xmx option. 1GB is the total memory in the machine.

        At your suggestion I then passed -Xmx356M, expecting the heap to fill and the system hang again. When I selected the same token described in the original post, the memory footprint of the eclipse process rose from 101M to 384M and stayed there. However, (pleasant surprise) this time Eclipse (and the system) appears fully functional.

        Changed to -Xmx456M. On selecting the token, memory footprint of the process rises from 100M to 508M. Again, eclipse appears to function normally.

        Appears an interaction of code completion with this wxPython object. Does it merit further investigation?

        Thanks, Fabio, for the great support.

         
        • Fabio Zadrozny

          Fabio Zadrozny - 2008-06-19

          Actually, the memory you see allocated is not always the actual memory in use -- it seems to keep there, but that may not be the actual amount of memory that it's using... that's why you get those results... I think there's a plugin that can give you a better report on the actual memory being used in a java vm -- but I don't remember which one was -- anyways, it doesn't seem to be leaking for me (just the memory requirements for having the wx tokens were higher than what you were giving to Eclipse).

          Cheers,

          Fabio