Bug 8521 - Webkitgtk JIT causes render failure on arm7
Summary: Webkitgtk JIT causes render failure on arm7
Status: RESOLVED DUPLICATE of bug 9474
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: graphics (show other bugs)
Version: 2.0
Hardware: BeagleBone Multiple
: Medium normal
Target Milestone: 2.1
Assignee: Robert Yang
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-10-15 10:05 UTC by Mark O'DOnovan
Modified: 2016-04-26 00:45 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark O'DOnovan 2015-10-15 10:05:41 UTC

    
Comment 1 Mark O'DOnovan 2015-10-15 10:09:47 UTC
There doesn't seem to be a bug category for meta-sato so i'll try here:

Regarding:
https://lists.yoctoproject.org/pipermail/yocto/2015-September/026660.html

The example below fails to render if JIT is enabled.
Disabling JIT solves this issue.

It will however render if I uncomment the 'alert' statement.

<!DOCTYPE html>
<html>
<head>
<title>Test</title>
</head>
<body>
<p>Page Rendered</p>
<script>
  //alert("JavaScript works")
</script>
</body>
</html>
Comment 2 Mark O'DOnovan 2015-10-15 10:16:54 UTC
And my meta-sato I meant poky/meta/recipes-sato.

Sorry if this bug report is a bit scattered, I was trying
to close the suggested-duplicate bugs window and submitted
an almost empty bug-report
Comment 3 Cristian Iorga 2015-11-18 16:58:03 UTC
Hi Randy,
Can you find the right owner for this bug, please?
I suspect the fix should be similar to poky commit: 7ecfaaaf5886c1892cc5190f8d632265ffd92f50

Thanks,
Cristian
Comment 4 Randy MacLeod 2016-04-25 23:25:36 UTC
Robert, I noticed that you were involved in an email thread where JIT is disabled for arm*. Please take this defect and fix in 2.2 and backport to 2.1. ../Randy
Comment 5 Robert Yang 2016-04-26 00:45:56 UTC
Duplicated to 9474.

*** This bug has been marked as a duplicate of bug 9474 ***