Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(71)

Issue 23961004: Avoid a write to NULL in ReadFieldBinary (Closed)

Created:
7 years, 3 months ago by cpu_(ooo_6.6-7.5)
Modified:
7 years, 3 months ago
CC:
chromium-reviews
Visibility:
Public.

Description

Avoid a write to NULL in ReadFieldBinary what happens is that we use vector_as_array(&data) which returns null if data is empty, but we don't check |size| whichcan be 0 so data.resize(size) still an empty vector. This is currently happening for browser_tests.exe in the waterfall. There might be a better fix but lots of tests are having exceptions so I want to stop that. TBR=mnissler BUG=none TEST=logs are clean Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=222177

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+2 lines, -0 lines) Patch
M chrome/browser/policy/preg_parser_win.cc View 1 chunk +2 lines, -0 lines 0 comments Download

Messages

Total messages: 4 (0 generated)
cpu_(ooo_6.6-7.5)
this is what we see in the bots Starting tests... IMPORTANT DEBUGGING NOTE: each test ...
7 years, 3 months ago (2013-09-10 01:47:17 UTC) #1
cpu_(ooo_6.6-7.5)
7 years, 3 months ago (2013-09-10 01:50:34 UTC) #2
cpu_(ooo_6.6-7.5)
Committed patchset #1 manually as r222177.
7 years, 3 months ago (2013-09-10 01:53:32 UTC) #3
Mattias Nissler (ping if slow)
7 years, 3 months ago (2013-09-11 13:42:24 UTC) #4
Message was sent while issue was closed.
Interesting. Do you happen to have preserved stack traces somewhere? This surely
needs a proper fix, but I'd be very interested to learn what triggered this as I
had never seen this problem before.

Powered by Google App Engine
This is Rietveld 408576698