Neil Hodgson wrote:
Joe Sislow:
The program 'SciTE' received an X Window System error.
This probably reflects a bug in the program.
Main reasons for getting X Window errors are sending oversize
requests. There are various work-arounds for this in Scintilla such as
breaking long strings up. Try changing SciTE version: if 1.73 is
having problems then maybe an older version doesn't. One feature that
has been causing some issues is translucency when attempted over a
large area (such as selecting a 10,000 character line) so you could
try turning off the translucent selection - selection.alpha=256.
I've upgraded, but not downgraded, so I'll try an earlier version. I've
had no luck with the RPM (currently sitting at 1.71-1) or the latest
source (1.73). Both crash regularly.
I'll also try turning off the selection.alpha. I suppose my mouse could
be slipping when I scroll, and it highlights a lot. I'll play with that
and see if I can induce it.
Another area to look at is how are you using SciTE that is
different to others. What properties have you changed and does
reverting them fix the problem? Are you writing text rather than code;
using an uncommon lexer; displaying on a limited palette screen; or
are you writing in Hindi? My main Linux installation is FC6 (upgraded
from FC5 so may not be exactly same as raw install) so FC6 gets tested
by me more than other GTK+ platforms.
I'm not doing anything fancy that I'm aware of. I use a black
background, so I've wacked out the colors a bit. I primarily edit C
code, but I occasionally edit text. I've also got 3-5 files open for
long periods of time (days). I also used fixed width characters for
everything. Oh, most of the files I edit are on an nfs mount, too --
not local to my drive.
This install is -- I believe -- upgraded from FC4. I've gone through
with ldd to make sure I'm up to date on any relevant libs. Since I saw
crashes reported on other apps recently (Firefox and audacity come to
mind), I figured some bug crept into the xorg libs somewhere, and since
it's intermittent, it's hard to find. All I know is that I'm getting
crashes rather regularly (every day or two) no matter what I've done
with the libs. Since other apps have been crashing with the same error,
though, I wasn't willing to blame SciTE, but I figured I'd have better
odds of getting to the bottom of it here.
Anyway, is there anything I can do to try and track down the offending
lib? The only other app that's crashing occasionally is Firefox, and I
don't think I'll have much luck getting help from the Mozilla folks.
SciTE should process a --sync command line option to talk to X
synchronously so that failures are reported immediately which should
make it possible to get a backtrace. Unfortunately --sync makes SciTE
very slow.
Yeah, I ran that and it just spit up the same error. Is there a debug
command I can enable thru configure or something to have it spit more
info when it dies? Also...with some of my source files...it's
UNBEARABLY slow, so it's hard to run it regularly that way.
Thanks. Anything else I can do to track it down?
_______________________________________________
Scite-interest mailing list
[email protected]
http://mailman.lyra.org/mailman/listinfo/scite-interest
