| Summary: | Weston crashes after "unexpectedly large timestamp jump" | ||
|---|---|---|---|
| Product: | Wayland | Reporter: | Sunny <sjwlaoda> |
| Component: | weston | Assignee: | Wayland bug list <wayland-bugs> |
| Status: | RESOLVED MOVED | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | 1.5.0 | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | crash log | ||
If you can still reproduce this, can you please try running under Valgrind? -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/wayland/weston/issues/56. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 107767 [details] crash log Hi I am using weston 1.6.0, I encountered a problem with weston running on fbdev backend after weston prints "unexpectedly large timestamp jump". for weston, I use animation=zoom, if I use "fade", then there is no such issue. for client egl applications, I use a script to launch two applications one by one, the first application draws one frame to the screen and then exits, the second application draws a very complicated scene that will take more than 2 seconds for GPU to finish. so when the second application runs, the weston desktop still keeps the first application's image, and then weston crashes. I can provide more information if required