RH7.1/gcc 2.96-81, clobbered CVS build from 05/12/2001 01:32 I realize i'm using an unofficial compiler, but today i crash each time i reply to a newsgroup. The posting is sendt - crash occures immediately afterwards. Happens all the time.
Can't send attachments today either.. and when using NC4.77 it landed in another bug first. Dunno which :/
R.K.Aa, I'd upgrade this to be smoketest blocker if someone else can verify it.
I'm seeing this not only with Newsgroup postings but on most email sends. I can't verify its exact location but it's happening on both the official nightlies and my own CVS compiled stuff. Been seeing it for about two days, and have been looking for the bug to file it under because it looked like something that someone else would already have reported. Linux, kernel 2.4.4, X-4.0.3
thanks for logging the bug with the stack trace. that stack trace resembles another one I saw recently, involving the timer for the caret. let me go find it..
I found #80209, but that wasn't the bug I was looking for.
There seems to be problems also when replying to a mail with a "Reply-To" header. (Replying to one with only a "From" went OK.)
Now i got the first stack again on replying to a plain mail. (nsView::GetPosition). I'm crashing around 80% of the time when replying to anything in mailnews.
sspitzer: You were probably looking for bug 80355 (just found it referred to in the newsgroup). It crashes in nsCaret::GetViewForRendering
yes, #80355 was the one. thanks.
Assignee: sspitzer → ducarroz
Tried to mail you yet a stack. Got it? (i crashed)
Resolving as invalid. I use gcc2.96RH which I'm told is to be considered bugged.
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → INVALID
using this as my mail trash-bug since i still crash frequently. - current CVS after mailing reply and attaching a jpg: #0 0x0073002f in ?? () at eval.c:41 #1 0x41488e77 in nsCaret::DrawCaret () from components/libgklayout.so #2 0x41489525 in nsCaret::CaretBlinkCallback () from components/libgklayout.so #3 0x40d9b176 in nsTimerGtk::FireTimeout () from components/libtimer_gtk.so #4 0x40d9b37f in process_timers () from components/libtimer_gtk.so #5 0x40d9b3ff in TimerCallbackFunc () from components/libtimer_gtk.so #6 0x40682731 in g_timeout_dispatch () from /usr/lib/libglib-1.2.so.0 #7 0x406817f3 in g_main_dispatch () from /usr/lib/libglib-1.2.so.0 #8 0x40681dd9 in g_main_iterate () from /usr/lib/libglib-1.2.so.0 #9 0x40681f8c in g_main_run () from /usr/lib/libglib-1.2.so.0 #10 0x40596803 in gtk_main () from /usr/lib/libgtk-1.2.so.0 #11 0x404d1125 in nsAppShell::Run () from components/libwidget_gtk.so #12 0x404b3406 in nsAppShellService::Run () from components/libnsappshell.so #13 0x0804e170 in main1 () at eval.c:41 #14 0x0804e9d1 in main () at eval.c:41 #15 0x401fb177 in __libc_start_main (main=0x804e898 <main>, argc=1, ubp_av=0xbffff72c, init=0x804aab4 <_init>, fini=0x805035c <_fini>, rtld_fini=0x4000e184 <_dl_fini>, stack_end=0xbffff71c) at ../sysdeps/generic/libc-start.c:129
Mark it as verified/invalid.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.