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

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.

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

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.

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

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.