RESOLVED FIXED143561
Remove TextureMapperImageBuffer
https://bugs.webkit.org/show_bug.cgi?id=143561
Summary Remove TextureMapperImageBuffer
Csaba Osztrogonác
Reported 2015-04-09 02:57:02 PDT
It isn't maintained and doesn't work, see https://bugs.webkit.org/show_bug.cgi?id=143214#c20 for details.
Attachments
Patch (13.07 KB, patch)
2015-04-09 02:57 PDT, Csaba Osztrogonác
no flags
Patch (15.59 KB, patch)
2015-04-09 03:08 PDT, Csaba Osztrogonác
no flags
Patch (21.49 KB, patch)
2015-04-09 03:33 PDT, Csaba Osztrogonác
no flags
Patch (22.31 KB, patch)
2015-04-09 03:43 PDT, Csaba Osztrogonác
no flags
Patch (33.51 KB, patch)
2015-04-09 05:23 PDT, Csaba Osztrogonác
zan: review+
results without the patch (6.71 KB, text/plain)
2015-04-10 06:11 PDT, Csaba Osztrogonác
no flags
results with the patch (26.05 KB, text/plain)
2015-04-10 06:12 PDT, Csaba Osztrogonác
no flags
crash log for accessibility/accessibility-node-memory-management.html (3.77 KB, text/plain)
2015-04-10 06:16 PDT, Csaba Osztrogonác
no flags
llvmpipe experiment (3.55 KB, patch)
2015-04-10 06:23 PDT, Csaba Osztrogonác
no flags
Patch (33.49 KB, patch)
2015-05-05 08:36 PDT, Csaba Osztrogonác
no flags
Csaba Osztrogonác
Comment 1 2015-04-09 02:57:51 PDT
Csaba Osztrogonác
Comment 2 2015-04-09 03:08:05 PDT
Created attachment 250432 [details] Patch removing setShouldSupportContentsTiling too
Csaba Osztrogonác
Comment 3 2015-04-09 03:12:32 PDT
Maybe we can remove AccelerationMode everywhere. Am I right?
Csaba Osztrogonác
Comment 4 2015-04-09 03:33:01 PDT
Created attachment 250433 [details] Patch removing accelerationMode + GTK buildfix
Csaba Osztrogonác
Comment 5 2015-04-09 03:43:47 PDT
Created attachment 250435 [details] Patch more GTK fix
Gwang Yoon Hwang
Comment 6 2015-04-09 04:04:30 PDT
(In reply to comment #3) > Maybe we can remove AccelerationMode everywhere. Am I right? Oh, yes. Please remove those!
Csaba Osztrogonác
Comment 7 2015-04-09 05:23:20 PDT
Created attachment 250436 [details] Patch removing BitmapTextureImageBuffer too to fix the GTK build
Csaba Osztrogonác
Comment 8 2015-04-09 05:29:48 PDT
Just a question is there anybody build with USE(TEXTURE_MAPPER) && !USE(TEXTURE_MAPPER_GL) ?
Gwang Yoon Hwang
Comment 9 2015-04-09 05:37:42 PDT
(In reply to comment #8) > Just a question is there anybody build with > USE(TEXTURE_MAPPER) && !USE(TEXTURE_MAPPER_GL) ? I don't think so. Maybe we can merge TEXTURE_MAPPER_GL and TEXTURE_MAPPER
Gwang Yoon Hwang
Comment 10 2015-04-09 22:30:04 PDT
Comment on attachment 250436 [details] Patch Looks good for me. I'll merge TextureMapper and TextureMapperGL in separate patch.
Zan Dobersek
Comment 11 2015-04-10 00:44:05 PDT
Comment on attachment 250436 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=250436&action=review > Source/WebCore/platform/graphics/texmap/TextureMapper.cpp:42 > return platformCreateAccelerated(); platformCreateAccelerated() can be removed as well, perhaps in the patch that merges USE(TEXTURE_MAPPER) and USE(TEXTURE_MAPPER_GL).
Zan Dobersek
Comment 12 2015-04-10 00:44:59 PDT
On the note of merging USE(TEXTURE_MAPPER) and USE(TEXTURE_MAPPER_GL), can the TextureMapper and TextureMapperGL (and the related classes) be merged as well?
Gwang Yoon Hwang
Comment 13 2015-04-10 00:49:49 PDT
(In reply to comment #12) > On the note of merging USE(TEXTURE_MAPPER) and USE(TEXTURE_MAPPER_GL), can > the TextureMapper and TextureMapperGL (and the related classes) be merged as > well? Yes, we can merge it. But I think it is safe to do it in separated bug.
Csaba Osztrogonác
Comment 14 2015-04-10 06:01:44 PDT
Unfortunately it didn't solve the problem, but introduced another crashes, see https://bugs.webkit.org/show_bug.cgi?id=143214#c23 for details. I'll upload detailed results soon.
Csaba Osztrogonác
Comment 15 2015-04-10 06:11:12 PDT
Created attachment 250512 [details] results without the patch
Csaba Osztrogonác
Comment 16 2015-04-10 06:12:08 PDT
Created attachment 250513 [details] results with the patch
Csaba Osztrogonác
Comment 17 2015-04-10 06:15:14 PDT
(In reply to comment #16) > Created attachment 250513 [details] > results with the patch There are two major problem: - Expected to fail, but passed: (267) - these tests don't pass at all in the real life. - Regressions: Unexpected crashes (72) - using TextureMapperGL with EFL which disabling GL isn't so good and cause this crashes
Csaba Osztrogonác
Comment 18 2015-04-10 06:16:12 PDT
Created attachment 250515 [details] crash log for accessibility/accessibility-node-memory-management.html
Csaba Osztrogonác
Comment 19 2015-04-10 06:23:42 PDT
Created attachment 250516 [details] llvmpipe experiment I tried to adapt GTK's solution to use llvmpipe for XVFBDriver, additionally force EFL to use GL with setting ELM_ENGINE=opengl_x11 and setting EVAS_GL_NO_BLACKLIST to force EFL not to blacklist llvmpipe ... but I got crash at the beginning somewhere in EFL when it called glGetString.
Csaba Osztrogonác
Comment 20 2015-04-10 06:27:07 PDT
I don't have enough graphics skill and any EFL internal skill to fix this bug and bug143214 myself in the near future, so feel free to pick it up, if anybody interested in fixing this bug.
Csaba Osztrogonác
Comment 21 2015-05-05 08:36:39 PDT
Created attachment 252385 [details] Patch Patch for landing. No regression with USE_NATIVE_XDISPLAY=1, which is already set on the EFL bots, so it's safe to land it now.
Csaba Osztrogonác
Comment 22 2015-05-05 08:51:57 PDT
(In reply to comment #21) > Created attachment 252385 [details] > Patch > > Patch for landing. No regression with USE_NATIVE_XDISPLAY=1, which is > already set on the EFL bots, so it's safe to land it now. Landed in http://trac.webkit.org/changeset/183807
Note You need to log in before you can comment on or make changes to this bug.