search for: threaded

Hey thanks to Johann, I got wine to install correctly on my amd64. Then I installed winetools. When I run the newest build, version 2.1.1., and try to install windows software, i get this output: bash-2.05b$ winetools found gettext in /usr/bin which: no dillo in

...c:/users/Public/Desktop/Legend\ of\ Grimrock.lnk fixme:exec:SHELL_execute flags ignored: 0x00000100 fixme:exec:SHELL_execute flags ignored: 0x00004100 [af at andre ~]$ fixme:heap:HeapSetInformation (nil) 1 (nil) 0 err:ole:CoInitializeEx Attempt to change threading model of this apartment from multi-threaded to apartment threaded err:ole:CoInitializeEx Attempt to change threading model of this apartment from multi-threaded to apartment threaded err:ole:CoInitializeEx Attempt to change threading model of this apartment from multi-threaded to apartment threaded err:ole:CoInitializeEx Attempt to change th...

Hello, sorry for my later answer. so, after i started libvirtd (no vm´s running) and attach gdb i get the following threads (gdb) info thread Id Target Id Frame 11 Thread 0x7f18fef4e700 (LWP 20695) "libvirtd" pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 10 Thread 0x7f18fe74d700 (LWP 20696) "libvirtd"

I am getting all these messages when run `passenger-status''. Do I need to worry about this? I am using passenger 2.2.2 with puppet 0.24.8 and apache2 on ubuntu 9.04. I installed it using the wiki http://reductivelabs.com/trac/puppet/wiki/UsingPassenger Thread ''Main thread'': in ''int Server::start()'' (ApplicationPoolServerExecutable.cpp:553)

I''ve recently re-installed an X4500 running Nevada b109 and have been experiencing ZFS lock ups regularly (perhaps once every 2-3 days). The machine is a backup server and receives hourly ZFS snapshots from another thumper - as such, the amount of zfs activity tends to be reasonably high. After about 48 - 72 hours, the file system seems to lock up and I''m unable to do anything

Hi ----------------ursprüngliche Nachricht----------------- Von: "Michal Privoznik" mprivozn@redhat.com An: "web2" ustermann78@web.de , "libvirt-users redhat.com" , "libvirt-list redhat.com" Datum: Wed, 01 Oct 2014 18:12:45 +0200 ------------------------------------------------- > On 01.10.2014 10:31, web2 wrote: >> Hello, >> >>

...bout its business. Signed-off-by: Jim Fehlig <jfehlig@suse.com> Which was then modified by 0a840e23 (pure code movement). The thing is, libvirt listens on events from hypervisors. And some actions that are taken subsequently may take ages to finish. However, the events are executed single threaded, so they serialize effectively. And for the long lasting actions (like shutdown, in fact in libxl shutdown only) a new thread is spawned so the event loop is not burdened for too long. The thread is created with 'detach-state' attribute so once the shutdown is handled the thread should just...

I use eMule 0.50a with wine 1.1.43, and crashes every day. I am attaching the log. Code: Xlib: extension "Generic Event Extension" missing on display ":1.0". Xlib: extension "Generic Event Extension" missing on display ":1.0". fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC90.CRT" (9.0.21022.8) Xlib:

I too am having this problem reported by Frank Hoonhout. Asterisk runs fine for a few minutes and then stops accepting new calls. (I have a standalone server with SIP phones and I'm not doing any external registration). Asterisk CVS-04/07/03-09:28:50 0x420e0037 in poll () from /lib/i686/libc.so.6 (gdb) info threads 16 Thread 14351 (LWP 7258) 0x420e187e in select () from

Now at 36 hours since zdb process start and: PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP 827 root 4936M 4931M sleep 59 0 0:50:47 0.2% zdb/209 Idling at 0.2% processor for nearly the past 24 hours... feels very stuck. Thoughts on how to determine where and why? -- This message posted from opensolaris.org

On Thu, Nov 17, 2016 at 1:20 PM, Rafael Espíndola via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> Thank you for the explanation! That makes sense. >> >> Unlike ThinLTO, each thread in LLD consumes very small amount of memory >> (probably just a few megabytes), so that's not a problem for me. At the >> final stage of linking, we spawn threads to

Hi, would be glad to be contributing with this question to all the comunity. I?m having a weird issue, suddenly I get channels on IDLE 0x00 state until I do a dahdi restart. Trying to do a call trace to see whats going on deeper, I get surprised when tried to open the .call file to see the log this is incomplete. This is what I see [root at localhost telefonica]# nano

Hello, I am initializing FDR mode and finalizing/flushing the buffers manually. XRay does not log calls from the main thread unless there is a function call after __xray_log_finalize(). This behavior is abnormal since one would expect the trace file to contain all function calls made up to the point when __xray_log_finalize() is called. To demonstrate this behavior, I have taken the test case

...rGetLastError (global error) virConnGetLastError (per connection error) virSetErrorFunc (global error handler func) When we introduced thread support we didn't try to make the virConnGetLastError/SetErrorFun work. We just updated the docs to tell applications to /never/ use them in threaded applications, and always use the virGetLastError which was thread-local backed. For back compatibility we do copy the error from the global thread local into the per-connection object, so we didn't break single-threaded apps using that old function. IOW I think you could avoid alot of the comp...

web2 wrote: > Hi > > ----------------ursprüngliche Nachricht----------------- > Von: "Michal Privoznik" mprivozn@redhat.com > An: "web2" ustermann78@web.de , "libvirt-users redhat.com" > , "libvirt-list redhat.com" > Datum: Wed, 01 Oct 2014 18:12:45 +0200 > ------------------------------------------------- > > >

I'm having problems with this combination. I thought it was problems with Ices but I'm not so sure... I start Icecast and Ices and send them to the background. Usually about 10-12 hours later, they are dead. The icecast.log file shows this: [25/Mar/2001:16:09:41] [0:Main Thread] ERROR: Could not create new thread, retrying [25/Mar/2001:16:09:41] [0:Main Thread] ERROR: Could not create

Howdy Folks, This release is after painstaking analysis of a memory leak that was reported by Bradley Taylor, reduced by myself, and then fixed after much work. You should all thank Bradley for finding the bizarre fix. It turns out the Ruby has a memory leak when you use pretty much any thread locking primitive other than Sync (Mutex, Monitor, etc.): http://pastie.caboo.se/10194 The fix (for

On 01.10.2014 10:31, web2 wrote: > Hello, > > sorry for my later answer. > > so, after i started libvirtd (no vm´s running) and attach gdb i get the following threads > > (gdb) info thread > Id Target Id Frame > 11 Thread 0x7f18fef4e700 (LWP 20695) "libvirtd" pthread_cond_wait@@GLIBC_2.3.2 () at

On Thu, Nov 17, 2016 at 7:34 PM, Rui Ueyama <ruiu at google.com> wrote: > On Thu, Nov 17, 2016 at 6:30 PM, Davide Italiano <davide at freebsd.org> wrote: >> >> On Thu, Nov 17, 2016 at 1:20 PM, Rafael Espíndola via llvm-dev >> <llvm-dev at lists.llvm.org> wrote: >> >> >> >> Thank you for the explanation! That makes sense. >>

My WOW worked fine on ubuntu 10.04. Today I installed 10.10 and the wine from the Software Center, tried to start WOW from the previous WOW folder, and got this message: World of WarCraft (build 12340) Exe: Z:\home\csababogyo\WOW\World of Warcraft\Wow.exe Time: Oct 12, 2010 10:15:32.489 PM User: csababogyo Computer: HP-Compaq-8710w