Canceling ProcessAsync returns before inference terminates.
See original GitHub issuetry
{
await foreach (var segment in processor.ProcessAsync(decodedFileStream, ctx))
yield return segment;
}
finally
{
processor.Dispose();
}
// CPU Usage is still 100% here
I can see 100% CPU usage after ProcessAsync throws.
if I start to process another file before the CPU usage drops to zero, it pretty much crawls to a halt for minutes until the original instance terminates.
Issue Analytics
- State:
- Created 5 months ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Canceling ProcessAsync returns before inference terminates.
I can see 100% CPU usage after ProcessAsync throws. if I start to process another file before the CPU usage drops to zero,...
Read more >`vm` `Script` memory leak in Node.js 14 / 16 · Issue #40014
why UnboundScript's script cache and its code string won't GCed until kLastResort (aka. heap size up to exceeded)? Can this be fixed?
Read more >Lazy Let: A Cheap Way and Easy Way to Add Lazyness
Here a lazy variable binding delays computing it's value until actually needed. ... `x` is only computed if `conditional` returns true console.log(x); }....
Read more >Moq return task. If your method returns with a Task then you
So the rule of thumb is: if your method ends with await or return await , and it is the one and only...
Read more >Managed Language Comparison
An async method returning no result method-id Task ProcessAsync() async. invoke await type Task::Yield() invoke type Console::WriteLine("async...").
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I see you quickly released another tag 1.4.0 adding the latest master among other things. Thank you!
Thank you. Please make sure that the1.3.0 version pulls the latest
master
from whisper.cpp, as we just resolved the quantization issue there.