input/curl: fixed endless loop during buffering
When the connection is lost while buffering, the CURL input plugin may enter an endless loop, because it does not check the EOF condition. This patch makes fill_buffer() return success only if there's at least one buffer, which is enough of a check.x
This commit is contained in:
parent
9a3f5ff977
commit
6037beabe1
1
NEWS
1
NEWS
|
@ -1,6 +1,7 @@
|
||||||
ver 0.15.5 (2009/??/??)
|
ver 0.15.5 (2009/??/??)
|
||||||
* input:
|
* input:
|
||||||
- curl: don't abort if a packet has only metadata
|
- curl: don't abort if a packet has only metadata
|
||||||
|
- curl: fixed endless loop during buffering
|
||||||
* tags:
|
* tags:
|
||||||
- riff, aiff: fixed "limited range" gcc warning
|
- riff, aiff: fixed "limited range" gcc warning
|
||||||
* decoder_thread: change the fallback decoder name to "mad"
|
* decoder_thread: change the fallback decoder name to "mad"
|
||||||
|
|
|
@ -315,7 +315,7 @@ fill_buffer(struct input_stream *is)
|
||||||
return false;
|
return false;
|
||||||
}
|
}
|
||||||
|
|
||||||
return true;
|
return !g_queue_is_empty(c->buffers);
|
||||||
}
|
}
|
||||||
|
|
||||||
/**
|
/**
|
||||||
|
|
Loading…
Reference in New Issue