Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash when disposing GZipStream #21760

Open
DReichl opened this issue Apr 24, 2024 · 1 comment
Open

Crash when disposing GZipStream #21760

DReichl opened this issue Apr 24, 2024 · 1 comment

Comments

@DReichl
Copy link

DReichl commented Apr 24, 2024

Steps to Reproduce

The crash occurs when disposing a GZipStream object.

See the attached 'GZipBug' demo application.
GZipBug.zip

Current Behavior

Mono crashes natively (SIGSEGV).

See the attached files 'Output.txt' and 'mono_crash.b8f900552.0.json' for details.
Output.txt
mono_crash.b8f900552.0.json

Expected Behavior

Mono should not crash (and the 'GZipBug' demo application writes 'Test successful!').

On which platforms did you notice this

[ ] macOS
[X] Linux (Fedora 40)
[ ] Windows

Version Used: 6.12.0.199

Stacktrace

at <unknown> <0xffffffff>
at System.IO.Compression.DeflateStreamNative:CloseZStream <0x00092>
at SafeDeflateStreamHandle:ReleaseHandle <0x00033>
at System.Runtime.InteropServices.SafeHandle:DangerousReleaseInternal <0x00229>
at System.Runtime.InteropServices.SafeHandle:InternalDispose <0x0003f>
at System.Runtime.InteropServices.SafeHandle:Dispose <0x0003b>
at System.Runtime.InteropServices.SafeHandle:Dispose <0x00031>
at System.IO.Compression.DeflateStreamNative:Dispose <0x000bb>
at System.IO.Compression.DeflateStream:Dispose <0x0005b>
at System.IO.Stream:Close <0x00034>
at System.IO.Stream:Dispose <0x0002f>
at System.IO.Stream:Dispose <0x00073>
at System.IO.Compression.GZipStream:Dispose <0x0004f>
at System.IO.Stream:Close <0x00034>
at System.IO.StreamReader:Dispose <0x00064>
at System.IO.TextReader:Dispose <0x00034>
at GZipBug.Program:Main <0x001c3>
at System.Object:runtime_invoke_void <0x00086>
@tuliom
Copy link

tuliom commented Apr 26, 2024

PR #21759 fixes this issue.
We got a confirmation downstream about this fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants