Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upCrash on startup loading any url #19299
Comments
|
What if you do delete the compiled js and mozjs dependencies from target/ and do |
|
It appears to work. Cheers. |
|
That is not what I was expecting to happen :< |
|
Actually this is a bigger problem than I was thinking there. If I make a change to layout and trigger a normal debug build then the crash is back each time. Release build works fine. Clean debug build doesn't. |
|
So digging into this a little more I've been remotely testing commits and this crash starts after the bump to websocket library. which appears to consist solely of this servo/rust-websocket@23b3e2b commit in rust-websocket. I'm not seeing the correlation. I was originally assuming it was a race condition since debug-mozjs works and release works. I tried taskset limiting to 1 core and stress to artificially slow everything down but neither had any effect. It does appear to be locked up as the crash take 11-13 seconds to happen, until that point you just have a grey screen. CPU is 100% on a single core until the crash. The trace output during the run is
Not much more I can do till I get back to my machine, but its all a bit strange to me. |
|
Turns out there is not much more I can do when I'm home either. Attached the debugger, it doesn't fail in 11 seconds it fails instantly; not sure what the time is when run without the debugger. Not much happening looking at all the other threads stacktraces, generally just the hsts preload is happening but that seems to be on a different part each time the crash happens. Not sure where to look really, or why I am the only person seeing this, or why bumping rust-websocket could possible cause the issue. If anyone has any ideas it would be great to hear, I can try run anything you would need and provide more details if required. |
|
In the world of fun that is this issue, b13107a appears to have fixed it. I can build master and run the browser since that commit. |
|
I believe we established that this was caused by integration of servo-media and violating the One Definition Rule in C++. |
Any url causes the same problem
commit: e4cfff8
This comes after updating this gentoo machine to build with the new build requirements, builds fine but doesn't run anymore.
If you need anymore information let me know.