Tallefer / qtweb

Automatically exported from code.google.com/p/qtweb
0 stars 0 forks source link

QtWeb 3.8.4 (build 104) crashes on site load #185

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Connect to https://perseus.ipma.pt/

What is the expected output? What do you see instead?
Expect login page to load. I see a Windows crash message.

What version of the product are you using? On what operating system?
QtWeb 3.8.4 (build 104) under Windows XP x86 SP3 en_us

Please provide any additional information below.
This is a regression from version 3.7.5 (build 101)

Original issue reported on code.google.com by pedl...@gmail.com on 29 Jul 2013 at 9:59

GoogleCodeExporter commented 9 years ago
I've seen similar issues in 3.8.4 under WinXP SP3.

The issue here appears to be the URL format.  Enter google.com in the URL and 
press enter, and QtWeb dies horribly with a Windows error box.  Enter 
http://www.google.com. and it works.  (The link for Mozilla in the bookmarks 
bar also makes QtWeb crash.  The others work.) 

Original comment by dennis.m...@gmail.com on 3 Aug 2013 at 3:04

GoogleCodeExporter commented 9 years ago
This could be the same as issue 186.

Original comment by mcat....@gmail.com on 6 Aug 2013 at 1:13

GoogleCodeExporter commented 9 years ago
Seems unlikely.  Flash is always a problem, and consistent top crasher for 
Firefox.  What I saw happened simply trying to open a URL in what is supposed 
to be a supported format. 

I also tried QtWeb under Ubuntu 11.10, and it died shortly after launch with an 
illegal instruction error. 

If I get a chance, I'll try again under Ubuntu and try to reproduce the issue.

I looked at QtWeb in the first place because I have a *very* low end machine - 
867mhz Transmeta Crusoe CPU, 40GB IDE4 HD, 256MB RAM (which the CPU grabs 16MB 
of for code morphing).  I don't even try to run a current Firefox or Chrome 
build on it - too little RAM and too slow.  If it were more robust, QtWeb might 
be a good candidate for a reasonably standards compliant browser that would run 
acceptably on the hardware, but it's nowhere near ready for prime time.

Original comment by dennis.m...@gmail.com on 6 Aug 2013 at 1:57

GoogleCodeExporter commented 9 years ago
This bug is fixed in version 3.8.5 (build 108).
Thanks!

Original comment by pedl...@gmail.com on 12 Sep 2013 at 11:11

GoogleCodeExporter commented 9 years ago

Original comment by magis...@gmail.com on 13 Sep 2013 at 2:53