Skip to content

stream: don't call _read after destroy()

Rodrigo Muino Tomonari requested to merge github/fork/nxtedition/no-read-after-destroy into master

Partly fixes #29477 (closed).

Currently stream implementations MUST check for destroyed inside _read.

Found this while investigating a suspicious destroyed conditional in fs streams.

"Full" fix in #29485 but it is way too breaking at this point and needs more updated tests.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines

Merge request reports