Memory corruption while saving mhtml |
||||
Issue descriptionWe are trying to save a page as mhtml but its crashing SOMETIMES with below callstack ../third_party/WebKit/Source/platform/SharedBuffer.cpp:214 ../third_party/WebKit/Source/platform/SharedBuffer.h:119 ../third_party/WebKit/Source/platform/SharedBufferChunkReader.cpp:117 ../third_party/WebKit/Source/platform/mhtml/MHTMLParser.cpp:103 ../third_party/WebKit/Source/platform/mhtml/MHTMLParser.cpp:211 ../third_party/WebKit/Source/platform/mhtml/MHTMLArchive.cpp:81 ../third_party/WebKit/Source/core/fetch/ResourceFetcher.cpp:900 (discriminator 2) ../third_party/WebKit/Source/core/loader/DocumentLoader.cpp:589 (discriminator 2) ../third_party/WebKit/Source/core/loader/DocumentLoader.cpp:285 ../third_party/WebKit/Source/core/fetch/Resource.cpp:281 ../third_party/WebKit/Source/core/fetch/Resource.cpp:346 ../third_party/WebKit/Source/core/fetch/ResourceLoader.cpp:338 (discriminator 1) ../content/child/web_url_loader_impl.cc:763 (discriminator 1) ../content/child/resource_dispatcher.cc:399 ../base/tuple.h:166 (discriminator 8) ../content/child/resource_dispatcher.cc:525 (discriminator 3) ../content/child/resource_dispatcher.cc:137 ../base/bind_internal.h:159 (discriminator 2) ../base/callback.h:397 (discriminator 1) ../components/scheduler/base/task_queue_manager.cc:289 ../components/scheduler/base/task_queue_manager.cc:201 ../base/bind_internal.h:181 (discriminator 6) ../base/callback.h:397 (discriminator 1) ../base/message_loop/message_loop.cc:479 ../base/message_loop/message_loop.cc:488 ../base/message_loop/message_loop.cc:600 ../base/message_loop/message_pump_default.cc:33 ../base/run_loop.cc:35
,
Aug 2 2016
Yes. The issue is seen while opening a saved page. chorme version: 51.0.2704.106 Steps: 1. Fetch http://demo.easyrtc.com/demos/index.html 2. Select link for 'Simple Video+Audio' demo 3. select "connected users " which is shown below "The Demo" 4. Save as mhtml 5. Invoke the saved page
,
Aug 2 2016
Could you please attach the mhtml file from step 4? I tried the repro steps from #c2 (thanks!) and couldn't get a crash in 5 tries. Before digging deeper, it would be great if I could eliminate one possible difference between our repro steps/environments by making sure that I am using the same mhtml file that intermittently triggers a crash on your machine.
,
Aug 31 2016
,
Sep 7 2016
Thank you for providing more feedback. Adding requester "lukasza@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 7 2016
I tried the repro steps from #2 and couldn't reproduce the crash. Unfortunately, in absence of more specific steps this is not possible to conclusively investigate. |
||||
►
Sign in to add a comment |
||||
Comment 1 by lukasza@chromium.org
, Aug 1 2016Labels: Needs-Feedback