MantisBT - NetSurf |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0002344 | NetSurf | [All Projects] General | public | 2015-08-11 20:36 | 2016-02-16 15:26 |
|
Reporter | Dave Higton | |
---|
Assigned To | kinnison | |
---|
Priority | normal | Severity | crash | Reproducibility | always |
---|
Status | closed | Resolution | fixed | |
---|
Platform | Iyonix | OS | RISC OS | OS Version | 5.22 (13-Apr-15) |
---|
Product Version | 3.4 | |
---|
Target Version | 3.4 | Fixed in Version | 3.4 | |
---|
Fixed in CI build # | 2911 |
---|
Reported in CI build # | 2874 |
---|
URL of problem page | http://www.bbc.co.uk/sport/0/athletics/33867962 |
---|
|
Summary | 0002344: Page causes Netsurf to silently evaporate |
---|
Description | After a few seconds trying to open this URL, Netsurf disappears without a crash dump. |
---|
Steps To Reproduce | Just go to http://www.bbc.co.uk/sport/0/athletics/33867962 |
---|
Additional Information | OK up to CI 2783, fails in 2874, 2875, 2876 and 2882 (I don't have the others in between to test, and 2882 is the latest as I write). |
---|
Tags | No tags attached. |
---|
Relationships | |
Attached Files | NSlog.zip (7,298) 2015-08-12 11:39 https://bugs.netsurf-browser.org/mantis/file_download.php?file_id=307&type=bug
NSlog2.zip (15,286) 2015-08-12 15:55 https://bugs.netsurf-browser.org/mantis/file_download.php?file_id=308&type=bug |
---|
Notes |
|
|
Although I reported the issue using 2874, it failed on attempting to view the report in Mantis. 2873 works, though (and I'm typing this with it). |
|
|
(0000891)
|
David Pitt
|
2015-08-12 11:40
(Last edited: 2015-08-12 11:44) |
|
This appears to be a JavaScript issue. At tested with NetSurf 0002891, NetSurf now starts up with JavaScript enabled irrespective of what Choices may have been saved in the previous session. Disable JavaScript and the site renders.
P.S. I got a crash dump which I have uploaded.
|
|
|
|
I currently can't get it to evaporate on that page for me, but I did find and fix a node leak with it, thank you.
I'll keep you informed when we get ready to disable the force-on of JS. |
|
|
|
|
|
|
Do you mean the browser died, or just that there was a 'JAVASCRIPT WENT BANG' log entry? |
|
|
|
The browser does die and produces the log. |
|
|
|
Now on #2897, I see JS logging has been expanded, a second log has been uploaded. |
|
|
|
The second log is for version 0002892 and contains no extra logging. |
|
|
|
|
|
|
|
|
|
Confirmed resolved in 3.4 release |
|