As you might have noticed, the WebSocket tests are crashing on Leopard and Snow Leopard. I thought for a while that this might be related to my recent move of the WebSocket tests, but looks unrelated. The crashes started with a patch that flipped off the SVN executable bit for a bunch of files, which also seems unrelated (reverting that change locally also don't seem to make a difference). Here's a reduced test case: <script> var ws = new WebSocket('ws://localhost:1111/'); </script> Just open a local HTML file containing that code and you'll crash WebKit on Snow Leopard (and presumably Leopard as well). The crash looks like some kind of heap corruption. At this point, I'd like to hand this off to someone who's more familiar with the WebSockets code. Any volunteers? Thanks, Adam
On Oct 4, 2010, at 2:33 PM, Adam Barth wrote:
As you might have noticed, the WebSocket tests are crashing on Leopard and Snow Leopard. I thought for a while that this might be related to my recent move of the WebSocket tests, but looks unrelated. The crashes started with a patch that flipped off the SVN executable bit for a bunch of files, which also seems unrelated (reverting that change locally also don't seem to make a difference).
Here's a reduced test case:
<script> var ws = new WebSocket('ws://localhost:1111/'); </script>
Just open a local HTML file containing that code and you'll crash WebKit on Snow Leopard (and presumably Leopard as well). The crash looks like some kind of heap corruption. At this point, I'd like to hand this off to someone who's more familiar with the WebSockets code. Any volunteers?
<https://bugs.webkit.org/show_bug.cgi?id=47136> People with C++ and x86 assembly skills are encouraged to help out. Simon
On Oct 4, 2010, at 5:30 PM, Simon Fraser wrote:
On Oct 4, 2010, at 2:33 PM, Adam Barth wrote:
As you might have noticed, the WebSocket tests are crashing on Leopard and Snow Leopard. I thought for a while that this might be related to my recent move of the WebSocket tests, but looks unrelated. The crashes started with a patch that flipped off the SVN executable bit for a bunch of files, which also seems unrelated (reverting that change locally also don't seem to make a difference).
Here's a reduced test case:
<script> var ws = new WebSocket('ws://localhost:1111/'); </script>
Just open a local HTML file containing that code and you'll crash WebKit on Snow Leopard (and presumably Leopard as well). The crash looks like some kind of heap corruption. At this point, I'd like to hand this off to someone who's more familiar with the WebSockets code. Any volunteers?
<https://bugs.webkit.org/show_bug.cgi?id=47136>
People with C++ and x86 assembly skills are encouraged to help out.
The Xcode project was picking up qt/SocketStreamHandle.h in error. Fixed in http://trac.webkit.org/changeset/69057 You may have to quit and restart Xcode to have it build with the correct header. Simon
On Mon, Oct 4, 2010 at 6:24 PM, Simon Fraser <simon.fraser@apple.com> wrote:
On Oct 4, 2010, at 5:30 PM, Simon Fraser wrote:
On Oct 4, 2010, at 2:33 PM, Adam Barth wrote:
As you might have noticed, the WebSocket tests are crashing on Leopard and Snow Leopard. I thought for a while that this might be related to my recent move of the WebSocket tests, but looks unrelated. The crashes started with a patch that flipped off the SVN executable bit for a bunch of files, which also seems unrelated (reverting that change locally also don't seem to make a difference).
Here's a reduced test case:
<script> var ws = new WebSocket('ws://localhost:1111/'); </script>
Just open a local HTML file containing that code and you'll crash WebKit on Snow Leopard (and presumably Leopard as well). The crash looks like some kind of heap corruption. At this point, I'd like to hand this off to someone who's more familiar with the WebSockets code. Any volunteers?
<https://bugs.webkit.org/show_bug.cgi?id=47136>
People with C++ and x86 assembly skills are encouraged to help out.
The Xcode project was picking up qt/SocketStreamHandle.h in error.
Fixed in http://trac.webkit.org/changeset/69057
You may have to quit and restart Xcode to have it build with the correct header.
Many thanks for fixing this issue (and the followup #error). :) Adam
participants (2)
-
Adam Barth
-
Simon Fraser