vscode: Debug console scrolls near top after each evaluated line after exception raised in debug console

Issue Type: Bug

See also https://github.com/Microsoft/vscode-python/issues/4725 - but note that vscode-python people say they

do not control the scrolling behavior of the debug console in VS Code

Expected behaviour

Debug console behaves normally

Actual behaviour

Debug console scrolls to top after each evaluated line

Steps to reproduce:

  1. Save this code as Bug.py:
import sys
sys.exit()
  1. Enable breakpoints at “Uncaught exceptions”
  2. Debug Bug.py in VS Code
  3. When hitting SystemExit exception, run print(1) in Debug console.
  4. Run sys.exit() a bunch of times (1-5 times) in the Debug console.
  5. Notice that at one point, Debug console scrolls to top
  6. Scroll to bottom of Debug console output
  7. Run print(2) in Debug console.
  8. Notice that you don’t see 2 due to Debug console scrolling near top again.

VS Code version: Code 1.32.1 (05f146c7a8f7f78e80261aa3b2a2e642586f9eb3, 2019-03-08T00:51:49.278Z) OS version: Windows_NT x64 10.0.17763

System Info
Item Value
CPUs Intel® Core™ i5-4310M CPU @ 2.70GHz (4 x 2694)
GPU Status 2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: unavailable_off
surface_synchronization: enabled_on
video_decode: enabled
webgl: enabled
webgl2: unavailable_off
Memory (System) 7.91GB (2.69GB free)
Process Argv
Screen Reader no
VM 0%
Extensions (5)
Extension Author (truncated) Version
latex-workshop Jam 6.2.0
svn-scm joh 1.47.1
python ms- 2019.2.5558
multi-command ryu 1.3.0
code-settings-sync Sha 3.2.7

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 8
  • Comments: 26 (12 by maintainers)

Commits related to this issue

Most upvoted comments

Ok, thanks for help everybody. I can repro on my mac. Investigating…

@bersbersbers we have pushed a fix with the help of @jeanp413 Please try it with VSCode insiders starting from Tuesday which will have the fix. Thank you

Thanks for the steps, I will look into this this or next week.