- This topic has 39 replies, 6 voices, and was last updated 17 years, 3 months ago by
.
-
Posts
-
Are you using the Web Browser view or the visual page designer? These are the only components I’m aware of that have bindings to the Gecko (mozilla) rendering engine which is a native binding and *could* explain what is going on.
itay.gr, I would strongly encourage you to file that bug with the Eclipse team. I did some searches through their bug tracker and am not finding anything on Platform + Gecko problems or SWT + Gecko… so it’s possible it hasn’t been reported yet.
@support-rkalla wrote:
Are you using the Web Browser view or the visual page designer? These are the only components I’m aware of that have bindings to the Gecko (mozilla) rendering engine which is a native binding and *could* explain what is going on.
itay.gr, I would strongly encourage you to file that bug with the Eclipse team. I did some searches through their bug tracker and am not finding anything on Platform + Gecko problems or SWT + Gecko… so it’s possible it hasn’t been reported yet.
I’m doing regular java development (default java prespective).
I will file a report if nothing pops up soon.
I’m doing regular java development (default java prespective).
Do you have the Web Browser view open/focused?
Oh… or do you use the AJAX tools? I think those are the only two Gecko touch-points in Eclipse proper… I’m trying to figure out where the hook that is causing it to die is.
@support-rkalla wrote:
I’m doing regular java development (default java prespective).
Do you have the Web Browser view open/focused?
Oh… or do you use the AJAX tools? I think those are the only two Gecko touch-points in Eclipse proper… I’m trying to figure out where the hook that is causing it to die is.
No and no.
Thing is, that now i tried setting the
export MOZILLA_FIVE_HOME=”/usr/lib64/firefox/”and the error message changed to:
The program ‘Eclipse’ received an X Window System error.
This probably reflects a bug in the program.
The error was ‘BadRequest (invalid request code or no such operation)’.
(Details: serial 9070120 error_code 1 request_code 0 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the –sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)Notice how “Gecko” changed to “Eclipse”.
So it seemed to have ‘touched’ the right area… or maybe not.in any case, it still crashes once every few hours.
I wonder if the previous poster was using 64 Bit centos5/RHEL5 ?
Hmm… interesting find. I wonder if the platform isn’t completely roughed out on 64-bit platforms yet?
to keep everyone up to date,
there’s a bug report on the eclipse website:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=183421I’ve submitted all the crash reports that I could.
I hope they will get it fixed soon.
