Hi!

I am using LyX 1.4.3-4 on Windows XP and it is already the third or fourth time that LyX crashes while I am working on a document. Finally, I have managed to find a sequence of events that leads to the crash:

1- Open a new document and write enough lines of text (one character per line is enough) to make LyX scroll down 2- While in one of the last lines, write any letter and, almost simultaneously, press the "page up" key several times very fast.
3- LyX crashes (see below the debug messages - staring from point 2)

Is this an already known bug? If not, I will reported in bugzilla. Can someone check whether it also happens on other platforms (not Windows)?

Nicolás


Setting key to 89, y
KeySym is y
isOK is 1
isMod is 0
encoding is iso8859-1
Using codec ISO 8859-1
ISOEncoded returning value 121
void __thiscall LyXFunc::processKeySym(class boost::shared_ptr<class LyXKeySym>,enum key_modifier::state) acti
on first set to [86]
void __thiscall LyXFunc::processKeySym(class boost::shared_ptr<class LyXKeySym>,enum key_modifier::state)actio
n now set to [86]
void __thiscall LyXFunc::processKeySym(class boost::shared_ptr<class LyXKeySym>,enum key_modifier::state) Key
[action=86][Y]
LyXFunc::dispatch: cmd:  action: 86 arg: 'y' x: 0 y: 0
void __thiscall LCursor::dispatch(const class FuncRequest &) cmd: action: 86 arg: 'y' x: 0 y: 0

 cursor:                                | anchor:
inset: 01432DD0 idx: 0 par: 18 pos: 136 | inset: 01432DD0 idx: 0 par: 18 pos: 136
 selection: 0 x_target: 518

LCursor::dispatch: cmd:  action: 86 arg: 'y' x: 0 y: 0

 cursor:                                | anchor:
inset: 01432DD0 idx: 0 par: 18 pos: 136 | inset: 01432DD0 idx: 0 par: 18 pos: 136
 selection: 0 x_target: 518

void __thiscall InsetText::doDispatch(class LCursor &,class FuncRequest &) [ cmd.action = 86]
LyXText::dispatch: cmd:  action: 86 arg: 'y' x: 0 y: 0
Checking if we know [y]
   no we don't know [y]
Cannot decode: y
void __thiscall BufferView::Pimpl::updateScrollbar(void) Updating scrollbar: height: 23 curr par: 18 default h
eight 38
void __thiscall BufferView::Pimpl::update(enum Update::flags)[fitcursor = 1, forceupdate = 0, singlepar = 4]
buffer: 01398B20
class ViewMetricsInfo __thiscall BufferView::Pimpl::metrics(bool) y1: 358 y2: 444 pit1: 18 pit2: 18 npit: 23 s
inglepar: 1
#.
Redraw screen
expose 1257x874+0+0
void __thiscall BufferView::Pimpl::updateScrollbar(void) Updating scrollbar: height: 23 curr par: 18 default h
eight 38
void __thiscall BufferView::Pimpl::update(enum Update::flags)[fitcursor = 1, forceupdate = 0, singlepar = 0]
buffer: 01398B20
class ViewMetricsInfo __thiscall BufferView::Pimpl::metrics(bool) y1: -382 y2: 1410 pit1: 16 pit2: 21 npit: 23
 singlepar: 0
void __thiscall BufferView::Pimpl::updateScrollbar(void) Updating scrollbar: height: 23 curr par: 18 default h
eight 38
dispatch msg is
SelfInsert arg[`y']
keyevent has isNull() text !
KeySym is Prior
isOK is 1
isMod is 0
encoding is iso8859-1
Using codec ISO 8859-1
ISOEncoded returning value 0
void __thiscall LyXFunc::processKeySym(class boost::shared_ptr<class LyXKeySym>,enum key_modifier::state) acti
on first set to [36]
void __thiscall LyXFunc::processKeySym(class boost::shared_ptr<class LyXKeySym>,enum key_modifier::state)actio
n now set to [36]
void __thiscall LyXFunc::processKeySym(class boost::shared_ptr<class LyXKeySym>,enum key_modifier::state) Key
[action=36][PgUp]
LyXFunc::dispatch: cmd:  action: 36 arg: '' x: 0 y: 0
void __thiscall LCursor::dispatch(const class FuncRequest &) cmd: action: 36 arg: '' x: 0 y: 0

 cursor:                                | anchor:
inset: 01432DD0 idx: 0 par: 18 pos: 137 | inset: 01432DD0 idx: 0 par: 18 pos: 137
 selection: 0 x_target: 532

LCursor::dispatch: cmd:  action: 36 arg: '' x: 0 y: 0

 cursor:                                | anchor:
inset: 01432DD0 idx: 0 par: 18 pos: 137 | inset: 01432DD0 idx: 0 par: 18 pos: 137
 selection: 0 x_target: 532

void __thiscall InsetText::doDispatch(class LCursor &,class FuncRequest &) [ cmd.action = 36]
LyXText::dispatch: cmd:  action: 36 arg: '' x: 0 y: 0
__w64 int __thiscall LyXText::getPitNearY(int) const: y: 0 cache size: 6
__w64 int __thiscall LyXText::getPitNearY(int) const examining: pit: 16 y: -355 __w64 int __thiscall LyXText::getPitNearY(int) const examining: pit: 17 y: 351 __w64 int __thiscall LyXText::getPitNearY(int) const examining: pit: 18 y: 403 __w64 int __thiscall LyXText::getPitNearY(int) const examining: pit: 19 y: 489 __w64 int __thiscall LyXText::getPitNearY(int) const examining: pit: 20 y: 575 __w64 int __thiscall LyXText::getPitNearY(int) const examining: pit: 21 y: 1022 __w64 int __thiscall LyXText::getPitNearY(int) const: found best y: -355 for pit: 16 bool __thiscall LyXText::setCursorFromCoordinates(class LCursor &,int,int): x: 532 y: 0 pit: 16 yy: -382 bool __thiscall LyXText::setCursorFromCoordinates(class LCursor &,int,int): row 0 from pos: 0 bool __thiscall LyXText::setCursorFromCoordinates(class LCursor &,int,int): setting cursor pit: 16 pos: 0
__w64 int __thiscall LyXText::getPitNearY(int) const: y: -383 cache size: 6
__w64 int __thiscall LyXText::getPitNearY(int) const examining: pit: 16 y: -355 __w64 int __thiscall LyXText::getPitNearY(int) const examining: pit: 17 y: 351 __w64 int __thiscall LyXText::getPitNearY(int) const examining: pit: 18 y: 403 __w64 int __thiscall LyXText::getPitNearY(int) const examining: pit: 19 y: 489 __w64 int __thiscall LyXText::getPitNearY(int) const examining: pit: 20 y: 575 __w64 int __thiscall LyXText::getPitNearY(int) const examining: pit: 21 y: 1022 __w64 int __thiscall LyXText::getPitNearY(int) const: found best y: -1 for pit: 0 Assertion triggered in class Point __thiscall CoordCache::get(const class LyXText *,__w64 int) by failing chec
k "posit != it->second.end()" in file D:\LyX\lyx-143\src\coordcache.C:64
LyX: Attempting to save document C:/Documents/Salmonetes.lyx
  C:/Documents/Salmonetes.lyx.emergency
<Win32 path correction> [.../Salmonetes.lyx]->>[...\Salmonetes.lyx]
  Save seems successful. Phew.

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

Reply via email to