<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugs.webkit.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4.1"
          urlbase="https://bugs.webkit.org/"
          
          maintainer="admin@webkit.org"
>

    <bug>
          <bug_id>104665</bug_id>
          
          <creation_ts>2012-12-11 05:53:37 -0800</creation_ts>
          <short_desc>[EFL] API unit tests are running extremely slow on the bots</short_desc>
          <delta_ts>2013-01-21 11:33:30 -0800</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>WebKit</product>
          <component>WebKit EFL</component>
          <version>528+ (Nightly build)</version>
          <rep_platform>Unspecified</rep_platform>
          <op_sys>Unspecified</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>Normal</bug_severity>
          <target_milestone>---</target_milestone>
          <dependson>104666</dependson>
    
    <dependson>104782</dependson>
          <blocked>90451</blocked>
          <everconfirmed>1</everconfirmed>
          <reporter name="Thiago Marcos P. Santos">tmpsantos</reporter>
          <assigned_to name="Thiago Marcos P. Santos">tmpsantos</assigned_to>
          <cc>cdumez</cc>
    
    <cc>danw</cc>
    
    <cc>d-r</cc>
    
    <cc>gyuyoung.kim</cc>
    
    <cc>jinwoo7.song</cc>
    
    <cc>joone</cc>
    
    <cc>jussi.kukkonen</cc>
    
    <cc>kenneth</cc>
    
    <cc>laszlo.gombos</cc>
    
    <cc>lucas.de.marchi</cc>
    
    <cc>naginenis</cc>
    
    <cc>rakuco</cc>
    
    <cc>ryuan.choi</cc>
    
    <cc>svillar</cc>
    
    <cc>webkit.review.bot</cc>
          

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>788363</commentid>
    <comment_count>0</comment_count>
    <who name="Thiago Marcos P. Santos">tmpsantos</who>
    <bug_when>2012-12-11 05:53:37 -0800</bug_when>
    <thetext>They take ~60 seconds a full run on my desktop machine. For some reason on the bots we have a lot of dangling WebProcess sucking 100% of the CPU.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>788489</commentid>
    <comment_count>1</comment_count>
    <who name="Thiago Marcos P. Santos">tmpsantos</who>
    <bug_when>2012-12-11 09:02:21 -0800</bug_when>
    <thetext>Problem found!

The cache is creating too many garbage at:
/home/buildslave-1/.cache/WebKitEfl/</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>788498</commentid>
    <comment_count>2</comment_count>
    <who name="Thiago Marcos P. Santos">tmpsantos</who>
    <bug_when>2012-12-11 09:17:59 -0800</bug_when>
    <thetext>Guys, this is a serious issue.

The conclusion here is: soup_cache creates a lot of files over the time at .cache/WebKitEfl. When I checked the bots, it had close to 66k files.

Performance will deteriorate over time, since soup_cache_load() at WebProcessMainEfl.cpp does a complete readdir(.cache/WebKitEfl), so it will be O(n) and it takes a lot of CPU for that. *sigh*

We have to limit somehow the number of entries at this cache.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>788500</commentid>
    <comment_count>3</comment_count>
    <who name="Kenneth Rohde Christiansen">kenneth</who>
    <bug_when>2012-12-11 09:21:07 -0800</bug_when>
    <thetext>void soup_cache_set_max_size(SoupCache *cache, guint max_size);

http://developer.gnome.org/libsoup/unstable/SoupCache.html</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>788502</commentid>
    <comment_count>4</comment_count>
    <who name="Kenneth Rohde Christiansen">kenneth</who>
    <bug_when>2012-12-11 09:27:14 -0800</bug_when>
    <thetext>Why not use a different cache dir when running the tests and clear it before running the tests. Also I think something like 50MB should be sufficient and that should keep the file amount down as well</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>788504</commentid>
    <comment_count>5</comment_count>
    <who name="Kenneth Rohde Christiansen">kenneth</who>
    <bug_when>2012-12-11 09:30:38 -0800</bug_when>
    <thetext>https://bugzilla.mozilla.org/show_bug.cgi?id=559942 
https://code.google.com/p/chromium/issues/detail?id=40079

Info on chosen cache sizes in other browsers</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>789312</commentid>
    <comment_count>6</comment_count>
    <who name="Sergio Villar Senin">svillar</who>
    <bug_when>2012-12-12 01:09:54 -0800</bug_when>
    <thetext>(In reply to comment #2)
&gt; Guys, this is a serious issue.
&gt; 
&gt; The conclusion here is: soup_cache creates a lot of files over the time at .cache/WebKitEfl. When I checked the bots, it had close to 66k files.
&gt; 
&gt; Performance will deteriorate over time, since soup_cache_load() at WebProcessMainEfl.cpp does a complete readdir(.cache/WebKitEfl), so it will be O(n) and it takes a lot of CPU for that. *sigh*

That is not correct. The load of the cache reads the contents of a single file which stores the cache indexes. It&apos;s true that we need to improve that (there are several bugs in the gnome bugzilla for that) but it isn&apos;t not a complete readdir.

&gt; We have to limit somehow the number of entries at this cache.

There are a couple of options:

* setup a temporal dir for the cache during testing
* disable the cache during testing
* limit the size of the cache during testing</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>789353</commentid>
    <comment_count>7</comment_count>
    <who name="Joone Hur">joone</who>
    <bug_when>2012-12-12 02:04:15 -0800</bug_when>
    <thetext>I think we need an API to clear the cache files before running the test cases.
So, I&apos;ve filed a bug: https://bugs.webkit.org/show_bug.cgi?id=104782</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>789573</commentid>
    <comment_count>8</comment_count>
    <who name="Thiago Marcos P. Santos">tmpsantos</who>
    <bug_when>2012-12-12 08:15:56 -0800</bug_when>
    <thetext>(In reply to comment #6)
&gt; (In reply to comment #2)
&gt; &gt; Guys, this is a serious issue.
&gt; &gt; 
&gt; &gt; The conclusion here is: soup_cache creates a lot of files over the time at .cache/WebKitEfl. When I checked the bots, it had close to 66k files.
&gt; &gt; 
&gt; &gt; Performance will deteriorate over time, since soup_cache_load() at WebProcessMainEfl.cpp does a complete readdir(.cache/WebKitEfl), so it will be O(n) and it takes a lot of CPU for that. *sigh*
&gt; 
&gt; That is not correct. The load of the cache reads the contents of a single file which stores the cache indexes. It&apos;s true that we need to improve that (there are several bugs in the gnome bugzilla for that) but it isn&apos;t not a complete readdir.

Indeed, but looks like the entry count grows at the same rate as the file count on the folder. The process spends a lot of time inserting these entries on a list.

&gt; 
&gt; &gt; We have to limit somehow the number of entries at this cache.
&gt; 
&gt; There are a couple of options:
&gt; 
&gt; * setup a temporal dir for the cache during testing
&gt; * disable the cache during testing
&gt; * limit the size of the cache during testing

My main concern here is from the browser user point of view. I really don&apos;t expect the users to clear the cache when they fell like the browser is not performing.

At the time when I deleted the .cache/WebKitEfl folder on the bots, it had 65k files and the size of ~200MB. After removing the cache, the unit test run time dropped from 17 min to 1 min, which tells something about the impact of loading the cache when starting a WebProcess.

I did that yesterday and today it is already 1k files and ~3MB. I gonna fix this on the bots by creating some sort of temp dir, but it won&apos;t solve the underlining problem.

Would be good to work together with the libsoup developers on this issue.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>789574</commentid>
    <comment_count>9</comment_count>
    <who name="Dominik Röttsches (drott)">d-r</who>
    <bug_when>2012-12-12 08:17:48 -0800</bug_when>
    <thetext>CC&apos;ed Dan Winship - maybe he can comment.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>789583</commentid>
    <comment_count>10</comment_count>
    <who name="Sergio Villar Senin">svillar</who>
    <bug_when>2012-12-12 08:26:43 -0800</bug_when>
    <thetext>(In reply to comment #8)
&gt; (In reply to comment #6)
&gt; &gt; (In reply to comment #2)
&gt; &gt; &gt; Guys, this is a serious issue.
&gt; &gt; &gt; 
&gt; &gt; &gt; The conclusion here is: soup_cache creates a lot of files over the time at .cache/WebKitEfl. When I checked the bots, it had close to 66k files.
&gt; &gt; &gt; 
&gt; &gt; &gt; Performance will deteriorate over time, since soup_cache_load() at WebProcessMainEfl.cpp does a complete readdir(.cache/WebKitEfl), so it will be O(n) and it takes a lot of CPU for that. *sigh*
&gt; &gt; 
&gt; &gt; That is not correct. The load of the cache reads the contents of a single file which stores the cache indexes. It&apos;s true that we need to improve that (there are several bugs in the gnome bugzilla for that) but it isn&apos;t not a complete readdir.
&gt; 
&gt; Indeed, but looks like the entry count grows at the same rate as the file count on the folder. The process spends a lot of time inserting these entries on a list.
&gt; 
&gt; &gt; 
&gt; &gt; &gt; We have to limit somehow the number of entries at this cache.
&gt; &gt; 
&gt; &gt; There are a couple of options:
&gt; &gt; 
&gt; &gt; * setup a temporal dir for the cache during testing
&gt; &gt; * disable the cache during testing
&gt; &gt; * limit the size of the cache during testing
&gt; 
&gt; My main concern here is from the browser user point of view. I really don&apos;t expect the users to clear the cache when they fell like the browser is not performing.
&gt; 
&gt; At the time when I deleted the .cache/WebKitEfl folder on the bots, it had 65k files and the size of ~200MB. After removing the cache, the unit test run time dropped from 17 min to 1 min, which tells something about the impact of loading the cache when starting a WebProcess.
&gt; 
&gt; I did that yesterday and today it is already 1k files and ~3MB. I gonna fix this on the bots by creating some sort of temp dir, but it won&apos;t solve the underlining problem.
&gt; 
&gt; Would be good to work together with the libsoup developers on this issue.

So as I said there are a couple of reasons why it takes so long. The main one is likely that the HTTP headers are currently stored in the index. Loading the index means allocating space for all of them and also deserialize them from the index file.

I opened https://bugzilla.gnome.org/show_bug.cgi?id=665884 some time ago to fix that. The patches were accepted but I didn&apos;t commit them yet because I am not totally sure that they&apos;re correct (not having the headers in memory added some complexities to the SoupCache).</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>789940</commentid>
    <comment_count>11</comment_count>
    <who name="Thiago Marcos P. Santos">tmpsantos</who>
    <bug_when>2012-12-12 14:47:39 -0800</bug_when>
    <thetext>(In reply to comment #10)
&gt; (In reply to comment #8)
&gt; &gt; (In reply to comment #6)
&gt; &gt; &gt; (In reply to comment #2)
&gt; &gt; &gt; &gt; Guys, this is a serious issue.
&gt; &gt; &gt; &gt; 
&gt; &gt; &gt; &gt; The conclusion here is: soup_cache creates a lot of files over the time at .cache/WebKitEfl. When I checked the bots, it had close to 66k files.
&gt; &gt; &gt; &gt; 
&gt; &gt; &gt; &gt; Performance will deteriorate over time, since soup_cache_load() at WebProcessMainEfl.cpp does a complete readdir(.cache/WebKitEfl), so it will be O(n) and it takes a lot of CPU for that. *sigh*
&gt; &gt; &gt; 
&gt; &gt; &gt; That is not correct. The load of the cache reads the contents of a single file which stores the cache indexes. It&apos;s true that we need to improve that (there are several bugs in the gnome bugzilla for that) but it isn&apos;t not a complete readdir.
&gt; &gt; 
&gt; &gt; Indeed, but looks like the entry count grows at the same rate as the file count on the folder. The process spends a lot of time inserting these entries on a list.
&gt; &gt; 
&gt; &gt; &gt; 
&gt; &gt; &gt; &gt; We have to limit somehow the number of entries at this cache.
&gt; &gt; &gt; 
&gt; &gt; &gt; There are a couple of options:
&gt; &gt; &gt; 
&gt; &gt; &gt; * setup a temporal dir for the cache during testing
&gt; &gt; &gt; * disable the cache during testing
&gt; &gt; &gt; * limit the size of the cache during testing
&gt; &gt; 
&gt; &gt; My main concern here is from the browser user point of view. I really don&apos;t expect the users to clear the cache when they fell like the browser is not performing.
&gt; &gt; 
&gt; &gt; At the time when I deleted the .cache/WebKitEfl folder on the bots, it had 65k files and the size of ~200MB. After removing the cache, the unit test run time dropped from 17 min to 1 min, which tells something about the impact of loading the cache when starting a WebProcess.
&gt; &gt; 
&gt; &gt; I did that yesterday and today it is already 1k files and ~3MB. I gonna fix this on the bots by creating some sort of temp dir, but it won&apos;t solve the underlining problem.
&gt; &gt; 
&gt; &gt; Would be good to work together with the libsoup developers on this issue.
&gt; 
&gt; So as I said there are a couple of reasons why it takes so long. The main one is likely that the HTTP headers are currently stored in the index. Loading the index means allocating space for all of them and also deserialize them from the index file.
&gt; 
&gt; I opened https://bugzilla.gnome.org/show_bug.cgi?id=665884 some time ago to fix that. The patches were accepted but I didn&apos;t commit them yet because I am not totally sure that they&apos;re correct (not having the headers in memory added some complexities to the SoupCache).

I made the mistake of just deleting the cache on the bots. I should have saved it to help on the profiling the hotspots for optimization. Fortunately (if I can say that) the EFL bot maintained by Samsung still has the issue.

Gyuyoung, is it possible to share somehow the contents of .cache/WebKitEfl from the efl-buildslave-1 before you remove it? It would be very helpful on debugging this issue.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>790231</commentid>
    <comment_count>12</comment_count>
    <who name="Gyuyoung Kim">gyuyoung.kim</who>
    <bug_when>2012-12-12 20:32:03 -0800</bug_when>
    <thetext>(In reply to comment #11)
&gt; Gyuyoung, is it possible to share somehow the contents of .cache/WebKitEfl from the efl-buildslave-1 before you remove it? It would be very helpful on debugging this issue.

Sure, I will share it via email or ftp server.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>796884</commentid>
    <comment_count>13</comment_count>
      <attachid>180645</attachid>
    <who name="Joone Hur">joone</who>
    <bug_when>2012-12-23 22:46:25 -0800</bug_when>
    <thetext>Created attachment 180645
Proposed Patch

I&apos;ve implemented ewk_context_resource_cache_clear API, which allows to clear all resource caches in memory and local storage. 
https://bugs.webkit.org/show_bug.cgi?id=104782

We can clear all cache files by calling this API before running the API unit tests.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>796921</commentid>
    <comment_count>14</comment_count>
      <attachid>180645</attachid>
    <who name="Kenneth Rohde Christiansen">kenneth</who>
    <bug_when>2012-12-24 01:48:39 -0800</bug_when>
    <thetext>Comment on attachment 180645
Proposed Patch

Is this up for review? I still think the name is not so good, what is a resource cache? Does it include more than http?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>797553</commentid>
    <comment_count>15</comment_count>
      <attachid>180645</attachid>
    <who name="Thiago Marcos P. Santos">tmpsantos</who>
    <bug_when>2012-12-27 07:38:19 -0800</bug_when>
    <thetext>Comment on attachment 180645
Proposed Patch

I&apos;m fine with this patch as long as we create a patch to fix the performance degradation caused by the cache.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>798190</commentid>
    <comment_count>16</comment_count>
      <attachid>180645</attachid>
    <who name="Gyuyoung Kim">gyuyoung.kim</who>
    <bug_when>2012-12-29 21:03:14 -0800</bug_when>
    <thetext>Comment on attachment 180645
Proposed Patch

LGTM</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>798191</commentid>
    <comment_count>17</comment_count>
      <attachid>180645</attachid>
    <who name="Gyuyoung Kim">gyuyoung.kim</who>
    <bug_when>2012-12-29 21:05:31 -0800</bug_when>
    <thetext>Comment on attachment 180645
Proposed Patch

It looks someone else might wanna have final a look.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>798192</commentid>
    <comment_count>18</comment_count>
    <who name="Joone Hur">joone</who>
    <bug_when>2012-12-29 21:07:05 -0800</bug_when>
    <thetext>(In reply to comment #15)
&gt; (From update of attachment 180645 [details])
&gt; I&apos;m fine with this patch as long as we create a patch to fix the performance degradation caused by the cache.

The ewk_context_resource_cache_clear API landed, so this patch could fix the performance degradation.

http://trac.webkit.org/changeset/138554</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>801511</commentid>
    <comment_count>19</comment_count>
    <who name="Thiago Marcos P. Santos">tmpsantos</who>
    <bug_when>2013-01-07 11:57:09 -0800</bug_when>
    <thetext>What about landing this patch? Joone?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>801681</commentid>
    <comment_count>20</comment_count>
    <who name="Joone Hur">joone</who>
    <bug_when>2013-01-07 14:53:25 -0800</bug_when>
    <thetext>(In reply to comment #19)
&gt; What about landing this patch? Joone?

I think that we need Kenneth&apos;s final confirmation.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>801772</commentid>
    <comment_count>21</comment_count>
    <who name="Laszlo Gombos">laszlo.gombos</who>
    <bug_when>2013-01-07 16:02:20 -0800</bug_when>
    <thetext>(In reply to comment #6)
&gt; (In reply to comment #2)
&gt; &gt; Guys, this is a serious issue.
&gt; &gt; 
&gt; &gt; The conclusion here is: soup_cache creates a lot of files over the time at .cache/WebKitEfl. When I checked the bots, it had close to 66k files.
&gt; &gt; 
&gt; &gt; Performance will deteriorate over time, since soup_cache_load() at WebProcessMainEfl.cpp does a complete readdir(.cache/WebKitEfl), so it will be O(n) and it takes a lot of CPU for that. *sigh*
&gt; 
&gt; That is not correct. The load of the cache reads the contents of a single file which stores the cache indexes. It&apos;s true that we need to improve that (there are several bugs in the gnome bugzilla for that) but it isn&apos;t not a complete readdir.

Sergio, can you share with us which soup bugs (bug ids or urls) are relevant for this issue so that we can track them ?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>801903</commentid>
    <comment_count>22</comment_count>
    <who name="Dan Winship">danw</who>
    <bug_when>2013-01-07 18:13:01 -0800</bug_when>
    <thetext>https://bugzilla.gnome.org/show_bug.cgi?id=665884 moves the HTTP headers from the cache index file into the individual cache files, thereby making the index much smaller.

https://bugzilla.gnome.org/show_bug.cgi?id=666143 discusses changing the way cache files are stored, but Sergio keeps forgetting to attach his old patches there (hint hint :).</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>812288</commentid>
    <comment_count>23</comment_count>
      <attachid>180645</attachid>
    <who name="WebKit Review Bot">webkit.review.bot</who>
    <bug_when>2013-01-21 11:33:24 -0800</bug_when>
    <thetext>Comment on attachment 180645
Proposed Patch

Clearing flags on attachment: 180645

Committed r140348: &lt;http://trac.webkit.org/changeset/140348&gt;</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>812289</commentid>
    <comment_count>24</comment_count>
    <who name="WebKit Review Bot">webkit.review.bot</who>
    <bug_when>2013-01-21 11:33:30 -0800</bug_when>
    <thetext>All reviewed patches have been landed.  Closing bug.</thetext>
  </long_desc>
      
          <attachment
              isobsolete="0"
              ispatch="1"
              isprivate="0"
          >
            <attachid>180645</attachid>
            <date>2012-12-23 22:46:25 -0800</date>
            <delta_ts>2013-01-21 11:33:24 -0800</delta_ts>
            <desc>Proposed Patch</desc>
            <filename>clear_cache.patch</filename>
            <type>text/plain</type>
            <size>1629</size>
            <attacher name="Joone Hur">joone</attacher>
            
              <data encoding="base64">ZGlmZiAtLWdpdCBhL1NvdXJjZS9XZWJLaXQyL0NoYW5nZUxvZyBiL1NvdXJjZS9XZWJLaXQyL0No
YW5nZUxvZwppbmRleCBjN2RhMTliLi5mYzc2MmEzIDEwMDY0NAotLS0gYS9Tb3VyY2UvV2ViS2l0
Mi9DaGFuZ2VMb2cKKysrIGIvU291cmNlL1dlYktpdDIvQ2hhbmdlTG9nCkBAIC0xLDUgKzEsMTgg
QEAKIDIwMTItMTItMjMgIEpvb25lIEh1ciAgPGpvb25lLmh1ckBpbnRlbC5jb20+CiAKKyAgICAg
ICAgW0VGTF0gQVBJIHVuaXQgdGVzdHMgYXJlIHJ1bm5pbmcgZXh0cmVtZWx5IHNsb3cgb24gdGhl
IGJvdHMKKyAgICAgICAgaHR0cHM6Ly9idWdzLndlYmtpdC5vcmcvc2hvd19idWcuY2dpP2lkPTEw
NDY2NQorCisgICAgICAgIFJldmlld2VkIGJ5IE5PQk9EWSAoT09QUyEpLgorCisgICAgICAgIENs
ZWFyIEhUVFAgY2FjaGUgZmlsZXMgYmVmb3JlIHJ1bm5pbmcgdGhlIHVuaXQgdGVzdHMsIHdoaWNo
IHByZXZlbnRzIAorICAgICAgICBwZXJmb3JtYW5jZSBkZWdyYWRhdGlvbiBkdWUgdG8gc28gbWFu
eSBjYWNoZSBmaWxlcy4KKworICAgICAgICAqIFVJUHJvY2Vzcy9BUEkvZWZsL3Rlc3RzL1VuaXRU
ZXN0VXRpbHMvRVdLMlVuaXRUZXN0QmFzZS5jcHA6CisgICAgICAgIChFV0syVW5pdFRlc3Q6OkVX
SzJVbml0VGVzdEJhc2U6OlNldFVwKToKKworMjAxMi0xMi0yMyAgSm9vbmUgSHVyICA8am9vbmUu
aHVyQGludGVsLmNvbT4KKwogICAgICAgICBbRUZMXVtXSzJdIEltcGxlbWVudCBld2tfY29udGV4
dF9yZXNvdXJjZV9jYWNoZV9jbGVhcgogICAgICAgICBodHRwczovL2J1Z3Mud2Via2l0Lm9yZy9z
aG93X2J1Zy5jZ2k/aWQ9MTA0NzgyCiAKZGlmZiAtLWdpdCBhL1NvdXJjZS9XZWJLaXQyL1VJUHJv
Y2Vzcy9BUEkvZWZsL3Rlc3RzL1VuaXRUZXN0VXRpbHMvRVdLMlVuaXRUZXN0QmFzZS5jcHAgYi9T
b3VyY2UvV2ViS2l0Mi9VSVByb2Nlc3MvQVBJL2VmbC90ZXN0cy9Vbml0VGVzdFV0aWxzL0VXSzJV
bml0VGVzdEJhc2UuY3BwCmluZGV4IGIzZmJjYmYuLmU2NGY0Y2MgMTAwNjQ0Ci0tLSBhL1NvdXJj
ZS9XZWJLaXQyL1VJUHJvY2Vzcy9BUEkvZWZsL3Rlc3RzL1VuaXRUZXN0VXRpbHMvRVdLMlVuaXRU
ZXN0QmFzZS5jcHAKKysrIGIvU291cmNlL1dlYktpdDIvVUlQcm9jZXNzL0FQSS9lZmwvdGVzdHMv
VW5pdFRlc3RVdGlscy9FV0syVW5pdFRlc3RCYXNlLmNwcApAQCAtNjIsNiArNjIsOSBAQCB2b2lk
IEVXSzJVbml0VGVzdEJhc2U6OlNldFVwKCkKIAogICAgIEV3a19Db250ZXh0KiBuZXdDb250ZXh0
ID0gZXdrX2NvbnRleHRfbmV3KCk7CiAgICAgbV93ZWJWaWV3ID0gZXdrX3ZpZXdfc21hcnRfYWRk
KGV2YXMsIHNtYXJ0LCBuZXdDb250ZXh0KTsKKyAgICAvLyBDbGVhciBIVFRQIGNhY2hlIGZpbGVz
IGJlZm9yZSBydW5uaW5nIHRoZSB1bml0IHRlc3RzLCB3aGljaCBwcmV2ZW50cyAKKyAgICAvLyBw
ZXJmb3JtYW5jZSBkZWdyYWRhdGlvbiBkdWUgdG8gc28gbWFueSBjYWNoZSBmaWxlcy4KKyAgICBl
d2tfY29udGV4dF9yZXNvdXJjZV9jYWNoZV9jbGVhcihuZXdDb250ZXh0KTsKICAgICBld2tfb2Jq
ZWN0X3VucmVmKG5ld0NvbnRleHQpOwogCiAgICAgZXdrX3ZpZXdfdGhlbWVfc2V0KG1fd2ViVmll
dywgZW52aXJvbm1lbnQtPmRlZmF1bHRUaGVtZSgpKTsK
</data>

          </attachment>
      

    </bug>

</bugzilla>