remove a lock from VImage.cc
it wasn't really needed, and windows will barf with pointers across DLLs
This commit is contained in:
parent
b85231baba
commit
9419e07a6b
@ -2,6 +2,7 @@
|
||||
- add a compat stub, thanks Benjamin
|
||||
- python bandjoin is now just an instance function
|
||||
- small doc improvements
|
||||
- small vips7 C++ improvement
|
||||
|
||||
7/10/15 started 8.2.0
|
||||
- added im_bufmagick2vips(), a vips7 wrapper for magick load from buffer
|
||||
|
@ -216,12 +216,9 @@ VImage::VImage() throw( VError )
|
||||
|
||||
_ref = new refblock;
|
||||
|
||||
/* This is not 100% safe if VIPS threading is not implemented on this
|
||||
* platform ... but it doesn't really matter.
|
||||
/* This is not safe with threading ... but it doesn't really matter.
|
||||
*/
|
||||
g_mutex_lock( im__global_lock );
|
||||
im_snprintf( filename, 256, "intermediate image #%d", id++ );
|
||||
g_mutex_unlock( im__global_lock );
|
||||
|
||||
if( !(_ref->im = im_open( filename, "p" )) )
|
||||
verror();
|
||||
|
Loading…
Reference in New Issue
Block a user