mirror of
https://github.com/juce-framework/JUCE.git
synced 2026-01-15 00:24:19 +00:00
9b90398cf9
As far as I can tell, if a read was cancelled from a background thread, the IO operation wasn't cancelled, so the system was poking at the stack-allocated OVERLAPPED structure after it had been removed from the stack, at which point something else might be occupying that region of stack memory. I'm pretty sure Address Sanitizer should be able to catch this sort of thing so I'm surprised it didn't complain here. |
||
|---|---|---|
| .. | ||
| juce_analytics | ||
| juce_audio_basics | ||
| juce_audio_devices | ||
| juce_audio_formats | ||
| juce_audio_plugin_client | ||
| juce_audio_processors | ||
| juce_audio_utils | ||
| juce_blocks_basics | ||
| juce_box2d | ||
| juce_core | ||
| juce_cryptography | ||
| juce_data_structures | ||
| juce_dsp | ||
| juce_events | ||
| juce_graphics | ||
| juce_gui_basics | ||
| juce_gui_extra | ||
| juce_opengl | ||
| juce_osc | ||
| juce_product_unlocking | ||
| juce_video | ||
| CMakeLists.txt | ||