[pywin32-bugs] [ pywin32-Bugs-1476208 ] 208/py2.3: Registry ToolbarDebugging-Bar964
OLD project page for the Python extensions for Windows
Brought to you by:
mhammond
|
From: SourceForge.net <no...@so...> - 2008-02-20 22:53:08
|
Bugs item #1476208, was opened at 2006-04-25 10:58 Message generated for change (Comment added) made by rupole You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1476208&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: pythonwin Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: kxroberto (kxroberto) Assigned to: Nobody/Anonymous (nobody) Summary: 208/py2.3: Registry ToolbarDebugging-Bar964 Initial Comment: After some debugging sessions (pywin.debuger.pm()... some irregular "not pumping" states as it happens sometime ..) there are about 1000 of ToolbarDebugging-BarXXX folders filed up in the registry: some 20 in "Pythonwin Debugger" and some 900+ in "Python for Win32" Starting and exiting Pythonwin very slow (thus always saves all?) robert --- PythonWin 2.3.5 (#62, Feb 8 2005, 16:23:02) [MSC v.1200 32 bit (Intel)] on win32. Portions Copyright 1994-2004 Mark Hammond (mha...@sk...) - see 'Help/About PythonWin' for further copyright information. >>> ---------------------------------------------------------------------- >Comment By: Roger Upole (rupole) Date: 2008-02-20 17:53 Message: Logged In: YES user_id=771074 Originator: NO This should be fixed now. The ToolbarDebugging keys won't be created at all now, and will be ignored if they already exist. Not sure if it's worth the trouble to change the setup scripts to delete any existing keys. ---------------------------------------------------------------------- Comment By: Roger Upole (rupole) Date: 2008-02-19 17:07 Message: Logged In: YES user_id=771074 Originator: NO I ran into this recently myself. It appears the calls to LoadBarState and SaveBarState using "ToolbarDebugging" are completely superfluous, since the state of the Debug toolbar is already saved in the "ToolbarDefault" section. Has anyone seen an excessive number of ToolbarDefault keys being created ? ---------------------------------------------------------------------- Comment By: kxroberto (kxroberto) Date: 2006-04-26 03:39 Message: Logged In: YES user_id=972995 that massive accumulation happened definitely during using 208 yesterday - within one or some sessions within hours. The debugger was a few times in strange states. See below. Maybe the difference is also, that they accumulate in "Python for Win32" and not in "Pythonwin Debugger"? Yet, I used the debugger (also) with pywin.debugger.pm()/.run() from the Interactive pane. Yes, I may have tried to reenter the debugger while debugging. There are usually "alread pumping" warings and not allowed and so - as no sub-debugging is possible like in pdb. The debugger also enters sometime into states, where it freezes somehow on all attempts to run or step something and just says "not pumping" - also while the debugger is obviously not anymore active and I want to just run things. Then I have to restart Pythonwin. Thus there may be a mode confusion problem behind that bug or Pywin doesn't know correctly if its debugging or not ... As the debugger is a complex thing, especially when windowing apps are debugged, the debugger freeze / confusion is acceptable. Yet the protection against that massive accumulation of registry should maybe work on a lower level. Reopened it - though the bug obviously happens only upon intense use of the debugger. It took long to find out why Pywin startup _and_ exits _and_ enters/leaves the debugger very slow. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2006-04-25 18:58 Message: Logged In: YES user_id=14198 This should have been fixed a few builds ago (but sadly the fix did not include deleting the bad entries). Please try deleting those keys (or just delete the parent key) and try again - you should find only 20 or so are created (which is normal). Please reopen this bug if that is not the case. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1476208&group_id=78018 |