| Summary: | Segmentation fault in KJS::allocateBlock | ||
|---|---|---|---|
| Product: | [Applications] konqueror | Reporter: | Graeme Hewson <bugs> |
| Component: | general | Assignee: | Konqueror Bugs <konqueror-bugs-null> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | crash | CC: | bugs |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 4.13.2 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Graeme Hewson
2014-07-25 07:39:25 UTC
To reproduce a similar problem: 1. Start Konqueror through Kickoff or an icon, or from Konsole with "kfmclient openProfile webbrowsing". 2. Go to http://tfl.gov.uk/oyster - this currently redirects to http://tfl.gov.uk/fares-and-payments/oyster?cid=fs076 3. Crash occurs at this point (maybe helped by moving the mouse). The crash doesn't occur if Konqueror is started from Konsole with "/usr/bin/konqueror". I say it's a similar problem because the Crash Reporting Assistant says debug symbols are missing. If I click on "Install Debug Symbols", it goes through the motions of installing the symbols, but I'm not asked for my password and they're not installed. There's no way I can see of determining which symbols are missing. If I go directly to http://tfl.gov.uk/fares-and-payments/oyster?cid=fs076 after starting Konqueror, the Crash Reporting Assistant isn't invoked, and the browser simply quits with no message. Created attachment 88063 [details] New crash information added by DrKonqi konqueror (4.13.2) on KDE Platform 4.13.2 using Qt 4.8.6 - What I was doing when the application crashed: In bash session: $ ulimit -v 850000 $ konqueror http://lwn.net Browse for a while. -- Backtrace (Reduced): #6 memset () at ../sysdeps/x86_64/memset.S:78 #7 0x00007fd27fb1104a in memset (__len=65536, __ch=0, __dest=0x0) at /usr/include/x86_64-linux-gnu/bits/string3.h:84 #8 KJS::allocateBlock () at ../../kjs/collector.cpp:209 #9 0x00007fd27fb11b91 in KJS::Collector::allocate (s=s@entry=64) at ../../kjs/collector.cpp:361 #10 0x00007fd27fb41535 in KJS::JSCell::operator new (size=size@entry=64) at ../../kjs/value.cpp:41 I'm not sure exactly what happened before my original report, but I had a Konsole session with a limited amount of virtual memory (through ulimit). I think the limit was somehow applied to all Konqueror sessions. Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! It's possible to induce a crash in Konqueror 5.0.97 when storage is limited, but I don't know if it's the same problem as reported above. $ ulimit -v 1500000 $ konqueror http://lwn.net KonqFrame(0x55bdbb41ee70) QObject(0x0) mmap() failed: Cannot allocate memory mmap() failed: Cannot allocate memory Received signal 11 SEGV_MAPERR 000000000000 LLVM ERROR: out of memory Received signal 6 |