Bug 96179 - Crash in object_heap.c:68 after heavy switching on/off H264 decoding of 6 streams in parallel
Summary: Crash in object_heap.c:68 after heavy switching on/off H264 decoding of 6 str...
Status: RESOLVED WORKSFORME
Alias: None
Product: libva
Classification: Unclassified
Component: intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: haihao
QA Contact: Sean V Kelley
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-25 07:48 UTC by Thomas
Modified: 2017-02-03 06:38 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Thomas 2016-05-25 07:48:28 UTC 
I've got here a test running with gstreamer switching on and off 6 H264 streams in parallel. For the decoding hardware acceleration is used with the vaapi elements.
After a few hundred switches I get a crash in object_heap.c:68 because heap->bucket is NULL.
I've tested it with the head revision of the git repository.

Regards,
Thomas
Comment 1 haihao 2016-07-27 07:26:35 UTC 
Could you provide your command line?
Comment 2 Thomas 2016-07-27 12:01:55 UTC 
Sorry, I don't have a command line for this. It happend inside a library which is used by chrome.
Comment 3 Víctor Jáquez 2016-07-27 13:06:58 UTC 
A backtrace is possible?
Comment 4 Thomas 2016-07-27 14:52:56 UTC 
I will try to reproduce it. This may take some time becase we switched off vaapi support.
Comment 5 haihao 2016-08-23 05:12:39 UTC 
Any update? could you provide a backtrace?
Comment 6 haihao 2016-12-01 04:20:02 UTC 
Any update on the backtrace?
Comment 7 Thomas 2017-01-27 06:49:05 UTC 
I have tested it with the latest GStreamer version and libva 1.7.2 and i965-va-driver 1.7.0.
I couldn't reproduce the error even after more than 7000 switches.
Regards,
Thomas
Comment 8 haihao 2017-02-03 06:38:58 UTC 
According to comment #7, I closed the bug as worksforme.  Note the project is moved to https://github.com/01org/libva, please feel free to file a new issue in https://github.com/01org/libva/issues/new if you still experience this issue.

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.