Re: Another appeal about Flaky browsers
On 07/28/2016 11:31 AM, Alan McConnell wrote: Have you started it in "safe-mode"? Mo problems with it running sid and chrome directly installed from google. Ric I have to call chromium from the command-line. I have just tried 'chromium -safe-mode &'. It runs fine for a while, but then the randaom 'Aw snap's start again. There you have it. I installed "chrome", not "chromium". I install nvidia driver directly from nvidia. I install "chrome" directly from Google. Both work without a burp in the barrel, for me. YMMV Ric -- My father, Victor Moore (Vic) used to say: "There are two Great Sins in the world... ..the Sin of Ignorance, and the Sin of Stupidity. Only the former may be overcome." R.I.P. Dad. http://linuxcounter.net/user/44256.html
Re: Another appeal about Flaky browsers
On Wed, Jul 27, 2016 at 05:50:36PM -0400, Ric Moore wrote: > On 07/27/2016 05:38 PM, Lisi Reisz wrote: > > >The rest of us aren't having the problem, so it must be something in Alan's > >personal set-up or config files. Having said which, I do find that Google > >Chrome is currently eating memory like there is no tomorrow, so is the > >problem shortage of memory? I know no one else on this E-list is having my problems, because otherwise the howls would be deafening. > Have you started it in "safe-mode"? Mo problems with it running sid and > chrome directly installed from google. Ric I have to call chromium from the command-line. I have just tried 'chromium -safe-mode &'. It runs fine for a while, but then the randaom 'Aw snap's start again. Here are the messages to stderr that have come up in the first five minutes(just a few of them!): (start) [8316:8316:0728/110824:ERROR:navigation_entry_screenshot_manager.cc(141)] Invalid entry with unique id: 11 [71:71:0728/110845:ERROR:PlatformKeyboardEvent.cpp(117)] Not implemented reached in static PlatformEvent::Modifiers blink::PlatformKeyboardEvent::getCurrentModifierState() [71:71:0728/110846:ERROR:PlatformKeyboardEvent.cpp(117)] Not implemented reached in static PlatformEvent::Modifiers blink::PlatformKeyboardEvent::getCurrentModifierState() [71:71:0728/110855:ERROR:PlatformKeyboardEvent.cpp(117)] Not implemented reached in static PlatformEvent::Modifiers blink::PlatformKeyboardEvent::getCurrentModifierState() [71:71:0728/110902:ERROR:PlatformKeyboardEvent.cpp(117)] Not implemented reached in static PlatformEvent::Modifiers blink::PlatformKeyboardEvent::getCurrentModifierState() [71:71:0728/110907:ERROR:PlatformKeyboardEvent.cpp(117)] Not implemented reached in static PlatformEvent::Modifiers blink::PlatformKeyboardEvent::getCurrentModifierState() [71:71:0728/110909:ERROR:PlatformKeyboardEvent.cpp(117)] Not implemented reached in static PlatformEvent::Modifiers blink::PlatformKeyboardEvent::getCurrentModifierState() [71:71:0728/110910:ERROR:PlatformKeyboardEvent.cpp(117)] Not implemented reached in static PlatformEvent::Modifiers blink::PlatformKeyboardEvent::getCurrentModifierState() [71:71:0728/110911:ERROR:PlatformKeyboardEvent.cpp(117)] Not implemented reached in static PlatformEvent::Modifiers blink::PlatformKeyboardEvent::getCurrentModifierState() [71:71:0728/110912:ERROR:PlatformKeyboardEvent.cpp(117)] Not implemented reached in static PlatformEvent::Modifiers blink::PlatformKeyboardEvent::getCurrentModifierState() [71:71:0728/110912:ERROR:PlatformKeyboardEvent.cpp(117)] Not implemented reached in static PlatformEvent::Modifiers blink::PlatformKeyboardEvent::getCurrentModifierState() Received signal 11 SEGV_MAPERR 77a08684 #0 0xb057a72a #1 0xafc29d28 ([vdso]+0xd27) #2 0xb1426899 #3 0xb169fb1d #4 0xb169fe8f #5 0xb16df58f #6 0xb16872a8 #7 0xb18717b0 #8 0xb18705e0 #9 0xb151a170 #10 0xb1404f96 #11 0xb1405311 #12 0xb2a7f4ce #13 0xb2a7ffb5 #14 0xb2a7db95 #15 0xb2a7d50a #16 0xb2a49cee #17 0xb2a4b160 #18 0xb2a4b2f0 #19 0xb5425cf1 #20 0xb237ec6e #21 0xb237e7ed #22 0xb237e3f3 #23 0xb237fac8 #24 0xb2371cb8 #25 0xb2371d2e #26 0xb237edbb #27 0xb22a9002 #28 0xb2a5133c #29 0xb22a91f8 #30 0xb22a922e #31 0xb257b69c #32 0xb257bf2d #33 0xb258ced0 #34 0xb57ddb07 #35 0xb57de099 #36 0xb57bf94b #37 0xb57c15ff #38 0xb57bd552 #39 0xb57bcb82 #40 0xb57c33df #41 0xb58049a6 #42 0xb5804d59 #43 0xb05f7f52 #44 0xb580b86f #45 0xb580a41f #46 0xb580d3b2 #47 0xb05f7f52 #48 0xb0599b9d #49 0xb0599fdf -(finish) Again: it would be nice to know: what log files tell the results of calls to a browser(e.g. opening/closing tabs etc) Or doesn't the system record browser activity? Re another suggestion that a responder made: I have found a directory, /home/alan/.config/chromium/Default/Session Storage which contains -rw--- 1 alan alan 33801 Jul 21 08:31 000185.ldb -rw--- 1 alan alan 21828 Jul 25 11:09 000197.ldb -rw--- 1 alan alan 34437 Jul 28 11:12 000199.log -rw--- 1 alan alan 16667 Jul 26 10:58 000200.ldb -rw--- 1 alan alan16 May 31 14:35 CURRENT -rw--- 1 alan alan 0 May 31 14:35 LOCK -rw--- 1 alan alan 272 Jul 28 11:07 LOG -rw--- 1 alan alan 272 Jul 28 08:24 LOG.old -rw--- 1 alan alan 6652 Jul 26 10:58 MANIFEST-01 (the output of ls -l) These '000..' files are reported by the file utility as 'data files'. Does anyone know what they are for? or how to read them? Thanks to all responders for sympathy and suggestions. Again: I'd like to
Re: Another appeal about Flaky browsers
On 2016-07-27 16:38, Lisi Reisz wrote: On Wednesday 27 July 2016 22:18:36 Felix Miata wrote: Alan McConnell composed on 2016-07-27 16:07 (UTC-0400): > I wrote about this a while ago, but have to repeat my appeal. > > Under jessie all the gui browsers I have tried(iceweasel and > chromium) crash continually, with messages "Well, this is embarrassing" > and "Aw, snap" continually appearing. This happened only rarely with > jessie's predecessor, wheezy. irc://moznet/%23firefox is where I would go to find a favorable resolution most quickly. Otherwise, goto the mozilla.org mailing lists or forums or to mozillazine.org. Maybe it does have to do with Jessie rather than Mozilla, but those places I'd expect to do better at identifying the root problem, especially if you do as Ric suggests and it doesn't help. The rest of us aren't having the problem, so it must be something in Alan's personal set-up or config files. Having said which, I do find that Google Chrome is currently eating memory like there is no tomorrow, so is the problem shortage of memory? Lisi I have never had the problem myself, but I am still using Debian Wheezy, since the last "upgrade" it also is using FireFox-esr, There were enough people having this problem, that they even have a thread on it at Mozilla, https://support.mozilla.org/en-US/questions/956252 and not just Debian. A startpage search gets quite a few results as well: https://lmsptfy.com/?q=FireFox-esr%20error%20Well%2C%20this%20is%20embarrassing%20and%20Aw%2C%20snap --
Re: Another appeal about Flaky browsers
On Wednesday 27 July 2016 23:01:20 Felix Miata wrote: > Lisi Reisz composed on 2016-07-27 22:38 (UTC+0100): > >> so is the problem shortage of memory? > > Memory shortage normally only produces slowdowns (due to swapping), not > crashing or failing even to start. So that is not Alan's problem. I am not having anything resembling his problems on either Chrome or Firefox on Jessie. :-/ And no-one else has reported having the same problems. So it seems to be personal to Alan. Lisi
Re: Another appeal about Flaky browsers
On Wednesday 27 July 2016 22:50:36 Ric Moore wrote: > On 07/27/2016 05:38 PM, Lisi Reisz wrote: > > The rest of us aren't having the problem, so it must be something in > > Alan's personal set-up or config files. Having said which, I do find > > that Google Chrome is currently eating memory like there is no tomorrow, > > so is the problem shortage of memory? > > Have you started it in "safe-mode"? Mo problems with it running sid and > chrome directly installed from google. Ric I'm on a back-up box, so am not terribly interested in any fine tuning. I just curse if need be!! Lisi
Re: Another appeal about Flaky browsers
Lisi Reisz composed on 2016-07-27 22:38 (UTC+0100): so is the problem shortage of memory? Memory shortage normally only produces slowdowns (due to swapping), not crashing or failing even to start. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: Another appeal about Flaky browsers
On 07/27/2016 05:38 PM, Lisi Reisz wrote: The rest of us aren't having the problem, so it must be something in Alan's personal set-up or config files. Having said which, I do find that Google Chrome is currently eating memory like there is no tomorrow, so is the problem shortage of memory? Have you started it in "safe-mode"? Mo problems with it running sid and chrome directly installed from google. Ric -- My father, Victor Moore (Vic) used to say: "There are two Great Sins in the world... ..the Sin of Ignorance, and the Sin of Stupidity. Only the former may be overcome." R.I.P. Dad. http://linuxcounter.net/user/44256.html
Re: Another appeal about Flaky browsers
On Wednesday 27 July 2016 22:18:36 Felix Miata wrote: > Alan McConnell composed on 2016-07-27 16:07 (UTC-0400): > > I wrote about this a while ago, but have to repeat my appeal. > > > > Under jessie all the gui browsers I have tried(iceweasel and > > chromium) crash continually, with messages "Well, this is embarrassing" > > and "Aw, snap" continually appearing. This happened only rarely with > > jessie's predecessor, wheezy. > > irc://moznet/%23firefox is where I would go to find a favorable resolution > most quickly. Otherwise, goto the mozilla.org mailing lists or forums or to > mozillazine.org. Maybe it does have to do with Jessie rather than Mozilla, > but those places I'd expect to do better at identifying the root problem, > especially if you do as Ric suggests and it doesn't help. The rest of us aren't having the problem, so it must be something in Alan's personal set-up or config files. Having said which, I do find that Google Chrome is currently eating memory like there is no tomorrow, so is the problem shortage of memory? Lisi
Re: Another appeal about Flaky browsers
Alan McConnell composed on 2016-07-27 16:07 (UTC-0400): I wrote about this a while ago, but have to repeat my appeal. Under jessie all the gui browsers I have tried(iceweasel and chromium) crash continually, with messages "Well, this is embarrassing" and "Aw, snap" continually appearing. This happened only rarely with jessie's predecessor, wheezy. irc://moznet/%23firefox is where I would go to find a favorable resolution most quickly. Otherwise, goto the mozilla.org mailing lists or forums or to mozillazine.org. Maybe it does have to do with Jessie rather than Mozilla, but those places I'd expect to do better at identifying the root problem, especially if you do as Ric suggests and it doesn't help. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: Another appeal about Flaky browsers
On 07/27/2016 04:07 PM, Alan McConnell wrote: Alan, whose animus against Debian is increasing hourly because of the wretched failures of the jessie installation Got a big harddrive?? Could you create another partition and install Jessie clean to it? You might have some cruft left over from wheezy in the way of config files, /etc. After all, the giant leap from wheezy to jessie is relatively huge. Mine blew up to hell and gone. Yet a fresh install worked smooth as butter. I mounted the first partition to /opt and copied JUST personal files over and was happy as a little clam. I'm rid of the entire upgrade business after installing sid, ~cleanly~. I don't need strong drink anymore. Ric -- My father, Victor Moore (Vic) used to say: "There are two Great Sins in the world... ..the Sin of Ignorance, and the Sin of Stupidity. Only the former may be overcome." R.I.P. Dad. http://linuxcounter.net/user/44256.html
Re: Another appeal about Flaky browsers
On Wed, Jul 27, 2016 at 04:07:55PM -0400, Alan McConnell wrote: > I wrote about this a while ago, but have to repeat my appeal. > > Under jessie all the gui browsers I have tried(iceweasel and > chromium) crash continually, with messages "Well, this is embarrassing" > and "Aw, snap" continually appearing. This happened only rarely with > jessie's predecessor, wheezy. Alan, if I recall correctly, someone suggested the Pale Moon browser. Because I was unhappy with firefox, I did just that. Pale Moon provides all the functionality I need, and it has not crashed since installed some time ago. What has been your luck with it? Haines Brown
