Bug 131489 - [EFL] WebKit eats a huge amount of memory with large fonts
Summary: [EFL] WebKit eats a huge amount of memory with large fonts
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Linux
: P1 Major
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks: 116980
  Show dependency treegraph
 
Reported: 2014-04-10 04:25 PDT by Renata Hodovan
Modified: 2017-03-11 10:34 PST (History)
6 users (show)

See Also:


Attachments
Test case (66 bytes, text/html)
2014-04-10 04:25 PDT, Renata Hodovan
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Renata Hodovan 2014-04-10 04:25:26 PDT
Created attachment 229042 [details]
Test case

WebKit eats a huge amount of memory if we are trying to load texts with really large font-size. E.g.: the following test uses all the 8G of my memory and the only solution to kill the browser is a complete PC reboot:


<style type="text/css">
		
	* {
	font-size:5388%;

	}
	
</style>
A

I've run the test on release and debug EFL builds, but I'm not sure that it is a port specific issue or not. It would be great if someone could validate it on other ports too.
Comment 1 Csaba Osztrogonác 2014-04-10 07:36:08 PDT
I tried it with Safari and ToT WebKit, it managed 
to paint the huge "A" properly without any problem.
Comment 2 Renata Hodovan 2014-04-10 08:41:33 PDT
(In reply to comment #1)
> I tried it with Safari and ToT WebKit, it managed 
> to paint the huge "A" properly without any problem.

Thanks Ossy. Could someone try it on a GTK build too?
Comment 3 Renata Hodovan 2014-04-17 02:01:46 PDT
I guess this bug and the time-out at fast/css/font-size-nan.svg happen for the same reason.
Comment 4 Renata Hodovan 2014-04-18 06:58:48 PDT
I've tried the test on a GTK build and it works fine.
Comment 5 Michael Catanzaro 2017-03-11 10:34:20 PST
Closing this bug because the EFL port has been removed from trunk.

If you feel this bug applies to a different upstream WebKit port and was closed in error, please either update the title and reopen the bug, or leave a comment to request this.