Re: Freeze followed by St9bad_alloc

2010-01-18 Thread Les Denham
On Monday 18 January 2010 13:51:27 rgheck wrote:
> This suggests to me an infinite loop somewhere that keeps consuming 
> memory until there's none left, which is when you get a memory 
> allocation error. I think this is really just std::bad_alloc in disguise.
> 
Yes, that's what I would guess.

Since sending the message this morning I've upgraded to 1.6.5, and so far the 
problem has not recurred.  This could be a sign the problem was fixed in 
1.6.5, or it could be a sign that I had a problem with my installation 
(remembering that Gentoo compiles everything from source on the target 
machine) which was fixed by the recompiling and relinking in the upgrade.

Les
-- 
..
Les Denham


Re: Freeze followed by St9bad_alloc

2010-01-18 Thread rgheck

On 01/18/2010 02:10 PM, Les Denham wrote:

I have been having problems with a report I'm working on currently.

When I'm editing one of the files in the report, LyX freezes, and after
several minutes it crashes with a cryptic error message "St9bad_alloc".

This occurs most frequently when I'm doing something with a figure float.  The
most recent occurrence appeared to originate when I cut a figure float from
one child document and pasted it into another. The problem appears to
originate most commonly when I change the paragraph settings from the default
left alignment to center.  It also happens much more commonly when I'm using
US Letter page size than when using A4.  On the current document it happened
from the first time when I changed page size from A4 to Letter.

I've found I can usually fix the problem once I identify which float is
causing the error by simply opening the float and making a change in the
settings.  Apparently any change works.

   
This suggests to me an infinite loop somewhere that keeps consuming 
memory until there's none left, which is when you get a memory 
allocation error. I think this is really just std::bad_alloc in disguise.


That doesn't really tell us what the problem is, though, unfortunately. 
If you could run under a debugger, we might get more info.


rh