Bug 340077

Summary:	Crash when maneuvering in google streetview
Product:	[Applications] konqueror	Reporter:	John Hunter <jmdh01>
Component:	general	Assignee:	Konqueror Bugs <konqueror-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	NOR
Version First Reported In:	4.13.3
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
URL:	https://maps.google.co.uk/maps?hl=en-GB&q=wallingford&gbv=2&ie=UTF-8&ei=5JFBVLq5F7SQ7AbF_4DgDQ&ved=0CAkQ_AU&output=classic&dg=brw
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description John Hunter 2014-10-17 23:17:25 UTC

I was moving along a road (proceding north up Reading Road, Wallingford) in Google streetview. After about 400m of progress up the road in roughly 30m steps, konqueror crashed with a request that I should report this bug.  It could be in a Google plugin? The machine was using 1.7GB ram out of a possible 6GB.

Reproducible: Sometimes

Steps to Reproduce:
1. Go to www.google.co.uk
2. Search for "Wallingford, United Kingdom"
3. Click on "Maps" - "Satellite"
4. Zoom in; click on the southern end of "Reading Road" near to the roundabout to enter streetview.
5. Progress up the road in 25m/30m steps
6. I have tried twice to reproduce the crash without achieving it

Actual Results:  
After the first time, konqueror crashed as describrd above

Expected Results:  
It should not have crashed

Generally, Konqueror handles Google Streetview far better than Firefox; however random crashes are very annoying, resulting in loss of train of thought.

The only information supplied is:
Executable: konqueror PID: 4814 Signal: Segmentation fault (11) Time: 17/10/2014 22:41:39

Distro: Netruner 14
Kernel: 3.13.0-37-generic (32-bit)
KDE libs: 4.13.3
Qt: 4.8.6
Processor: Intel Core i5-2320 3GHz
RAM: 6 GB
Screen: 1680x1050 (60Hz)

Comment 1 Tommi Tervo 2014-10-18 08:47:41 UTC

Just a suggestion, you should use 64bit linux distribution. 32bit kernel has 2GB/process limit.

Comment 2 Andrew Crouthamel 2018-11-12 02:55:17 UTC

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!

Comment 3 John Hunter 2018-11-12 22:35:14 UTC

Tommi Tervo is most probably right: it was almost certainly brought about by the 2GB limit. Many s/w quirks with 32 bit systems disappeared when I changed to 64 bit Linux.