Bug 3988

Summary: Iceape getting frozen for more than 30 seconds on 50% of webpages
Product: Mageia Reporter: Jaromír Cápík <tavvva>
Component: RPM PackagesAssignee: Christiaan Welvaart <cjw>
Status: RESOLVED WONTFIX QA Contact:
Severity: major    
Priority: Normal CC: mageia, marja11
Version: Cauldron   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: iceape-2.6.1-1.mga2.src.rpm CVE:
Status comment:

Description Jaromír Cápík 2012-01-01 13:02:40 CET
Description of problem:
Iceape getting frozen for more than 30 seconds on 50% of visited webpages. Then after the mentioned timeout everything works well ... the mouse and keyboard input starts to react and the application window starts redrawing again. If I enter a different webpage, the same usually happens again (it's more than 50% of cases ... I'm not sure about the percentage ... it probably depends on the page content). Firefox doesn't seem to suffer these issues.

Version-Release number of selected component (if applicable):
2.6.1-1.mga2

How reproducible:
approx. 50% of cases
Comment 1 Jaromír Cápík 2012-01-01 14:25:55 CET
I just disabled Shockwave Flash plugin and the problem disappeared ... it's strange, that Firefox doesn't suffer such issue.
Comment 2 Jaromír Cápík 2012-01-01 14:35:30 CET
I tried several plugin versions [10.0 r42 - 11.1 r102] (which all worked well with seamonkey) and all of them make iceape frozen ...
Comment 3 Manuel Hiebel 2012-01-01 16:09:52 CET
You should more open a bug at adobe or http://www.seamonkey-project.org/community#bugreport, if you are sure it's the flash player.
Comment 4 Jaromír Cápík 2012-01-02 21:15:41 CET
No ... I believe it's an iceape bug, since all tested versions of the flash plugin worked well with previous Seamonkey versions. Moreover recent Firefox has absolutely no problems with the flash plugin.
Comment 5 Manuel Hiebel 2012-01-03 06:31:50 CET
ok but iceape is seamonkey, and we are not upstream
Comment 6 Jaromír Cápík 2012-01-03 19:13:34 CET
I know, that Iceape is Seamonkey :) I was just trying to say, that the Iceape maintainer from the Mageia team should try to search for available patches, check if newer version is available or forward the issue to upstream. This bug can be understood as something for tracking purposes if the issue is really "UPSTREAM".
Comment 7 Martin Whitaker 2012-01-16 23:28:23 CET
I have just encountered this bug whilst testing Mageia2 alpha 3. Note that the SeaMonkey 2.6.1 x86_64 binary you can download from www.seamonkey-project.org does not suffer from this bug, so it is a problem with the Mageia build.

Note this problem is easy to reproduce - just visit http://www.adobe.com/software/flash/about/ with the flash plugin enabled.

CC: (none) => mageia

Comment 8 Marja Van Waes 2012-02-24 17:52:33 CET
(In reply to comment #7)
> I have just encountered this bug whilst testing Mageia2 alpha 3. Note that the
> SeaMonkey 2.6.1 x86_64 binary you can download from www.seamonkey-project.org
> does not suffer from this bug, so it is a problem with the Mageia build.
> 
> Note this problem is easy to reproduce - just visit
> http://www.adobe.com/software/flash/about/ with the flash plugin enabled.

assigning to maintainer

CC: (none) => marja11
Assignee: bugsquad => cjw

Comment 9 Manuel Hiebel 2012-05-02 00:17:15 CEST
iceape was removed from the repo

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