43, SciLab 5.5.0, SketchUp 2015, V-Ray for 3dmax 2015, Consultant PlusĢ cores AMD Opteron 6386 SE 2.8GHz, 3Gb memory 80, HaoZip 5.0, Microsoft IIS 8.0 Express, Java 8 SE 8u66, K-Lite Mega Codec Pack 11.5.6, Microsoft Office Professional Plus 2013, Microsoft Project Professional 2013, Microsoft Visio Professional 2013, Microsoft Internet Explorer 11, Microsoft Silverlight 5.1, Microsoft Silverlight SDK 5.1, Microsoft SQL Server 2012 Express LocalDB, Microsoft Visual Studio Community 2013, Mozila Firefox 41.0.2, Opera. If you have a comprehensive minimal test case reproducing the issue you're hitting on Firefox, and/or detailed steps to reproduce the issue on Beta 46, can you please open a new bug, set its component to JavaScript Engine, and we can start looking at it there? This bug here is probably not the source of your issues.4 cores Intel Xeon e5-2690 3GHz, 6Gb memory, NVidia Grid K2 1GbĪdobe Acrobat X Pro 10.1.1, Adobe AIR 19.0.0.213, Adobe Creative Suite 6 Design Standart, Adobe Flash Player19 (ActiveX, NPAPI, PPAPI), Adobe Photoshop CS3, Adobe Reader XI (11.0.12), Adobe Shockwave Player 12.2, Autodesk 3ds Max 2015, Autodesk AutoCAD 2015, Autodesk DirectConnect 2015, Autodesk Inventor Server Engine for 3ds Max 2015, Autodesk Material Library 2015, Autodesk Recap, CCleaner 5.11, CorelDRAW Graphics Suite X4,Far Manager 3, Foxit Reader 7., Google Chrome. If the issue is reproducing in both the latest Chrome release and in Firefox Beta 46, it *could* also be a bug in your code base, but a bug in both browsers isn't excluded, of course. Hi, this shouldn't be related to this enhancement: in a nutshell, this provoked Firefox to *crash* if there is a serious security issue (code being overwritten), which should *not* be hit by GWT, unless there is a bug in Firefox itself. > Maybe the GWT produced JS is not really W^X protection compatible.
> Haven't spent time yet to test with a custom FF build *WITHOUT* the > anything specific regarding to W^X protection there. > 49 release, which contains several security updates too. > Strangely enough, it also shows the same behavior in the very latest Chrome > is still apparent in FF Dev Edition 47. > GWT/GXT (Sencha), which seems break terribly since Firefox Beta 46, and it > We have an internal company web client application based on (JS generation) (In reply to wing-tung Leung from comment #30) $ /usr/pobj/firefox-41.0.2/build-amd64/js/src/shell/js -non-writable-jitcode /usr/pobj/firefox-41.0.2/mozilla-release/js/src/octane/run.js Output from some js/src/octane/run.js runs with 41.0.2 + the patch from 1215573 on OpenBSD/amd64:
0 kommentar(er)
