Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #99455 > unrolled thread
| Started by | Marc Aymerich <glicerinu@gmail.com> |
|---|---|
| First post | 2015-11-25 15:10 +0100 |
| Last post | 2015-11-25 15:10 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Futex hang when running event loop on a separated thread Marc Aymerich <glicerinu@gmail.com> - 2015-11-25 15:10 +0100
| From | Marc Aymerich <glicerinu@gmail.com> |
|---|---|
| Date | 2015-11-25 15:10 +0100 |
| Subject | Re: Futex hang when running event loop on a separated thread |
| Message-ID | <mailman.74.1448460653.20593.python-list@python.org> |
On Tue, Nov 24, 2015 at 9:17 PM, Marc Aymerich <glicerinu@gmail.com> wrote: > On Tue, Nov 24, 2015 at 8:41 PM, Zachary Ware > <zachary.ware+pylist@gmail.com> wrote: >> On Tue, Nov 24, 2015 at 12:37 PM, Marc Aymerich <glicerinu@gmail.com> wrote: >>> still it appears to work only if the main thread is in the foreground >>> (as of calling Thread() with deamon=True), I don't get why it behaves >>> differently :( maybe it is waiting for other stuff, but no idea how to >>> confirm this with strace of other means.. i always see the same >>> 'futex(0x7f9a70000c10, FUTEX_WAIT_PRIVATE, 0, NULL' >> >> What's your exact version of Python? asyncio is still evolving >> rapidly, and may behave differently between patch releases (say, >> between 3.4.1 and 3.4.3). >> >> I have tried out your reproducer with my fix, and I can't provoke a >> hang using Python 3.4.3 on either OSX or Ubuntu Trusty. Can you give >> some more specific directions to reproduce? >> >> -- >> Zach >> -- >> https://mail.python.org/mailman/listinfo/python-list > > > Yep, I'm a bit lost about how fuse implements going into background... > so the only way I have to reproduce this so far is by using fuse :( problem solved ! Just found out that threads should be started by fuse.init() in order to run when fuse is backgrounded. -- Marc
Back to top | Article view | comp.lang.python
csiph-web