|
| Iniciado por guest, 06,oct. 2016 08:00 - 1 respuesta |
| |
| | | |
|
| |
| Publicado el 06,octubre 2016 - 08:00 |
| I had a section of code that checked to make sure that threads were still running using threadstate(). I have found that not only does it report the thread as not running when it is actually working, but that it also can cause the main thread of the application to crash while leaving the supposedly non-working thread running. I removed the thread checking code and the system works just fine. Has anyone else had problems with threadstate()? |
| |
| |
| | | |
|
| | |
| |
| Publicado el 25,octubre 2016 - 17:09 |
Hi,
I'm having a similar problem. For a while now I've been trying to find a solution to a random bug that occurs with reading a socket in a thread. In about 90% of the cases, my program works fine but somthimes the thread just stops running while executing the exact same code every single time. I've checked this by logging everything and with each log I add, i check the state of the thread. Maybe it's the same problem? I've also heard about this problem in a different project of a collegue of mine. No solutions yet. I will start testing soon. |
| |
| |
| | | |
|
| | | | |
| | |
|