*** This bug is a duplicate of bug 445009 ***
https://bugs.launchpad.net/bugs/445009
** Changed in: eclipse-eclipsers
Status: Unknown = Confirmed
--
Eclipse crashes on installing update
https://bugs.launchpad.net/bugs/460104
You received this bug notification because you are a member
*** This bug is a duplicate of bug 445009 ***
https://bugs.launchpad.net/bugs/445009
** Changed in: eclipse (Fedora)
Status: In Progress = Fix Committed
--
Eclipse crashes on installing update
https://bugs.launchpad.net/bugs/460104
You received this bug notification because you are a
Workaround works for me, too.
System - Preferences - Assistive Technologies - Untick first checkbox -
Eclipse works.
Do you think we should mark this as a duplicate of 445009? It really
seems to be the same issue.
--
Eclipse crashes on installing update
https://bugs.launchpad.net/bugs/460104
On Mon, 2009-11-02 at 18:59 +, nh2 wrote:
Workaround works for me, too.
System - Preferences - Assistive Technologies - Untick first checkbox -
Eclipse works.
Do you think we should mark this as a duplicate of 445009? It really
seems to be the same issue.
I think it is a good idea
Yes, this workaround works for me, too.
--
Eclipse crashes on installing update
https://bugs.launchpad.net/bugs/460104
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
*** This bug is a duplicate of bug 445009 ***
https://bugs.launchpad.net/bugs/445009
** This bug has been marked a duplicate of bug 445009
Eclipse SIGSEGVs in libpango
--
Eclipse crashes on installing update
https://bugs.launchpad.net/bugs/460104
You received this bug notification
*** This bug is a duplicate of bug 445009 ***
https://bugs.launchpad.net/bugs/445009
OK, I marked it as duplicate and copied the upstream links over there.
Someone having permissions should set the importance to Medium there, too.
--
Eclipse crashes on installing update
Please check if this is a duplicate of Bug 445009. It is about a SIGSEGV in
libpango after clicking Cancel like in Comment #21 and the Red Hat upstream
bug, but not about text fields like the Eclipse upstream bug seems to be.
In this bug, there is another Eclipse upstream bug linked.
--
@nh2
Yes indeed it seems very similar.
Eclipse crashes as soon a click 'cancel' button (click close the window
using the WM) on almost every dialog windows.
The only dialog window that have not the issue is the Open file
dialogue. But on my system it is a native gnome open file window.
--
@nh2 @xaelis
Yes very similar bug.
I solved turning off Gnome Assistive Technologies, after logout Eclipsed
works again.
Please see also this bug:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/469375
--
Eclipse crashes on installing update
https://bugs.launchpad.net/bugs/460104
You
Yes ! I confirm same bug :
Turning off assistive technologies stop Eclipse crashes.
--
Eclipse crashes on installing update
https://bugs.launchpad.net/bugs/460104
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Yepp, thanks alot for the hint! turning off assistive technologies also
worked for me
--
Eclipse crashes on installing update
https://bugs.launchpad.net/bugs/460104
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Changed in: eclipse (Fedora)
Status: Unknown = In Progress
--
Eclipse crashes on installing update
https://bugs.launchpad.net/bugs/460104
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I try :
xae...@joshua:~$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v
--tool=memcheck --leak-check=full --num-callers=40 --smc-check=all
--log-file=valgrind.log --trace-children=yes /usr/bin/eclipse -vm
/usr/lib/jvm/java-6-sun/jre/lib/amd64/server/
Same result as Dario :
#
# A fatal
Note that the last crash we have with valgrind, has nothing to do with
eclipse instability we previous report.
With this last command, eclipse crash before it start (during the splash
screen).
--
Eclipse crashes on installing update
https://bugs.launchpad.net/bugs/460104
You received this bug
Hi all,
same problem here. Every time i click a cancel button from Eclipse
interface it crashes...
Here my valgrind log :)
** Attachment added: valgrind.log
http://launchpadlibrarian.net/34669714/valgrind.log
--
Eclipse crashes on installing update
https://bugs.launchpad.net/bugs/460104
sorry, my previous valgrind.log was dumb.
here one more complete. 31Mb.
Oh i'm running Intel :)
** Attachment added: valgrind.log.tar.gz
http://launchpadlibrarian.net/34672894/valgrind.log.tar.gz
--
Eclipse crashes on installing update
https://bugs.launchpad.net/bugs/460104
You received
Here is my valgrind log. I have add show-reachable option, don't know if
it can help.
xae...@joshua:~$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v
--tool=memcheck --leak-check=full --show-reachable=yes --num-callers=40
--smc-check=all --log-file=valgrind.log /usr/bin/eclipse -vm
Unfortunately, that still didn't get valgrind to trace the jvm. Let's try this:
G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck
--leak-check=full --num-callers=40 --smc-check=all --log-file=valgrind.log
--trace-children=yes /usr/bin/eclipse -vm
with this eclipse crashed even before starting up, here's the output:
G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck
--leak-check=full --num-callers=40 --smc-check=all --log-file=valgrind.log
--trace-children=yes /usr/bin/eclipse -vm
Hmm, it's trying to write valgrind.log to /usr/bin, which is going to
fail because normal accounts don't have write privs there. Try changing
--log-file=valgrind.log to --log-file=~/valgrind.log
The output should then get written to your home directory.
--
Eclipse crashes on installing update
uh, i thought that the --log-file argument was the same from the
previous commands, and didn't bother to check it... however the result
is the same as before:
G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck
--leak-check=full --num-callers=40 --smc-check=all
dario: can you attach the valgrind.log as well? it should be in your
home directory.
--
Eclipse crashes on installing update
https://bugs.launchpad.net/bugs/460104
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Looks like both logs were done on amd64 machines. Eclipse starts a new
process on launch on that arch, which means that valgrind unfortunately
didn't catch the error. You can force Eclipse to start the jvm in the
same process instead of a new one by giving it the arguments -vm
Excelent, with that command i've been able to obtain a valgrind log.
Here it is.
** Attachment added: valgrind.log
http://launchpadlibrarian.net/34570029/valgrind.log
--
Eclipse crashes on installing update
https://bugs.launchpad.net/bugs/460104
You received this bug notification because you
** Attachment added: hs_err_pid18135.log
http://launchpadlibrarian.net/34515325/hs_err_pid18135.log
--
Eclipse crashes on installing update
https://bugs.launchpad.net/bugs/460104
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Please find attached the valgrind result and the corresponding eclipse
crash log.
Step to reproduce (Not the only one !) :
xae...@joshua:~$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v
--tool=memcheck --leak-check=full --show-reachable=yes --num-callers=40
--log-file=valgrind.log
i started eclipse with valgrind
(don't know why valgrind can't solve the path, but at least it should
give a more explicative error, rather than can't open
nameofprogram i'm pretty sure in a old bug report i failed to fetch
a valgrind log due to this, i changed the ubuntu wiki page, or would
uh, seems i'm a little late... hovewer here's the error .log and the
output of running eclipse through valgrind:
G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck
--leak-check=full --num-callers=40 --smc-check=all --log-file=valgrind.log
/usr/bin/eclipse
Gtk-Message:
I've found this on my folder. It seems like a valgrind log, but i've
been never able to run eclipse with the valgrind command.
** Attachment added: Valgrind Log
http://launchpadlibrarian.net/34540503/valgrind.log
--
Eclipse crashes on installing update
https://bugs.launchpad.net/bugs/460104
Do not seem to be a pango version issue finally~:
I have just upgrade to gtk+ 2.18.3 (with pango 1.26.0) on my gentoo.
Eclipse still working with no issue.
--
Eclipse crashes on installing update
https://bugs.launchpad.net/bugs/460104
You received this bug notification because you are a member
** Bug watch added: Red Hat Bugzilla #531186
https://bugzilla.redhat.com/show_bug.cgi?id=531186
** Also affects: eclipse (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=531186
Importance: Unknown
Status: Unknown
** Changed in: eclipse (Ubuntu)
Importance: Undecided =
** Bug watch added: Eclipse bugs #285749
https://bugs.eclipse.org/bugs/show_bug.cgi?id=285749
** Also affects: eclipse-eclipsers via
https://bugs.eclipse.org/bugs/show_bug.cgi?id=285749
Importance: Unknown
Status: Unknown
--
Eclipse crashes on installing update
** Bug watch added: Red Hat Bugzilla #522187
https://bugzilla.redhat.com/show_bug.cgi?id=522187
** Changed in: eclipse (Fedora)
Remote watch: Red Hat Bugzilla #531186 = Red Hat Bugzilla #522187
** Changed in: eclipse (Ubuntu)
Status: New = Confirmed
--
Eclipse crashes on installing
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a valgrind log following the
instructions at https://wiki.ubuntu.com/Valgrind and attach the file to
the bug report. This will greatly help us in tracking down your problem.
--
Eclipse
I've been trying to obtain a valgrind log following the isntructions,
but when i try to run eclipse:
gu...@bender:~$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v
--tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log
eclipse
/bin/sh: Can't open eclipse
And nothing
This bug happen very often on karmic amd64.
Not only will installing a particular plugin but will using eclipse, making it
unusable.
Happen either with sun-jdk-6 and openjdk-6.
A same eclipse installation (from eclipse download page) works on jaunty
and crash on karmic.
I have try with a fresh
** Package changed: openjdk-6 (Ubuntu) = eclipse (Ubuntu)
--
Eclipse crashes on installing update
https://bugs.launchpad.net/bugs/460104
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: Error log
http://launchpadlibrarian.net/34339030/hs_err_pid11908.log
--
Eclipse crashes on installing update
https://bugs.launchpad.net/bugs/460104
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
39 matches
Mail list logo
