Opened 7 years ago
Last modified 6 years ago
#136 new defect
The debugger sometimes failes to display any debugging information (debugger goes blank!)
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | critical | Milestone: | |
Component: | default | Keywords: | |
Cc: | Also affects CVS HEAD (eXept version): | no |
Description
The debugger on windows sometimes goes blank without displaying any information (Model is nil).
Till now I have observed three patterns. only some are reproducible with specific steps - it is quite hard to find out a pattern for testing. It usually occurs when using StX for prolong period of time.
The observations:
- the debugger goes blank when you resize the window between two breakpoints - this is reproducible and I'll attach a short video of it
- the debugger goes blank first time when you start a debugging process for a specific window (window group?). Any subsequent debugging windows are shown correctly. When you change and try to debug something else it repeats it self; the first window does not show anything the subsequent runs are fine.
- the debugger goes blank every 2nd windows when you debug. This is probably the most annoying and simultaneously hardest to simulate. Did not yet find any pattern to reproduce this pattern.
I'll attach video + screenshots from my observations.
Attachments (4)
Change History (8)
by , 7 years ago
Attachment: | empty_window_debugger.mp4 added |
---|
by , 7 years ago
Attachment: | empty_window_debugger_v2.mp4 added |
---|
Empty debugger window between two debug runs
by , 7 years ago
Attachment: | empty_debugger_window_first_window_bug.jpg added |
---|
A screenshot for the first empty debugger window
comment:1 by , 6 years ago
To me it looks like the debugger is missing (some) damage events and does not redraw properly. When it happens to you again, could you please do the following:
- Execute following and attach the log with dump to this issue:
Builder::ReportRunner dumpProcesses
- Evaluate following and tell me whether it helped or not:
| invalidate | invalidate := [ :v | v invalidate. v subViews do: invalidate]. Debugger allInstances do: invalidate.
Thanks!
comment:2 by , 6 years ago
Hi Jan,
finally got a blank window.
ad 1) Execute following and attach the log with dump to this issue (did it twice to make sure you got the results):
Builder::ReportRunner dumpProcesses
The log file: https://swing.fit.cvut.cz/projects/stx-jv/attachment/ticket/136/smalltalk_2018-05-18_utf8.log.
In the launcher I got this output:
Collection [error]: displayString of self referencing collection. Collection [error]: displayString of self referencing collection. Collection [error]: displayString of self referencing collection. Collection [error]: displayString of self referencing collection. Collection [error]: displayString of self referencing collection. Collection [error]: displayString of self referencing collection.
ad 2) Evaluate following and tell me whether it helped or not:
I'm evaluating it, this will take somewhat longer.
by , 6 years ago
Attachment: | smalltalk_2018-05-18_utf8.log added |
---|
Builder::ReportRunner dumpProcesses -> log file
comment:3 by , 6 years ago
The debug window can be minimized and then maximized to refresh the contents. (form of invalidate Jan said).
comment:4 by , 6 years ago
I've just noticed that after a message at shell:
VERBOSE: DebugView [info] (2018-07-18 15:09:36.661): ignored error while unwinding: returnDoing context cannot be restarted/returned from VERBOSE: WARNING: DebugView [warning] (2018-07-18 15:09:36.668): abort failed VERBOSE:
The debugger window goes blank on the next debugging session.
Empty window between two breakpoints