Comment #4 on issue 16495 by [email protected]: Histogram data in a renderer should be uploaded to the browser before the renderer process is terminated. http://code.google.com/p/chromium/issues/detail?id=16495
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=33933
------------------------------------------------------------------------
r33933 | [email protected] | 2009-12-05 16:09:37 -0800 (Sat, 05 Dec 2009) |
12 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/base/histogram.cc?r1=33933&r2=33932
M
http://src.chromium.org/viewvc/chrome/trunk/src/base/histogram.h?r1=33933&r2=33932
M
http://src.chromium.org/viewvc/chrome/trunk/src/base/histogram_unittest.cc?r1=33933&r2=33932
M
http://src.chromium.org/viewvc/chrome/trunk/src/base/message_loop.cc?r1=33933&r2=33932
M
http://src.chromium.org/viewvc/chrome/trunk/src/base/message_loop.h?r1=33933&r2=33932
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/chrome_browser_application_mac.mm?r1=33933&r2=33932
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/diagnostics/sqlite_diagnostics.cc?r1=33933&r2=33932
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/jankometer.cc?r1=33933&r2=33932
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/net/dns_host_info.cc?r1=33933&r2=33932
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/net/websocket_experiment/websocket_experiment_runner.cc?r1=33933&r2=33932
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/renderer_host/buffered_resource_handler.cc?r1=33933&r2=33932
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/safe_browsing/safe_browsing_blocking_page.cc?r1=33933&r2=33932
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ssl/ssl_blocking_page.cc?r1=33933&r2=33932
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/sync/profile_sync_service.cc?r1=33933&r2=33932
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/renderer/render_thread.cc?r1=33933&r2=33932
M
http://src.chromium.org/viewvc/chrome/trunk/src/net/base/connection_type_histograms.cc?r1=33933&r2=33932
M
http://src.chromium.org/viewvc/chrome/trunk/src/net/base/mime_sniffer.cc?r1=33933&r2=33932
M
http://src.chromium.org/viewvc/chrome/trunk/src/net/base/sdch_manager.cc?r1=33933&r2=33932
M
http://src.chromium.org/viewvc/chrome/trunk/src/net/disk_cache/histogram_macros.h?r1=33933&r2=33932
M
http://src.chromium.org/viewvc/chrome/trunk/src/net/disk_cache/stats.cc?r1=33933&r2=33932
M
http://src.chromium.org/viewvc/chrome/trunk/src/net/disk_cache/stats.h?r1=33933&r2=33932
M
http://src.chromium.org/viewvc/chrome/trunk/src/net/disk_cache/stats_histogram.cc?r1=33933&r2=33932
M
http://src.chromium.org/viewvc/chrome/trunk/src/net/disk_cache/stats_histogram.h?r1=33933&r2=33932
M
http://src.chromium.org/viewvc/chrome/trunk/src/net/ftp/ftp_network_transaction.cc?r1=33933&r2=33932
M
http://src.chromium.org/viewvc/chrome/trunk/src/net/ftp/ftp_server_type_histograms.cc?r1=33933&r2=33932
M
http://src.chromium.org/viewvc/chrome/trunk/src/net/http/http_network_transaction.cc?r1=33933&r2=33932
M
http://src.chromium.org/viewvc/chrome/trunk/src/net/socket_stream/socket_stream_metrics.cc?r1=33933&r2=33932
Use factory to create histograms, and refcounts to track lifetimes
This is CL patch 377028 by Raman Tenneti, with minor changes to
make the try-bots happier.
It is cleanup that better ensures lifetimes of histograms (making it harder
for users to abuse them).
bug=16495 (repairs leak induced by the first landing)
bug=18840 (should make leaks less possible)
tbr=raman.tenneti
Review URL: http://codereview.chromium.org/462027
------------------------------------------------------------------------
--
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 adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
