[Bug 1602910] Re: firefox-trunk: Bad news first: This tab has crashed Now for the good news: You can just close this tab, restore it or restore all your crashed tabs.

2018-08-26 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1602910] Re: firefox-trunk: Bad news first: This tab has crashed Now for the good news: You can just close this tab, restore it or restore all your crashed tabs.

2018-06-27 Thread Paul White
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed

[Bug 1602910] Re: firefox-trunk: Bad news first: This tab has crashed Now for the good news: You can just close this tab, restore it or restore all your crashed tabs.

2017-01-17 Thread daniel CURTIS
Hello. I've had the same message/error today. It seems, that the "plugin-container" profile was responsible (which, I created today). But, there was not any entries in the log files such as `/var/log/kern.log` or `/var/log/syslog`. Everything was OK: for example putting profile in the "enforce"

[Bug 1602910] Re: firefox-trunk: Bad news first: This tab has crashed Now for the good news: You can just close this tab, restore it or restore all your crashed tabs.

2016-07-13 Thread ncv
Looks like this call generate the problem: 0x7fffec8cc3dd <+45>:callq 0x7fffec7c2230 Assembly snippet: Dump of assembler code for function InvokeInterruptCallback(JSContext*): 0x7fffec8cc3b0 <+0>: push %rbp