[ruby-core:102629] [Ruby master Bug#4405] WIN32OLE & Threads incompatible

Issue #4405 has been updated by jeremyevans0 (Jeremy Evans).

Status changed from Assigned to Closed

From my testing, this was fixed between Ruby 1.9.3 and Ruby 2.0, printing WIN32OLE object instead of raising an exception.  It still works on Ruby 3.0, so I think this can be closed.

----------------------------------------
Bug #4405: WIN32OLE & Threads incompatible
https://bugs.ruby-lang.org/issues/4405#change-90623

* Author: larsch (Lars Christensen)
* Status: Closed
* Priority: Normal
* Assignee: suke (Masaki Suketa)
* ruby -v: ruby 1.9.2p136 (2010-12-25) [i386-mingw32]
----------------------------------------
=begin
 The WIN32OLE library does not work when using Ruby threads. It may raise exceptions such as this:
 
 (druby://localhost:2002) threadsys.rb:7:in `connect': failed to parse display name of moniker `winmgmts://localhost/root/cimv2' (WIN32OLERuntimeError)
 
 WIN32 OLE api's are not generally Thread safe, and it can be argued that it is the user's task to ensure that it is accessed only from one thread, or the main thread. However, there are some complications;
 
 - Using WIN32OLE from DRb (DRb can not be used without Threads).
 - Using WIN32OLE indirectly (e.g. through Sys::ProcTable).
 
 My specific case was a DRb server that examined processes using Sys::ProcTable, which happen to use WIN32OLE.  This causes an exception. Attached is a simple script that recreates the problem. Note that in this simple case, WIN32OLE is only invokes once, and only from one single thread (and it still throws the exception).
=end


---Files--------------------------------
threadsys.rb (257 Bytes)


-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:[e-mail]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>