See url. Go to the bottom of the page where there isn't any text anymore in table cells. Select a few lines of those table cells and the do a 'View Selection Source' in the context menu. Actual result: Firefox consumes > 500MB of memory (I had a case of >1.5GB, but I'm afraid of finishing the view selection source process, because with that memory usage, it brings my system to a crawl). Expected result: Firefox consuming < 500MB of memory, preferably, it should just use a few extra MB's. It seems that Firefox126.96.36.199 isn't that memory hungry when doing the steps to reproduce, it 'just' uses something like 200-300MB.
Created attachment 250167 [details] Page in question, zipped The page in question, attached to the bug, in case the url disappears.
Created attachment 251642 [details] Another page in question, zipped Another page, where I got this issue. This time it's just a large amount of text in the page and the doing "View Selection Source" on some part of it.
(In reply to comment #0) >... > Actual result: > It seems that Firefox188.8.131.52 isn't that memory hungry when doing the steps to > reproduce, it 'just' uses something like 200-300MB. 184.108.40.206 compared to __? This essentially loops/hangs for me. I selected the first couple lines, pick view selection and after several minutes I get "unresponsive script and I can't break out after selecting "stop script". VM size is at 1.5meg and cpu 95% maybe one of these? http://tinyurl.com/y88jb5
Severity: major → critical
Keywords: hang, perf
Summary: View selection source consumes large amounts of memory on this page → View Selection Source consumes large amounts of memory and loops
Version: unspecified → Trunk
http://www.theyworkforyou.com/lords/?id=2006-10-17b.651.0&s=speaker%3A12913#g721.0 Selecting text from before this div until a little way into it, then viewing selection source, causes very high memory and CPU usage. In addition, after a while (something like 20 seconds, I haven't measured it) a dialogue box pops up saying there is a misbehaving script and would I like to kill it. Clicking on "Stop script" has no effect (beyond closing the window, and even that takes a long time) and further boxes appear if I wait. Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:220.127.116.11) Gecko/20061208 Firefox/18.104.22.168 Also on the latest nightly build, will reply with its UA in a moment.
Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9a2pre) Gecko/20070128 Minefield/3.0a2pre
This bug (or a related one) affects ordinary pages as well, although to a lesser extent. On the web application I am developing, if you view selection source on the whole page and then try to scroll down more than 1 page, then FF hangs for 10-15 seconds (I mean hangs all windows, no UI response etc.) Just confirming that this does happen to a lot of page.
3.1 might be better, but still high impact on the huge testcase URL http://www.bkn.go.id/honorerhapus.htm Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b2) Gecko/20081125 Firefox/3.1b2
Summary: View Selection Source consumes large amounts of memory and loops → View Selection Source consumes large amounts of memory and loops with high cpu
Testcase2 of bug 416052 ( https://bugzilla.mozilla.org/attachment.cgi?id=301807 ) also seems to exhibit this problem.
bz, is there a core bug this view source bug should depend on?
I have no idea. What's the actual JS running here? Is it just being totally stupid in some way, or is it doing things that should be reasonable?
That said, if someone can give me spefic steps to reproduce (e.g. on that page from comment 0, should I just be selecting some of the garbage text below he table?) I can try to at least profile...
Here's a question. Is the memory usage much different from the memory usage if you view the source of that frame?
bz, using v3.6 memory usage is about double that of a straight out, simply view source. using attachment 250167 [details] 1. scroll to bottom of page 2. click scrollbar to go back(up) ~8 screens 3. select from there down to bottom 4. view selection source however, high cpu is short lived, and memory not terrible - nothing debilitating to UI. memory varies 100-200mb. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2b1pre) Gecko/20090928 Namoroka/3.6b1pre Martijn, is it better/worse with a newer version?
Memory usage more than normal view source + size of actual page (since view selection source sticks all that stuff into a data: URI) is not quite expected, but not likely to be an obvious core bug; more likely to be a bug in the way view selection source builds up its huge string. If cpu is not a problem, there's no point profiling.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → WORKSFORME
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
You need to log in before you can comment on or make changes to this bug.