Re: More on gnome and mozilla (post-KSE)
÷ Mon, 01.07.2002, × 00:21, Julian Elischer ÎÁÐÉÓÁÌ: hmmm well, since the only changes were in the kernel except for libkvm I'm puzzled. If you boot off the old kernel (You still have it right? :-) does it still act the same? I have same problem, reverting to old (20020625) kernel not helps :( I was forced to get old world and make world. gkrellm gets 11 signal too, licq eats 100%CPU after forking qt plugin On Sun, 30 Jun 2002, walt wrote: Dunno if this is important, but I meant to mention it in my initial problem report: the problem with gnome and mozilla chewing up CPU cycles begain just after the make world finished and while the make kernel was still compiling, so whatever this problem is it was not due to changes in the kernel. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- Vladimir B. Grebenschikov [EMAIL PROTECTED], SWsoft, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: More on gnome and mozilla (post-KSE)
hmmm well, since the only changes were in the kernel except for libkvm I'm puzzled. If you boot off the old kernel (You still have it right? :-) does it still act the same? On Sun, 30 Jun 2002, walt wrote: Dunno if this is important, but I meant to mention it in my initial problem report: the problem with gnome and mozilla chewing up CPU cycles begain just after the make world finished and while the make kernel was still compiling, so whatever this problem is it was not due to changes in the kernel. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re More on gnome and mozilla (post-KSE)
Julian on FreeBSD-CURRENT wrote: On Sun, 30 Jun 2002, walt wrote: Dunno if this is important, but I meant to mention it in my initial problem report: the problem with gnome and mozilla chewing up CPU cycles begain just after the make world finished and while the make kernel was still compiling, so whatever this problem is it was not due to changes in the kernel. hmmm well, since the only changes were in the kernel except for libkvm I'm puzzled. If you boot off the old kernel (You still have it right? :-) does it still act the same? Yes. The bad behavior started with the old kernel and still does the same thing when I reboot it today. I should mention I also did see one segfault from mozilla after it churned away for 30 seconds or so, but I only saw that once--I think it was while the kernel was still compiling--and haven't seen it since. I notice today that gnumeric also segfaults with both old and new kernels. It may be possible (sorry I can't be sure) that what I'm calling the 'old' kernel may have been compiled in the middle of your KSE commit--it's dated only a couple of hours older that the 'new' kernel which was definitely made after your commit was done. If this is the case then the bad behavior may have started earlier than I thought--at the previous reboot--and I just didn't notice it. I run xfce routinely on the -CURRENT machine so I wouldn't notice the gnome breakage until my wife sat down at the machine and started whining that gnome-mahjongg didn't work ...and she couldn't read her Hotmail with mozilla either. As to your question about debugging skills--alas, few and far between. I've never used gdb but I'm willing to try if someone could give me an example of what I would need to do to give you the right info. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
