Results 21 to 23 of 23
-
06-13-2009, 02:10 PM #21
I've been opening in a terminal with the command firefox - g . This leaves a record of the crash. I had one yesterday which was a freeze up and left more than I can put in a post.
This morning my browser crashed three times in an hour and each time the terminal readout was Segmentation fault . On the last crash a window popped up asking me to send a report to [email protected]. It read, "The application Plasma Workspace (plasma) crashed and caused the signal 11 (SIGSEGV)"
Any thoughts ?Be careful how you treat people on your way up, you may meet them again on your way back down.
-
06-13-2009, 02:19 PM #22
- Join Date
- Mar 2008
- Location
- Berlin
- Posts
- 3,490
Thanked: 1903Two: Plasma is broken, or your RAM is.
- Switch to Gnome for a change, and see if the problem persists.
- Before you go to bed, boot into memtest86+, and let it run.
Good luck.
-
The Following User Says Thank You to BeBerlin For This Useful Post:
JimmyHAD (06-13-2009)
-
06-13-2009, 02:52 PM #23
definitely memory related, not to over simplify but it is an allocation issue firefox is trying to access memory it believes is free but the pointer has it allocated and possibly in use else where
a couple of suggestion if you do a google search for firefox segmentation fault but as you mentioned you are running kubuntu here is how one kubuntu user solved it Firefox Segmentation fault - Ubuntu Forums
other basic suggestions is to try loading FF without any add ons as well, and updating flash to newest version
and finally if you have an ASUS Eee pc this may help Firefox Segmentation fault - Ubuntu Forums
-
The Following User Says Thank You to crankymoose For This Useful Post:
JimmyHAD (06-13-2009)