Here's my problem -
I am creating a dragon GUI application which is used for wx python process After clicking on the button, some file creation / encoding that moves behind the scenes initially, it was working, while everything on the GUI fridge, so I decided to create / encode the file on a different thread - here Rubbing as soon as the method of eliminating the thread - (Expected Attracted quickly) for audiobook in audio code object:
thread in audiobook objects. Start_New (self sequel Signalbook, Tupal ([Audiobook])) Then this is a strange part - on a machine that I used to use this code, go to a thread, finish and Guai come back without cold. On any other machine, it shoots two threads very quickly and when they get locked down, they get crashed! Does the thread behavior change between some operating systems? I am using the same version of the dragon. I am completely sure about this.
Actually, I need to know two things: what happened to the Python threads, the way to end them After, and how can I create a GUI which sticks around for the trigger method to get rid of threads !!
Thanks in advance! If you need more information then let me know
If I am reminded correctly, windows The "real" threads, where there are processes in the Linux thread, the difference is that common threads share the same memory and the processes are not.
I think your program runs under Accidents and Linux under Win. If I'm not mistaken then it is possible that your CreateSingleBook-threads reach the same object, which does not have lock-protection.
With the real thorn, everything is not done properly, if not explicitly stated otherwise. Then you will get some protection against lock and race conditions.
Just my initial estimate, anyone with more information feels free to correct me or else I would advise to apply a lock on the object you are trying to manipulate.
Comments
Post a Comment