Bug 10687

Summary:	Chromium-browser is too unstable
Product:	Mageia	Reporter:	Marek Laane <qiilaq69>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal
Version:	Cauldron
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Marek Laane 2013-07-03 18:26:41 CEST

Description of problem: It's little bit hard to describe the bug but in essence it is: Chromium's last versions have some serious performance problems: it is very, really often I have "oops, couldn't display" message (e.g. just opened the browser and from 29 tabs 8 wouldn't open correctly but with the error message). I know, of course, that I've maybe too many tabs open (mostly about 40), including some automatically refreshing (like Facebook or Feedly) but the last version which worked without problems was Chromium 26 form Tainted repository. Both 27 and 28 (from Core) have mentioned display/performance problem - which I could resolve going back to 26-tainted but I rather would see Chromium from Core working without problems, too.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:

Comment 1 David Walser 2013-07-08 16:27:39 CEST

Unless there's something Mageia specifically can do about this, it would be better to report this upstream.

Comment 2 Marek Laane 2013-07-08 16:49:43 CEST

I can't say it definitely but I have now used some days Google Chrome and it does not show any such problem. So I rather think it may be something about Mageia that causes instability in Chromium but am not sure, of course.

Comment 3 Manuel Hiebel 2013-07-12 18:21:27 CEST

and wi

Severity: critical => normal

Comment 4 David Walser 2014-01-28 17:02:15 CET

Without any more specifics, there's really nothing we can do.  Also, the package has been updated several times since.  Please open a new bug if you have a more specific problem with the newer packages (and if it's definitely a Mageia-specific problem).

Status: NEW => RESOLVED
Resolution: (none) => OLD