Shervin Emami wrote, On 2013-07-15 00:25: > Unfortunately I need Skype, VirtualBox, Oracle JDK and NVIDIA CUDA Toolkit, > I need those many times each day for my work as a remote developer. I'd > love to get rid of Flash, so just now I switched YouTube to use WebM > instead (go to "http://www.youtube.com/html5";) as a start. But when I > experience browser crashes, it's not while doing anything strange like > watching youtube so I don't think Flash is my problem. Maybe when Dolphin > or Plasma or Iceweasel crash it really is a problem with my RAM hardware (I > put 16GB RAM in my laptop since i often build Android from source and often > use WinXP through VirtualBox), possibly related to the fact I use 5GB of > RAM as a ramdisk where I do lots of my temp stuff in. First option is since you've already got VirtualBox setup, setup a VM for Skype and other tricky software. Flash is EVERYWHERE, no joke. When you're running your web browser, open up a terminal window and run top (or better yet htop) and sort by CPU usage. You'll see Flash pop up a bunch, not just YouTube vids. There are some great plugins that'll ask you before starting up any Flash content, might be worth checking out. If you want to test your ram, apt-get install memtest86+, reboot, select it in GRUB, and let that thing run over night. > For the repeatable bugs I found in Kate & Inkscape, you guys convinced me I > should file the bug reports and then find ways to live around the bugs for > the near future. I sent a message to this group recently about the Kate > crash because I wasn't sure how to report it, but no-one replied: " > http://lists.debian.org/debian-kde/2013/06/msg00014.html";. For the Inkscape > crash i tested it on Mint KDE 14, Mint KDE 13 and ArchLinux and none of > those crashed, only Debian Stable, and only while using OpenGL as the KWin > renderer (ie: it doesn't crash while using XRender), so I'm also a bit > confused about whether to file a bug to Debian or to Inkscape, since it > seems to have been fixed in recent versions of Inkscape. Unless told specifically to do so by a project community, file bugs in a tracker over sending an issue to a mailing list. Mailing lists are good for disucssing current thing, bug trackers are good for recording a history and it's eventually resolution (or ignorance). Unless you want to ask a community if you shouldn't file a bug (never ask if you should, because you'll fall into that no one will reply trap). -- Rubin rubin@starset.net
Attachment:
signature.asc
Description: OpenPGP digital signature