search

code-google-com / editra-plugins

Automatically exported from code.google.com/p/editra-plugins
0 stars 0 forks source link

Projects Threading issue #33

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
 Hello,

This got reported with the error reporter recently. I am not really sure what 
would cause this error other than the system running out 
of threads.

Any Ideas?

#---- System Information ----#
Editra Version: 0.2.29
Operating System: Windows NT 6.0 (build 6000)
Python Version: 2.5.1 (r251:54863, May  1 2007, 17:47:05) [MSC v.1310 32 bit 
(Intel)]
wxPython Version: 2.8.7.1 (msw-ansi)
wxPython Info:
    __WXMSW__
   wxMSW
   ansi
   wx-assertions-on
   SWIG-1.3.29
Python Encoding: Default=ascii 
File=mbcswx
Python Encoding: cp1252
System Architecture: 32bit
Byte order: little
Frozen: False
#---- End System Information ----#

#---- Traceback Info ----#
*** Sun Jan 13 16:35:21 2008 ***
Traceback (most recent call last): 
  File "build/bdist.macosx-10.3-fat/egg/projects/ProjectPane.py", line 454, in OnSyncNode
    self.scStatus(items)  File "build/bdist.macosx-10.3-fat/egg/projects/ProjectPane.py", line 611, in scStatus
    self.scCommand(nodes, status)  File "build/bdist.macosx-10.3-fat/egg/projects/ProjectPane.py", line 770, in scCommand    
wkwargs=options)
  File "C:\Python25\Lib\site-packages\wx-2.8-msw-ansi\wx\lib\delayedresult.py", line 335, in startWorker
    thread.start()  File "C:\Python25\lib\threading.py", line 436, in start
    _start_new_thread(self.__bootstrap, ())
error: cant start new thread
#---- End Traceback Info ----#

Regards,

Cody Precord

Original issue reported on code.google.com by CodyPrec...@gmail.com on 14 Jan 2008 at 1:00

GoogleCodeExporter commented 9 years ago 
I'm not sure myself what would cause it.  The error message isn't very 
descriptive.  There shouldn't be very many 
threads running at a time.  There is one thread for each open folder, but I 
would imagine that Python should be 
able to handle hundreds of threads.  This one could be difficult to reproduce.

Original comment by Kevin.Da...@gmail.com on 14 Jan 2008 at 2:08

GoogleCodeExporter commented 9 years ago 
I haven't seen any more reports of this since this original one and have been 
unable
to reproduce it in anyway.

Closing as WontFix as it may have been caused by some system condition on the
affected computer that is outside our control.

Original comment by CodyPrec...@gmail.com on 27 Aug 2008 at 3:15

GoogleCodeExporter commented 9 years ago 
Move old 'fixed' issues to verified

Original comment by CodyPrec...@gmail.com on 3 Feb 2009 at 8:18