Not that I would know if this is a crash or not, but at least I'm still
seeing tons on unreaped npviewer.bins with the latest nspluginwrapper.
Who's the parent here that's supposed to reap these? Firefox itself?
jmk 5129 5097 13 Jul28 ?11:31:35 [npviewer.bin]
--
npviewer.bin cras
Just started happening to me as well after updating to Intrepid.
Thedailyshow worked well with Hardy + unofficial flash 10. Hardy with
'official' Flash 9 had the same problem.
--
npviewer.bin crashed with SIGSEGV in PL_HashTableLookupConst()
https://bugs.launchpad.net/bugs/285212
You received thi
Public bug reported:
Binary package hint: nspluginwrapper
Flash video stream used by thedailyshow seems to reliably crash nspluginwrapper.
kernel: [96509.058961] npviewer.bin[30695]: segfault at 726f7463 rip 726f7463
rsp ffab863c error 14
http://www.thedailyshow.com/
nspluginwrapper
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/16952387/Dependencies.txt
** Attachment added: "ExtensionSummary.txt"
http://launchpadlibrarian.net/16952388/ExtensionSummary.txt
** Attachment added: "pluginreg.dat.txt"
http://launchpadlibrarian.net/16952389/pluginr
Public bug reported:
Binary package hint: udev
My system randomly ends up in condition after bootup where I have 3
instances of udevd running of which upstart is only aware of one. None
of them seem properly working as ethernet device renaming has not been
finalized.
My guess for the reason migh
On Tue, Dec 1, 2009 at 12:29 AM, Scott James Remnant
wrote:
> Upstart waits for udevd to fork() before emitting "started udevd", this
> is sufficient to avoid races. udevd has opened all sockets and is
> listening on them by the time it forks, while it may not be in the main
> loop, any connectio
Luke Kim: quite unlikely that above patch would cause the issue you
see.. are you sure something else did not break in your environment?
Can you execute that same make manually?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
LK: Ok, good catch, that might be more suitable option. Thanks,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/955379
Title:
cmake hangs with qemu-arm-static
To manage notifications about this bug g
Ok, test case attached (80M tar). This hugely stripped one is not 100%
reproducer, but do few loops and you will hit it. Instructions for using:
- extract, chroot
- cd /home/abuild/rpmbuild
- su abuild
- export RPM_BUILD_ROOT=$PWD
- rpmbuild -ba SOURCES/libshortcut.spec
** Attachment added: "Tiz
Mind you, when you hit the bug it just hangs and cmake test errors are
just to speed up the process of hitting the bug (if cmake just fails you
did not hit the bug). Feel free to try with any qemu variant, they all
hang similarly when bug is hit. I think that root had some suse 1.2 one
inside.
--
If that is the case for you (for me it reproduces it every 4-5 runs or so),
there are two options:
1) put while(true) loop around the rpmbuild and you will hit it always, or
2) I can wrap up a bit bigger cmake usecase that systematically hits it. Warn
you though, size will jump to 200M.
--
You
> this blocks forever, because the thing that would wake it up is the
signal handler writing to the pipe we're selecting on, but we will never
run the signal handler until select exits
Duh, makes sense, have to think about this. Thank you for great analysis
:)
Apparently have to dig into qemu's c
So I guess 'raciness' of my proposed patch would only depend on how
small I could squeeze the section between 'sigpending' flag comparison
and actual syscall entering?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
And what would break if we make poll timeout instantly in case there are
signals pending and restart the given syscall after handlers run?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/955379
Title:
Moreover, is there even a need to restart anything, just make it async
call in case signals were pending?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/955379
Title:
cmake hangs with qemu-arm-static
Never mind, async/zero timeout call would suffer from same (albeit now
tiny) race. It would make this far less invasive as a change though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/955379
Title:
Just out of interest tried how far the timeout hackery can go working
around the issue. Well, looks like it goes quite far: having previously
reproduced the hang in 4-5 runs and in under a minute, now have had this
running without a hang for an hour. I will also test the patch under OBS
worker(s) a
Some kind of semi-workaround patch attached. It seems to leave this kind
of race window for me (for select which is worse):
0x6004bf98 <+136>: xor%r8d,%r8d
0x6004bf9b <+139>: test %eax,%eax
0x6004bf9d <+141>: jne0x6004c2b7
0x6004bfa3 <+1
Peter, I have qemu chrootable test case under which you could fire one
command to hit the bug reliably. Only issue is, are you willing to take
a peek at 100M extractable tarball? If not, I'll try to create a smaller
one.
--
You received this bug notification because you are a member of Ubuntu
Bug
19 matches
Mail list logo
