Changes between Version 3 and Version 4 of WebKitGTK/TrackingMemoryErrors


Ignore:
Timestamp:
May 4, 2013 3:52:09 AM (8 years ago)
Author:
elima@igalia.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WebKitGTK/TrackingMemoryErrors

    v3 v4  
    1414}}}
    1515
    16 Notice the @--smc-check-all@ flag, which enables checks for self modifying code. ??(@FIXME: I suppose this is required because WK generates a lot of its own code, but a better confirmation/explanation here would be nice)??.
     16Notice the ''--smc-check-all'' flag, which enables checks for self modifying code. ''(@FIXME: I suppose this is required because WK generates a lot of its own code, but a better confirmation/explanation here would be nice)''.
    1717
    1818=== WebKit2 ===
     
    2525}}}
    2626
    27 Here, the interesting bit is @--trace-children=yes@, which tells valgrind to also hook into any child process spawned by the original program. For WK2 this is required if you want to check memory in the Web process (which you most likely do), otherwise it will only check it in the UI process.
     27Here, the interesting bit is ''--trace-children=yes'', which tells valgrind to also hook into any child process spawned by the original program. For WK2 this is required if you want to check memory in the Web process (which you most likely do), otherwise it will only check it in the UI process.
    2828
    2929Notice that for both WK1 and WK2, the corresponding launcher programs are used instead of the provided script, in order to avoid checking for errors in the script's runtime, which apart from been undesired, will slow down the process even more.