#563 Variables disappearing when heavy memory load(?)

1.3.8
closed
debugger (210)
5
2014-07-08
2007-09-05
Ben Keeping
No

When debugging a program which builds up some large memory structures, I regularly find that all the contents of the Variables tab disappear, never to return. If this is not a known problem, I might be able to provide an example.

Discussion

  • Fabio Zadrozny
    Fabio Zadrozny
    2007-09-05

    Logged In: YES
    user_id=617340
    Originator: NO

    Basically, there's a timeout for the variables to appear in the tree (so, what happens is that the messages are not passed within that timeout and pydev goes on considering something bad happened while trying to get those variables -- which could happen if some str method entered a loop or something alike).

    I guess there could be some way to raise that limit...

    Cheers,

    fabio

     
  • Boris G
    Boris G
    2008-08-11

    Logged In: YES
    user_id=2124086
    Originator: NO

    Have exactly the same problem. The variables disappear on heavy memory load. When several variables go out of the scope, the variable list appears again.

     
  • Fabio Zadrozny
    Fabio Zadrozny
    2008-08-20

    • status: open --> pending
     
  • Fabio Zadrozny
    Fabio Zadrozny
    2008-08-20

    Logged In: YES
    user_id=617340
    Originator: NO

    Actually, I've tried reproducing it here in 2 ways:
    - on a script that had variables with a sleep on the __str__ with inner variables with the same things
    - on a class that had several attributes

    and in both cases, the variables still appeared (after showing a 'wait' 'for network' for some time)... with the case with lots of variables, it was empty for some secs when scrolling, but it appeared normal

    So, if someone could attach a test-case with steps to reproduce, it'd help me a lot (since I couldn't reproduce it here -- on Pydev 1.3.19 and Eclipse 3.3 on Windows XP)

     
    • status: pending --> closed
     
  • Logged In: YES
    user_id=1312539
    Originator: NO

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).