#5499 closed defect (fixed)
Recursive repaint SEGV
Reported by: | Owned by: | poenitz | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | painter | Version: | 1.6.0 |
Severity: | critical | Keywords: | crash |
Cc: | Juergen Spitzmueller, kmailuk@…, volker@…, lorenz@…, imjustmatthew@…, gmatht, maresr12temp@… |
Description (last modified by )
QPaintEngine::setSystemClip: Should not be changed while engine is active
QPaintEngine::setSystemClip: Should not be changed while engine is active
QWidgetPrivate::beginSharedPainter: Painter is already active
C:/Documents and Settings/rjudson/My Documents/508.lyx.emergency
QWidget::repaint: Recursive repaint detected
lyx: SIGSEGV signal caught
Sorry, you have found a bug in LyX. Please read the bug-reporting instructions
in Help->Introduction and send us a bug report, if necessary. Thanks !
Bye.
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Completed
Attachments (3)
Change History (38)
comment:1 by , 15 years ago
Severity: | normal → critical |
---|
comment:5 by , 15 years ago
Cc: | added |
---|
comment:8 by , 15 years ago
blocked: | → 5557 |
---|
comment:9 by , 15 years ago
Keywords: | crash added |
---|
I cannot reproduce this bug, neither by using Ctrl+W, moving toolbars, outliner
actions, etc.
comment:10 by , 15 years ago
Cc: | added |
---|
comment:12 by , 15 years ago
blocked: | 5557 → , volker@badziong.de |
---|
comment:14 by , 15 years ago
I cannot reproduce this bug, neither by using Ctrl+W, moving toolbars, outliner
actions, split screen, full screen, etc.
comment:15 by , 15 years ago
LyX 1.6.1 comes out around December 13, please test out if this crash occurs
also in LyX 1.6.1.
comment:16 by , 15 years ago
I can reliably reproduce this bug running both Alt-Installer-1.6.1 under Windows
XP and 1.6.0 compiled from source in Ubuntu.
For illustrations of step 1-4, see: http://tensorial.com/special/lyxcrash.png
Step 1: Create a new document with two lines. First line is "x" in math mode,
second line is "x" in regular text. It's essential to get the height correct.
Step 2: Hold down the left mouse button over the math mode "x". The math
toolbar should pop up, obscuring part/most of the math box.
Step 3: Slowly move the mouse downward
Step 4: Move the mouse beyond the point of scrolling down, but not beyond the
point of the math toolbar hiding.
Step 5: The mouse should still be over the math toolbar. Release the left mouse
button.
The result of these actions in XP causes:
QPaintEngine::setSystemClip: Should not be changed while engine is active
QPaintEngine::setSystemClip: Should not be changed while engine is active
QWidgetPrivate::beginSharedPainter: Painter is already active
C:/Documents and Settings/Ben/newfile1.lyx.emergency
QWidget::repaint: Recursive repaint detected
lyx: SIGSEGV signal caught
and in Ubuntu (1.6.0 compiled from source):
QPaintEngine::setSystemClip: Should not be changed while engine is active
QPaintEngine::setSystemClip: Should not be changed while engine is active
QWidgetPrivate::beginSharedPainter: Painter is already active
QWidgetPrivate::endSharedPainter: Attempting to end a null painter
[no crash--LyX continues to function]
This all probably seems very contrived, but it's not. I'll spend most of my
time typing at the bottom of the screen. After moving the mouse around enough,
I'll invariably retrigger this crash every few hours.
Hope this helps!
comment:17 by , 15 years ago
Cc: | added |
---|
On Linux, can you try to generate a backtrace?
http://wiki.lyx.org/FAQ/FurtherHelp#toc4
comment:18 by , 15 years ago
No luck. I can't seem to get a backtrace under Linux because it doesn't
segfault, and the error isn't fatal. (See my previous description of Windows vs
Linux.)
As an alternative, I just compiled 1.6.1 from source with the "--enable-debug"
option as the Wiki suggests, but I don't know how to get the corresponding debug
info. I did run lyx -dbg painting/scrolling. I don't know what the output
means, but nothing caught my attention.
comment:19 by , 15 years ago
I see. Maybe running under valgrind on Linux reveals something usable.
(unfortunately, I fail to reproduce the problem following your recipe).
comment:20 by , 15 years ago
i wonder how is it possible that you are able to reproduce in two different OS
while we can't even in one. isn't there something specific wrt your settings of
lyx? for example math toolbars visibility or so. isn't there something missing
in the recpipy? also what qt version in linux do you use?
comment:21 by , 15 years ago
I can reproduce it on 3 different OSes. Add my Vista computer, which behaves
identically to my XP computer.
I just got home for Xmas and installed LyX-1.6.1-1-Installer.exe on Mom's
computer. I was unable to reproduce the bug!!! :(
I'm racking my brain to figure out what I did differently. So bizarre! I'll
try some more experiments to see if I can figure it out.
Pavel--On Linux I compiled with Qt 4.4.1.
Jurgen--I'm not familiar with valgrind. I'd be willing to try something if you
could give me some guidance.
comment:22 by , 15 years ago
Subject: Re: Recursive repaint SEGV
Jurgen--I'm not familiar with valgrind. I'd be willing to try something if
you could give me some guidance.
Just run "valgrind lyx" and see if it outputs something useful on the console
after LyX has been closed. I'm not sure it actually does -- but who knows?
comment:23 by , 15 years ago
Please disregard my Comment #20 and refer only to Comment #19. I got an
"Internal Server Error" when I first submitted the attachment to bugzilla, so I
figured it didn't post. For #20 I rar'ed it and resubmitted, but forgot to
change the MIME type.
If anyone has the authority to delete comments, please delete #20 and this
(#21), as well as the attachment of 4:42:06. Thanks!
comment:24 by , 15 years ago
Cc: | added |
---|
comment:26 by , 15 years ago
I created two new bugs with recipes which are related to this. These are bug
5820 and #5821.
comment:27 by , 15 years ago
The observations on #5820 indicate that this is a Qt bug that is fixed in the
qt-copy packages that come with KDE on linux and that will be fixed upstream in
forthcoming Qt 4.5 (and probably 4.4.4).
Unless these are released, there is probably less we can do.
comment:29 by , 15 years ago
Priority: | high → normal |
---|
comment:30 by , 15 years ago
Cc: | added; removed |
---|---|
Description: | modified (diff) |
does the crash still occur with Qt 4.5.2 (which is also used for this windows installer: ftp://ftp.lyx.org/pub/lyx/bin/1.6.3/LyX-1.6.3-2-Installer.exe)?
comment:31 by , 15 years ago
comment:32 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
OK. Closing. Please reopen if you can reproduce the bug with Qt 4.5 or the installer mentioned in comment:30, respectively.
comment:33 by , 14 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Well, this keeps popping up in keytest, giving "lassert.cpp(21): ASSERTION text_.size() <= 2 VIOLATED IN GuiKeySymbol.cpp:673" see:
I have not been able to *manually* reproduce, but I will reopen as this was with Qt 4.5.2. Feel free to close again if the new information is not useful.
comment:34 by , 14 years ago
Cc: | added |
---|---|
Resolution: | → fixed |
Status: | reopened → closed |
Sorry, I don't see a relation between your keycodes (ctrl-w), the assertion (text_.size() < 2, and this bug.
Please open a new bug.
comment:35 by , 14 years ago
Cc: | added |
---|
I (dropbox314=benm) haven't triggered this crash for several months. Whatever the cause, looks "fixed" to me.
we need more detailed information. Is it reproducible? How?