Updates:
Cc: phajdan...@chromium.org
Comment #33 on issue 265 by phajdan...@chromium.org: Safe-Browsing feature
hogs system
http://code.google.com/p/chromium/issues/detail?id=265
Issue 1611 has been merged into this issue.
--
You received this message because you are listed in the
Comment #32 on issue 265 by phajdan...@chromium.org: Safe-Browsing feature
hogs system
http://code.google.com/p/chromium/issues/detail?id=265
Issue 1933 has been merged into this issue.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because
Comment #29 on issue 265 by divi...@hotmail.com: Safe-Browsing feature hogs
system
http://code.google.com/p/chromium/issues/detail?id=265
This should be priority 1 and has this been merged into the release branch
yet?
--
You received this message because you are listed in the owner
or CC
Comment #28 on issue 265 by shmulik: Safe-Browsing feature hogs system
http://code.google.com/p/chromium/issues/detail?id=265
Had the same problem on WinXP x64 with Chrome 1.0.154.36,
--new-safe-browsing fixes
it. When is r6015 from trunk, to make it the default behavior, going to be
merged
Comment #27 on issue 265 by philippickles: Safe-Browsing feature hogs system
http://code.google.com/p/chromium/issues/detail?id=265
I can also confirm this works well.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this
Comment #26 on issue 265 by jorgen.ekroth: Safe-Browsing feature hogs system
http://code.google.com/p/chromium/issues/detail?id=265
I can confirm that the new safe browsing system works quite well. The old
way pretty
much hogged the drive for minutes and minutes...
--
You received this
Comment #25 on issue 265 by xploded: Safe-Browsing feature hogs system
http://code.google.com/p/chromium/issues/detail?id=265
the hard drive did go crazy
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may
Comment #24 on issue 265 by xploded: Safe-Browsing feature hogs system
http://code.google.com/p/chromium/issues/detail?id=265
added the flag to the shortcut,
turned on safe browsing,
have not noticed anything going on.
I will go and try it again without the flag and see if the hard drive goes
Comment #22 on issue 265 by [EMAIL PROTECTED]: Safe-Browsing feature hogs
system
http://code.google.com/p/chromium/issues/detail?id=265
Thanks for all the feedback on this issue, we've made progress towards
fixing the problem.
The latest version of Google Chrome (0.4.154.25) is being
Comment #23 on issue 265 by [EMAIL PROTECTED]: Safe-Browsing
feature hogs system
http://code.google.com/p/chromium/issues/detail?id=265
Is the problem resolved when you update to 0.4.154.25 and run behind the
flag --new-
safe-browsing?
--
You received this message because you are listed
Issue 265: Safe-Browsing feature hogs system
http://code.google.com/p/chromium/issues/detail?id=265
Comment #21 by kurienmathew73:
Same behavior as in comment 14
(http://code.google.com/p/chromium/issues/detail?id=265#c14)
--
You received this message because you are listed in the owner
or
Issue 265: Safe-Browsing feature hogs system
http://code.google.com/p/chromium/issues/detail?id=265
Comment #16 by [EMAIL PROTECTED]:
(No comment was entered for this change.)
Issue attribute updates:
Status: Assigned
Owner: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
--
Issue 265: Safe-Browsing feature hogs system
http://code.google.com/p/chromium/issues/detail?id=265
Comment #15 by singh.ramandeep:
This happens on Vista too, The safe browsing file keeps growing. The hard
disk
access is in miliseconds. This just makes it useless.
Attachments:
Issue 265: Safe-Browsing feature hogs system
http://code.google.com/p/chromium/issues/detail?id=265
Comment #11 by zwangf:
I used Filemon (one of the sysinternal tools) and find that during a short
period of
78 seconds, there are almost 93862 read/write to the same safe browsing and
safe
Issue 265: Safe-Browsing feature hogs system
http://code.google.com/p/chromium/issues/detail?id=265
Comment #8 by xploded:
I can confirm the temporary unresponsiveness.
version 0.2.149.27 (updating as I type)
might be the Vaccuum procedure SQLite does. I just tried a vaccuum manually
using
15 matches
Mail list logo
