Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Learn More

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Firefox crashes

  • 3 antwurd
  • 1 hat dit probleem
  • 1 werjefte
  • Lêste antwurd fan kn88

more options

(process:11411): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed this is what i see in terminal when my browser crashes. I am using Peppermint 5 OS. My computer is an intel atom d2550 with intel graphics media accelerator 3600 series i have 2 Giga RAm and it is a dual core 1,8 processor. But even my chromium crashes.

(process:11411): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed this is what i see in terminal when my browser crashes. I am using Peppermint 5 OS. My computer is an intel atom d2550 with intel graphics media accelerator 3600 series i have 2 Giga RAm and it is a dual core 1,8 processor. But even my chromium crashes.

Alle antwurden (3)

more options

Please update to Firefox 31, Update Firefox to the latest release and then, if you still crash, hit us up again :)

more options

Make sure that all drivers and other programs that are part of the System Requirements on Linux are the latest versions.

more options

Well, I don't know why but now it is worse .... I hate the whole thing. I think it happens when i am searching for torrent files, and when I am using YouTube, but not every time.... but when it starts it's like 4-5 times. I try to open Firefox, it crashes, and again and again ... after a while it stops.... I have tried in this two days at least 10 different Linuxes and it was shit everywhere... and it is not my rams fault I have checked with memtest it is fine. But chromium also crashes, at totally different points. And in Firefox I did not download any extensions. I have tried to turn of the hardware accelerator.... no changes. But I read that this is a bug ... so when will it be solved?