Summary: | OOM and crash viewing CSS3 animation page | ||
---|---|---|---|
Product: | [Unmaintained] rekonq | Reporter: | skierpage <skierpage> |
Component: | general | Assignee: | Andrea Diamantini <adjam7> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | 0.8.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
skierpage
2012-01-04 10:26:04 UTC
*** This bug has been marked as a duplicate of bug 289261 *** It seems it only crashes if I limit memory, I normally set `ulimit -v 1536000` to guard against out-of-control browser memory consumption. This CSS page consumed enough virtual memory to trigger the crash. With `ulimit -v unlimited`, it doesn't crash and animates quite well, but rekonq's memory consumption with only the one tab open is extremely high, VSZ at 1.6 GB whereas Firefox is only 0.6 GB rendering the same page. Andrea Diamantini made this a dupe of another FastMalloc crash in *Konqueror*. It's unclear if that crash is related to running out of memory. Maybe the crash here is due to poor OOM handling in wtf/FastMalloc.cpp, but maybe by design FastMalloc crashes on OOM, and the real issue is excessive memory consumption in CSS parsing. So I left this a dupe and filed a separate bug 290583 about the high virtual memory consumption. I set that to be a dupe of konqueror bug because they have the same bt and the issue described here is obviously a qtwebkit one. But when testing against qtwebkit 2.2 I noticed everything works well with both browsers against the reported page. Didn't have yet info about memory limit. Testing and replying in bug 290583 you created and eventually reporting it upstream. |