Summary: | REGRESSION(r??????): Crash in ~TextureMapperGLData | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Michael Catanzaro <mcatanzaro> | ||||
Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED DUPLICATE | ||||||
Severity: | Normal | CC: | bugs-noreply, magomez, mcatanzaro | ||||
Priority: | P2 | ||||||
Version: | Other | ||||||
Hardware: | PC | ||||||
OS: | Linux | ||||||
See Also: | https://bugzilla.redhat.com/show_bug.cgi?id=1569539 | ||||||
Attachments: |
|
Description
Michael Catanzaro
2017-12-04 12:42:19 PST
Created attachment 338323 [details]
Backtrace
Full backtrace, note:
#0 WebCore::GLContext::version (this=0x0) at /usr/src/debug/webkitgtk4-2.20.1-1.fc27.x86_64/Source/WebCore/platform/graphics/GLContext.cpp:172
[Current thread is 1 (Thread 0x7f61dcff9700 (LWP 3206))]
Calling a member function on a NULL GLContext seems bad
Looks like the GLContext::current is required to be destroyed before all TextureMapperGLData objects, but that didn't happen for some reason. This is the same as https://bugs.webkit.org/show_bug.cgi?id=184040, which has more detailed backtrace. I have the latter on my TODO when I have a moment, can we close this as duplicated of that one? Sure, though the backtrace in attachment #338323 [details] looks more detailed to me. *** This bug has been marked as a duplicate of bug 184040 *** |