-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash in FcPatternDestroy fontconfig #668
Comments
I get a core dump in Servo with FcPatternDestroy for an HTML file with > 10000 nodes and CSS file with > 1000 rules. The relevant HTML and CSS files are at https://gist.github.com/pradeep90/7462416 I ran it on a Linux machine |
In particular, I'm using PuTTY and XMing to run Servo remotely on the Linux machine. I have reproduced the segfault with the HTML file above many times.
|
I can also reproduce same segfault error when running Servo remotely on other Linux machine. |
We don't use font-config on Mac, so this specific backtrace wouldn't happen. Perhaps @larsbergstrom can try and replicate? |
ohhh when I tested on the other Linux machine, it works well.
I'm not sure whether the kernel version is related or not. |
no relation with kernel version. seems related with font configuration with remote x server |
I know that @evilpie was testing locally, not with a remote server, but I'm fine with focusing on solving the remote one here since it's so reproducible. |
I tested on the machine directly, and I got the same segfault error. So, it's not the problem related only on remote server. |
I'll get a Linux VM set up and try to repro it here. |
This bug doesn't reproduce in a VM running Ubuntu Linux on the file Pradeep provided. I'll try it on an actual machine with an NVidia card (I have one in a closet I should be able to set up). @june0cho Can you tell if there is a video hardware difference between those machines? e.g.,
Thanks! |
@larsbergstrom It was Nvidia! I think @pradeep90 's machine also has same graphic card. VGA info is as following:
|
Thanks for the info! I set up a NVidia-based linux box and have it building rust+servo. I'll test it tomorrow (I also have a Windows VM and XMing set up so I can reproduce your exact environment, just in case). |
Just to confirm, I too have Nvidia graphics card on my Linux machine. |
Thanks, lars! I just got the same error in acid2.html as well. It is not always shown for acid2.html, but seems fail once per 7~8 times. For pradeep's test file, the error was always shown. |
Interesting; I can't even get far enough to see that crash. Any page I attempt to load generates warnings about calls to |
This sounds like the RGB vs RGBA problem
|
So, I've looked at a variety of NVidia drivers on Linux. I can reproduce this crash (or the RGBA issue) by choosing the appropriate driver. The easiest fix seems to be to use the Noveau driver, which you can install on Ubuntu by: If that's not an option (say, because you are doing GPGPU programming on these boxes as well and need the NVidia drivers installed), then we are going to have to do some more work to figure out exactly how to work around each of the features that are missing from these cards. I'd want to talk to @pcwalton more before spending a bunch of time doing that to make sure I understand what his longer-term plans are in this space, because I thought he mentioned plans for some major changes to our graphics dependencies. |
Is there a minimized test case? I can pass this along internally if there is something easy to repro that points to a bug in the NVIDIA drivers. I don't see anything in that stack trace from our libGL, though, and I'm not sure our driver team has time to diagnose "there's something bizarre deep in Servo". Feel free to @jwise me if you come across NVIDIA driver bugs; I can triage and pass things along internally, given a clear enough repro case. |
@jwise Thanks for the offer - if we run into something specific, I will definitely bug you! I've tracked down the first part of our issues with Nvidia linux support ( #1185 ) as being a problem with our code. I suspect that the latter is as well and has to do with how we're create/destroying pixmaps that just happens to work with other driver stacks. I will also consult our internal gfx experts before running up the "bug in the drivers!" flag. |
OK, I've confirmed that my pending PRs that clean up NVidia driver support also fix this issue. Will close once they land. |
This should be fixed now! |
Rename and simplify video_014.htm to duration.html
Go to http://en.wikipedia.org/wiki/Hamster
Resize the window like a mad man
The text was updated successfully, but these errors were encountered: