search

google / sawbuck

Automatically exported from code.google.com/p/sawbuck
107 stars 40 forks source link

Syzygy breaking M18 official builds #43

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
See http://goto.google.com/zzign

[1229/164529:INFO:parse_engine_rpc.cc(85)] Processing 
'trace-chrome.exe-201111164115864-2567248.bin'.
[1229/164529:ERROR:parse_engine.cc(93)] Trying to insert conflicting module: 
\Device\HarddiskVolume2\b\build\slave\chrome-official\build\src\build\Release\in
strumented\chrome.dll (base=0x1883176960, size=34738176).
[1229/164529:ERROR:parse_engine.cc(93)] Trying to insert conflicting module: 
\Device\HarddiskVolume2\b\build\slave\chrome-official\build\src\build\Release\in
strumented\chrome.dll (base=0x1883176960, size=34738176).
[1229/164529:ERROR:reorderer.cc(386)] Relative(0x019BE2ED) maps to a non-code 
block (_bad_alloc_Message in 
\Device\HarddiskVolume2\b\build\slave\chrome-official\build\src\build\Release\in
strumented\chrome.dll).
[1229/164529:ERROR:parse_engine_rpc.cc(74)] Failed to consume 
'src\build\Release\call_traces\trace-chrome.exe-201111164115864-2567248.bin'.
[1229/164529:ERROR:reorderer.cc(255)] Failed to consume call trace events.
[1229/164529:ERROR:reorder_main.cc(182)] Reorder failed.
ERROR:__main__:Exception during Syzygy optimization.

Original issue reported on code.google.com by siggi@chromium.org on 30 Dec 2011 at 3:05

GoogleCodeExporter commented 8 years ago 
This is a bug in managing module information under PID reuse.
This will probably only manifests when there is heavy memory pressure, as under 
those conditions, Chrome.dll's section object is liable to get evicted from 
memory, and may get assigned another ASLR load address on next use.

The diagnosis of the issue was hindered due to a string formatting bug that 
obscured the trace file name PIDs. Fixed in 
http://code.google.com/p/sawbuck/source/browse/#svn/trunk590.

The list of PIDs processed was:
2912
1096
4632
4140
3432
4232
864
2596
3564
4836
4500
4196
3208
3932
4468
1500
2760
4912
4352
4732
908
4784
4952
920
4956
4472
864

Original comment by siggi@chromium.org on 30 Dec 2011 at 3:46

GoogleCodeExporter commented 8 years ago 
- http://codereview.appspot.com/5504098/
  Clean up process info when call-trace file ends.

- http://codereview.appspot.com/5505087/
  Mark and remove dirty module information during trace parsing.

Original comment by rog...@chromium.org on 3 Jan 2012 at 6:54

GoogleCodeExporter commented 8 years ago 
Fixed, by the above-mentioned CLs.

Original comment by rog...@chromium.org on 25 Jan 2012 at 6:53