Closed GoogleCodeExporter closed 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
- 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
Fixed, by the above-mentioned CLs.
Original comment by rog...@chromium.org
on 25 Jan 2012 at 6:53
Original issue reported on code.google.com by
siggi@chromium.org
on 30 Dec 2011 at 3:05