WineHQ
Wine Forums

Board index » WineHQ » Wine Help




 Page 1 of 1 [ 4 posts ] 



 
Author Message
 Post Posted: Wed Jan 27, 2010 5:02 pm 
Offline
Moderator
Moderator
User avatar

Joined: Wed May 14, 2008 11:44 am
Posts: 1164
Building chromium in visual c++ 2005 on current wine on an 8 core monster
machine, I got some random errors:

Inconsistency detected by ld.so: dl-open.c: 256: dl_open_worker:
Assertion `_dl_debug_initialize (0, args->nsid)->r_state ==
RT_CONSISTENT' failed!
Inconsistency detected by ld.so: dl-open.c: 256: dl_open_worker:
Assertion `_dl_debug_initialize (0, args->nsid)->r_state ==
RT_CONSISTENT' failed!
wine: Invalid handle
wine client error:0: init_thread failed with status c000011f
wine: Invalid handle
wine: Module not found
Inconsistency detected by ld.so: dl-open.c: 256: dl_open_worker:
Assertion `_dl_debug_initialize (0, args->nsid)->r_state ==
RT_CONSISTENT' failed!

c000011f is STATUS_TOO_MANY_OPENED_FILES

There were corresponding errors in the devenv log saying
that perfectly good files didn't exist, so I imagine it was just
an open failure.

The wineserver is process 1247, and sure enough, ls /proc/1247 shows
file descriptors as high as 973 in use. The default ulimit -n is 1024,
so it probably briefly exceeded that.

I guess I'll bump up ulimit -n for the wine session and keep an eye
out for leaks...
(For those who haven't done this, one way is
sudo bash
ulimit -n 5000
su dank
That gets you a normal shell with the raised file descriptor limit.)

I didn't see any of this when running on a slower 4 core machine with
source from two days ago, so I'll bet it's just the extra load.

No idea what those ld.so errors are, though.
- Dan


Top 
 Post subject:
 Post Posted: Wed Jan 27, 2010 6:19 pm 
Offline
Level 8
Level 8

Joined: Fri Feb 29, 2008 2:54 am
Posts: 1020
Most likely ld.so messages are the same as the wine one. Out of file handles so cannot operate correctly so leading to strange message.

You can set higher limits globally accross the system. I run into 1000 limits a little too much.


Top 
 Post Posted: Wed Jan 27, 2010 7:06 pm 
 
Dan Kegel wrote:
Quote:
The wineserver is process 1247, and sure enough, ls /proc/1247 shows
file descriptors as high as 973 in use. The default ulimit -n is 1024,
so it probably briefly exceeded that.
If you think that's low, on Mac OS X the default FD limit is 256! You
can only open 256 handles before the system says EMFILE.

Quote:
No idea what those ld.so errors are, though.
Anyway, recall that all loading of shared libraries is done by ld.so in
userland. I'd venture a guess that ld.so opens the file, then tries to
mmap(2) the file into memory. Key words: "opens the file". It, too is
running out of FDs. That's probably why you're getting the
dlopen(3)-related error.

Chip


Top 
 Post subject:
 Post Posted: Thu Aug 11, 2011 2:19 am 
Offline
Newbie
Newbie

Joined: Thu Aug 11, 2011 2:14 am
Posts: 2
I didn't see any of this when running on a slower 4 core machine with
source from two days ago, so I'll bet it's just the extra load.


Top 
Display posts from previous:  Sort by  
 
 Page 1 of 1 [ 4 posts ] 




Board index » WineHQ » Wine Help


Who is online

Users browsing this forum: No registered users and 10 guests

 
 

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to: