Skip to content
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

Servo forced exit with error msg #554

Closed
junhoseo opened this issue Jul 1, 2013 · 2 comments
Closed

Servo forced exit with error msg #554

junhoseo opened this issue Jul 1, 2013 · 2 comments

Comments

@junhoseo
Copy link

@junhoseo junhoseo commented Jul 1, 2013

Hello,

I'm in troubled with servo engine.
I was build a servo src code and test the program. But the program forced exit with error msg.

My hardware and OS system environment are like this (build in virtualbox) :
host
32bit Windows7
4GB ram

guest
Ubuntu 12.04 64bit
assigned memory 1024MB
using hardware acceleration (3D)
video memory 48MB

Also, I want to see any video or picture about servo. There are no one about servo's search result. I interested in this engine, but i can't get any visible data about this. If anyone has a video or a picture, please give me that.

The error msg as follows :

jhseo@jhseo-VirtualBox:/devel/servo$ export LIBGL_ALWAYS_INDIRECT=1
jhseo@jhseo-VirtualBox:
/devel/servo$ ./build/servo ./src/test/html/hello.html
rust: ~"Elided an UnscannedTextbox because it was zero-length after compression; box b6: UnscannedTextRenderBox(\n)"
rust: ~"Elided an UnscannedTextbox because it was zero-length after compression; box b7: UnscannedTextRenderBox(\n)"
shader info log:
rust: task failed at 'failed to compile shader', /home/jhseo/devel/servo/src/support/layers/rust-layers/rendergl.rs:80
rust: domain main @0x1ac19d0 root task failed
rust: task failed at 'killed', /home/jhseo/devel/servo/src/compiler/rust/src/libcore/pipes.rs:281
rust: task failed at 'killed', /home/jhseo/devel/servo/src/compiler/rust/src/libcore/pipes.rs:281
rust: task failed at 'killed', /home/jhseo/devel/servo/src/compiler/rust/src/libcore/pipes.rs:281
rust: task failed at 'killed', /home/jhseo/devel/servo/src/compiler/rust/src/libcore/pipes.rs:281
rust: task failed at 'killed', /home/jhseo/devel/servo/src/compiler/rust/src/libcore/pipes.rs:281
rust: task failed at 'killed', /home/jhseo/devel/servo/src/compiler/rust/src/libcore/pipes.rs:281
rust: task failed at 'killed', /home/jhseo/devel/servo/src/compiler/rust/src/libcore/pipes.rs:281
rust: task failed at 'killed', /home/jhseo/devel/servo/src/compiler/rust/src/libcore/pipes.rs:281
rust: task failed at 'killed', /home/jhseo/devel/servo/src/compiler/rust/src/libcore/pipes.rs:281
rust: ~"tracing 140048052822848:"
rust: ~"tracing first child"
rust: ~"tracing last child"
rust: ~"tracing 140048052822992:"
rust: ~"tracing parent"
rust: ~"tracing first child"
rust: ~"tracing last child"
rust: ~"tracing prev sibling"
rust: ~"tracing 140048052822944:"
rust: ~"tracing parent"
rust: ~"tracing next sibling"
rust: ~"tracing prev sibling"
rust: ~"tracing 140048052823088:"
rust: ~"tracing parent"
rust: ~"tracing first child"
rust: ~"tracing last child"
rust: ~"tracing prev sibling"
rust: ~"tracing 140048052823328:"
rust: ~"tracing parent"
rust: ~"tracing prev sibling"
rust: ~"tracing 140048052823280:"
rust: ~"tracing parent"
rust: ~"tracing next sibling"
rust: ~"tracing prev sibling"
rust: ~"tracing 140048052823184:"
rust: ~"tracing parent"
rust: ~"tracing first child"
rust: ~"tracing last child"
rust: ~"tracing next sibling"
rust: ~"tracing prev sibling"
rust: ~"tracing 140048052823232:"
rust: ~"tracing parent"
rust: ~"tracing 140048052823136:"
rust: ~"tracing parent"
rust: ~"tracing next sibling"
rust: ~"tracing 140048052823040:"
rust: ~"tracing parent"
rust: ~"tracing next sibling"
rust: ~"tracing 140048052822896:"
rust: ~"tracing parent"
rust: ~"tracing next sibling"
servo: /home/jhseo/devel/servo/src/compiler/rust/src/rt/rust_task.cpp:80: void rust_task::delete_this(): Assertion `!borrow_list' failed.
stopped (core dumped)

@jdm
Copy link
Member

@jdm jdm commented Jul 1, 2013

Looks like the same problem as #340.

@metajack
Copy link
Contributor

@metajack metajack commented Jul 10, 2013

This should now be fixed as of today. Software rendering is no longer required on linux, as we've ported to glfw and reused the X11 display pointers to avoid driver bugs with GL context sharing.

Please reopen if you continue to have trouble.

@metajack metajack closed this Jul 10, 2013
ChrisParis pushed a commit to ChrisParis/servo that referenced this issue Sep 7, 2014
Use the routes defined in serve.py rather than the defaults
glennw pushed a commit to glennw/servo that referenced this issue Jan 16, 2017
Introduce SourceTexture, an abstraction for location of source textures.

This allows the backend thread to work with textures that have
been allocation by the texture cache, via webgl or an external
source transparently. The native texture ID is resolved by the
rendering thread as requited.

Specifically:

* Add SourceTexture, an abstraction for the location of a source texture.
* Add CacheTextureID, an ID for a texture cache managed texture.
    * This removes the need to allocate a pool of textures up front.
* Remove unused batch.rs file.
* Remove the concept of "raw textures" from device.rs
    * The native texture ID is stored inside the SourceTexture enum now.
* Remove some unused functions in device.rs.

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/webrender/554)
<!-- Reviewable:end -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.