multithreading

问题 I know the accepted, correct solutions for gracefully closing a thread. But assume my game is supposed to be fault-tolerant, and when a new gamegplay is started, it tries to gracefully close the (now-paused) thread of the old gameplay. If it fails to join it / close it (e.g. because the old thread is buggy and is in an infinite loop), it instantiates the new Thread and starts it. But I don't like the fact that the old thread is still there, eating resources. Is there an accepted way to kill

问题 I want to stop my thread after particular time. Here with i added my sample code. Any one of the thread takes more than 6 seconds means i want to stop the particular thread. Rest of the thread should not be affected. Do i need to use the Timer or some better way can we achieve? Suppose if i used Timer means do i need to create new timer for each thread and do i need to cancel the timer suppose if the job finished before 6secs? class MyRunnableThread implements Runnable{ public static int

问题 I Know that this question has been asked endlessly, but still. I think i am missing somthing. When we want updating UI( WinForm UI for the sake of argument ) in asynchronously manner. But we cannot using the async /await keyword and we have to use the ConfigureAwait(false). As i understand it "Tells" the task that it can resume itself on any available thread instead of waiting to to the main thread. Its preventing the deadlock by free the UI for not waiting for the long process to be

问题 As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 8 years ago . I feel that many classes (e.g. TcpClient , UdpClient , HttpListener ) would've been much easier to understand and use if they were

问题 I am trying to parallelize the multiplication of two matrix A , B . Unfortunately the serial implementation is still faster than the parallel one or the speedup is too low. (with matrix dimension = 512 the speedup is like 1.3 ). Probably something is fundamentally wrong. Can someone out there give me a tip? double[][] matParallel2(final double[][] matrixA, final double[][] matrixB, final boolean parallel) { int rows = matrixA.length; int columnsA = matrixA[0].length; int columnsB = matrixB[0]

问题 I have a thread that does display updates on my JFrame by using SwingUtilities.invokeLater. The thread's speed is adjustable, and when it set to full speed (no sleeping between updates), my program gets slowed down badly. I guess the problem is my thread is generating too much SwingUtilities.invokeLater events that JFrame's thread can not consume. So is there anything I can do on my thread to remove previously added but not consumed events? Or should I use some other ways to update JFrame

问题 I have written a FileSystemWatcher to call a pgm once for every file. But some of my files are lost. I tested the code with only 10-11 files. Deletion of a file is logged correctly, but not the creation. Some of the files are not logged. Is there maybe any problem in my TASK implementation? or is there any problem with Window Service ? public static FileSystemWatcher m_Watcher; static BlockingCollection<string> blockingCollection = new BlockingCollection<string>(); protected override void

问题 I'm confused of user/kernel thread and mode/context switch (Platform: Linux) I have two linked questions. (1) Is the below sentence right? If I make a system call, then mode switch (user mode to kernel mode) will occur and eventually switching from user thread to kernel thread happens. Since system call can only be executed in kernel thread, I think mode switch must occur the switching from the user thread to kernel thread. (2) Then, what we call the overhead of mode switching is that

问题 I'm confused of user/kernel thread and mode/context switch (Platform: Linux) I have two linked questions. (1) Is the below sentence right? If I make a system call, then mode switch (user mode to kernel mode) will occur and eventually switching from user thread to kernel thread happens. Since system call can only be executed in kernel thread, I think mode switch must occur the switching from the user thread to kernel thread. (2) Then, what we call the overhead of mode switching is that

问题 I'm confused of user/kernel thread and mode/context switch (Platform: Linux) I have two linked questions. (1) Is the below sentence right? If I make a system call, then mode switch (user mode to kernel mode) will occur and eventually switching from user thread to kernel thread happens. Since system call can only be executed in kernel thread, I think mode switch must occur the switching from the user thread to kernel thread. (2) Then, what we call the overhead of mode switching is that