WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED CONFIGURATION CHANGED
26417
Reproducible crash navigating away from pseudo-HTML page
https://bugs.webkit.org/show_bug.cgi?id=26417
Summary
Reproducible crash navigating away from pseudo-HTML page
Tobias Nopper
Reported
2009-06-15 14:58:20 PDT
WebKit (and current Safari) reproducably crashes when opening the (pseudo)-HTML site
http://share.tobias-nopper.de/1mb.html
Most of the times, WebKit crashes instantly, yet sometimes it takes a click on the reload button to crash. Crash report attached. Works for Safari 4.0 (5530.17) on Intel Mac 10.5.7 WebKit (5530.17,
r44680
) on Intel Mac 10.5.7 Safari 4.0 (530.17) on Windows XP SP2 WebKit (530.17,
r44680
) on Windows XP SP2 Mobile Safari 3.0 (iPhone OS 3.0 (7A341 Gold Master) Note: The linked website was initiaty created to check whether my iPhone was connected thru a compressing proxy over EDGE. If any other information is needed, please tell me so.
Attachments
(please ignore)
(3.70 KB, text/plain)
2009-06-15 14:59 PDT
,
Tobias Nopper
no flags
Details
crash log
(67.70 KB, text/plain)
2009-06-15 15:04 PDT
,
Tobias Nopper
no flags
Details
Show Obsolete
(1)
View All
Add attachment
proposed patch, testcase, etc.
Tobias Nopper
Comment 1
2009-06-15 14:59:04 PDT
Created
attachment 31306
[details]
(please ignore)
Tobias Nopper
Comment 2
2009-06-15 15:04:09 PDT
Created
attachment 31308
[details]
crash log
Mark Rowe (bdash)
Comment 3
2009-06-15 18:51:56 PDT
Blowing the stack below Element::detach.
Mark Rowe (bdash)
Comment 4
2009-06-15 18:52:08 PDT
<
rdar://problem/6974991
>
Ahmad Saleem
Comment 5
2022-09-01 04:15:42 PDT
We don't have reduction because the test case URL is 404 and I tried the Wayback Archive and it is also 404 and tried even :80 trick in Wayback but didn't work. So we don't have any test case to reproduce this. I am going to tag some Webkit folks, just so if they can analysis something from the crash log or if needed mark this appropriately. Thanks!
Alexey Proskuryakov
Comment 6
2022-09-01 10:29:48 PDT
This was likely some case of very deep nesting, I'd expect us to have nesting depth limits that prevent it now.
Tobias Nopper
Comment 7
2022-09-02 13:33:32 PDT
Hey, blast from the past. ;-) Sorry, I didn't expect anybody to be interested in this 13 year old bug anymore. I did now re-upload the then-faulty HTML file, which simply consists of loads of non-sensical HTML tags. You can check it out at the URL that I posted in the original bug report. Indeed, the bug is now gone, probably has been for many, many years now. :-) Greetings, Tobias Nopper
Alexey Proskuryakov
Comment 8
2022-09-02 18:23:55 PDT
Thank you, it feels good to confirm that it's gone.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug