New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 16 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Sep 2010
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 0
Type: Bug-Security
M-6

Restricted
  • Only users with EditIssue permission may comment.



Sign in to add a comment
link

Issue 50428: Browser crash @ TabContents::ExpireInfoBars

Reported by sh...@chromium.org, Jul 27 2010 Project Member

Issue description

Possibly a variant of  Issue 47669 .  Broken out because that issue is closed, and this is happening on the Mac dev channel.  I believe that the fix for that issue is in 472.4, so logging a new issue for triage purposes.

http://crash/reportdetail?reportid=702236afa258a1a1

Thread 0 *CRASHED* ( EXC_BAD_ACCESS / KERN_PROTECTION_FAILURE @ 0x00000000 )

0xa07616a4			
0x005fe1b6	 [Google Chrome Framework	 - tab_contents.cc:1462]	TabContents::ExpireInfoBars
0x00600931	 [Google Chrome Framework	 - tab_contents.cc:3008]	TabContents::Observe
0x00062b2b	 [Google Chrome Framework	 - notification_service.cc:119]	NotificationService::Notify
0x005e99e3	 [Google Chrome Framework	 - navigation_controller.cc:1073]	NavigationController::NotifyNavigationEntryCommitted
0x005ed17b	 [Google Chrome Framework	 - navigation_controller.cc:592]	NavigationController::RendererDidNavigate
0x0060535c	 [Google Chrome Framework	 - tab_contents.cc:2323]	TabContents::DidNavigate
0x004e4684	 [Google Chrome Framework	 - render_view_host.cc:987]	RenderViewHost::OnMsgNavigate
0x004e7798	 [Google Chrome Framework	 - render_view_host.cc:709]	RenderViewHost::OnMessageReceived
0x004c9eb2	 [Google Chrome Framework	 - browser_render_process_host.cc:844]	BrowserRenderProcessHost::OnMessageReceived
0x00f3a9ea	 [Google Chrome Framework	 - ../base/tuple.h:422]	RunnableMethod<IPC::ChannelProxy::Context,void (IPC::ChannelProxy::Context::*)(const IPC::Message&),Tuple1<IPC::Message> >::Run
0x0078984b	 [Google Chrome Framework	 - message_loop.cc:409]	MessageLoop::RunTask
0x007899fd	 [Google Chrome Framework	 - message_loop.cc:418]	MessageLoop::DeferOrRunPendingTask
0x0078aa6a	 [Google Chrome Framework	 - message_loop.cc:525]	MessageLoop::DoWork
0x007b6af3	 [Google Chrome Framework	 - message_pump_mac.mm:291]	base::MessagePumpCFRunLoopBase::RunWorkSource
0x95f6c15a	 [CoreFoundation	 + 0x0003f15a]	__CFRunLoopDoSources0
0x95f69c1e	 [CoreFoundation	 + 0x0003cc1e]	__CFRunLoopRun
0x95f690f3	 [CoreFoundation	 + 0x0003c0f3]	CFRunLoopRunSpecific
0x95f68f20	 [CoreFoundation	 + 0x0003bf20]	CFRunLoopRunInMode
0x93fe30fb	 [HIToolbox	 + 0x000350fb]	RunCurrentEventLoopInMode
0x93fe2eb0	 [HIToolbox	 + 0x00034eb0]	ReceiveNextEventCommon
0x93fe2d35	 [HIToolbox	 + 0x00034d35]	BlockUntilNextEventMatchingListInMode
0x94658134	 [AppKit	 + 0x00048134]	_DPSNextEvent
0x94657975	 [AppKit	 + 0x00047975]	-[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
0x94619bee	 [AppKit	 + 0x00009bee]	-[NSApplication run]
0x007b659c	 [Google Chrome Framework	 - message_pump_mac.mm:677]	base::MessagePumpNSApplication::DoRun
0x007b5d29	 [Google Chrome Framework	 - message_pump_mac.mm:213]	base::MessagePumpCFRunLoopBase::Run
0x0078a423	 [Google Chrome Framework	 - message_loop.cc:257]	MessageLoop::Run
0x001483b7	 [Google Chrome Framework	 - browser_main.cc:355]	BrowserMain
0x00009fa1	 [Google Chrome Framework	 - chrome_dll_main.cc:889]	ChromeMain
0x00001f57	 [Google Chrome	 - chrome_exe_main.mm:16]	main
 

Comment 1 by mikesmith@chromium.org, Jul 28 2010

Status: Assigned

Comment 2 by pinkerton@chromium.org, Aug 11 2010

Labels: ReleaseBlock-Stable
top crash, stable blocker

Comment 3 by thestig@chromium.org, Aug 17 2010

Labels: -OS-Mac OS-All
Happens on all platforms:
Linux: http://crash/reportdetail?reportid=474a8556e087cfaf
Windows: http://crash/reportdetail?reportid=de614f20278395d3

Comment 4 by sh...@chromium.org, Aug 17 2010

Jay, any status on this?  It's not a very high-frequency crasher overall, but I worry that for users using the translate feature it might be pretty annoying.

Comment 5 by jcivelli@chromium.org, Aug 18 2010

Status: Started
I am working on it now, trying to repro.
Looks like we add a NULL infobar delegate at some point to the TabContents.

Comment 6 by kerz@chromium.org, Aug 23 2010

Any update on this?

Comment 7 by jcivelli@chromium.org, Aug 23 2010

I spent quite some time last week investigating.
It is fairly clear why we are crashing (there is a NULL infobar delegate in the tab contents), but I could not figure-out how this can possibly happen.
I landed a band-aid patch last week (trunk and M6 branch), but I am not entirely convinced it is going to fix it.

Comment 8 by kerz@chromium.org, Aug 23 2010

Assuming the patch was r56866 for M6.  Will watch to see on the next beta release.

Comment 9 by kerz@chromium.org, Aug 23 2010

Full details:

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=56944 

------------------------------------------------------------------------
r56944 | jcivelli@chromium.org | 2010-08-20 17:09:20 -0700 (Fri, 20 Aug 2010) | 13 lines
Changed paths:
   M http://src.chromium.org/viewvc/chrome/branches/472/src/chrome/browser/tab_contents/tab_contents.cc?r1=56944&r2=56943

Merging r56866 to M6 branch:
Original review:
http://codereview.chromium.org/3112022

A crasher in TabContent::ExpireInfoBars is consistently reported in the field. Somehow one of the infobar delegate is NULL.
After spending some time investigating, I am still not clear on how this can happen.
Applying a band-aid with a NOTREACHED() in the hope someone will be able to repro consistently.

BUG= 47669 
TEST=Don't know how to repro :-(
TBR=kerz

Review URL: http://codereview.chromium.org/3186022
------------------------------------------------------------------------

Comment 10 by jeffreyc@chromium.org, Aug 24 2010

The next step is for QA to test and see if that fixed it or not.

Comment 11 by kerz@chromium.org, Aug 25 2010

Labels: -ReleaseBlock-Stable
Pulling release block off, as we have a bandaid.  If we see this popup again we can re-tag it.

Comment 12 by kerz@chromium.org, Sep 2 2010

Status: Fixed
Calling this fixed.  No crashes in the latest beta with this signature that I saw.

Comment 13 by thestig@chromium.org, Sep 7 2010

Status: Assigned
I still see this on 6.0.472.53: http://crash/reportdetail?reportid=19223651bb39898c

It doesn't happen very often on Linux, but it's still a top crasher on Mac.

Comment 14 by thestig@chromium.org, Sep 20 2010

It no longer happens on the dev channel 7.x, but happens on 6.x still. I reproduced it on Linux with the instructions from  bug 56238 .

Comment 15 by thestig@chromium.org, Sep 20 2010

 Issue 56238  has been merged into this issue.

Comment 16 by bugdro...@gmail.com, Sep 21 2010

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=60095

------------------------------------------------------------------------
r60095 | jcivelli@chromium.org | Tue Sep 21 13:14:26 PDT 2010

Changed paths:
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/translate/translate_manager.cc?r1=60095&r2=60094&pathrev=60095
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/autofill/autofill_manager.cc?r1=60095&r2=60094&pathrev=60095
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/autofill/autofill_manager.h?r1=60095&r2=60094&pathrev=60095
 M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/autofill/autofill_cc_infobar_delegate.cc?r1=60095&r2=60094&pathrev=60095

Fix crasher with autofill infobar.
The "save credit card" information was deleted by the AutofillManager when the form is submitted but was still pointed to by the TabContents, causing a crasher when navigating.

BUG= 50428 
TEST=See steps in 56238.

Review URL: http://codereview.chromium.org/3466006
------------------------------------------------------------------------

Comment 17 by sunandt@chromium.org, Sep 21 2010

Labels: Security Restrict-View-SecurityTeam
Steps
-----
1. Launch the www.paypal.com.
2. Go to Profile and add the new credit card.
3. Go to Profile and try to confirm the new credit card.
4. Click Confirm button.
5. Click Confirm button again.

Boom Boom!!

Stack Trace
------------
ChildEBP RetAddr  
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012f0a4 01da0664 <Unloaded_S.DLL>+0x76580df
0012f0b8 01da30f3 chrome_1c30000!TabContents::ExpireInfoBars(struct NavigationController::LoadCommittedDetails * details = 0x00000005)+0x49 
0012f1a4 0200932d chrome_1c30000!TabContents::Observe(class NotificationType type = class NotificationType, class NotificationSource * source = 0x0012f1f8, class NotificationDetails * details 

= 0x0012f204)+0x165
0012f1d4 01dea7e8 chrome_1c30000!NotificationService::Notify(class NotificationType type = class NotificationType, class NotificationSource * source = 0x00000000, class NotificationDetails * 

details = 0x0012f204)+0x185
0012f1fc 01de9f1b chrome_1c30000!NavigationController::NotifyNavigationEntryCommitted(struct NavigationController::LoadCommittedDetails * details = 0x0012f2b0, int extra_invalidate_flags = 

124093216)+0x51
0012f278 01da1d3a chrome_1c30000!NavigationController::RendererDidNavigate(struct ViewHostMsg_FrameNavigate_Params * params = 0x0012f388, int extra_invalidate_flags = 0, struct 

NavigationController::LoadCommittedDetails * details = 0x0012f2b0)+0x19c 
0012f350 01de350a chrome_1c30000!TabContents::DidNavigate(class RenderViewHost * rvh = 0x011b5300, struct ViewHostMsg_FrameNavigate_Params * params = 0x0012f388)+0x133
0012f6f4 01de298c chrome_1c30000!RenderViewHost::OnMsgNavigate(class IPC::Message * msg = 0x076580e0)+0x18e 
0012f72c 01f0fcc7 chrome_1c30000!RenderViewHost::OnMessageReceived(class IPC::Message * msg = 0x07602280)+0x185 
0012f74c 01da7391 chrome_1c30000!BrowserRenderProcessHost::OnMessageReceived(class IPC::Message * msg = 0x07602280)+0x118 
0012f758 01cec070 chrome_1c30000!RunnableMethod<ChromeURLRequestContextGetter,void (void)+0x17 
0012f788 01cec0fc chrome_1c30000!MessageLoop::RunTask(class Task * task = 0x07602270)+0x97 
0012f798 01cec292 chrome_1c30000!MessageLoop::DeferOrRunPendingTask(struct MessageLoop::PendingTask * pending_task = 0x07658320)+0x28
0012f7c8 01cfd275 chrome_1c30000!MessageLoop::DoWork(void)+0x71 [c:\b\slave\chrome-official\build\src\base\message_loop.cc @ 525]
0012f7f8 01cfd08a chrome_1c30000!base::MessagePumpForUI::DoRunLoop(void)+0x52 
0012f814 01cebe14 chrome_1c30000!base::MessagePumpWin::RunWithDispatcher(class base::MessagePump::Delegate * delegate = 0x07658320, class base::MessagePumpWin::Dispatcher * dispatcher = 

0x0012f854)+0x38 
0012f820 01cebda4 chrome_1c30000!MessageLoop::RunInternal(void)+0x26 
0012f828 01cec4a3 chrome_1c30000!MessageLoop::RunHandler(void)+0x17 
0012f844 01d65632 chrome_1c30000!MessageLoopForUI::Run(class base::MessagePumpWin::Dispatcher * dispatcher = 0x0012f854)+0x21
0012f878 01d6701f chrome_1c30000!`anonymous namespace'::RunUIMessageLoop(class BrowserProcess * browser_process = 0x0012fcb0)+0x26

ExceptionAddress: 076580e0 (<Unloaded_S.DLL>+0x076580df)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000008aa
   Parameter[1]: 076580e0
Attempt to execute non-executable address 076580e0

Comment 18 by sunandt@chromium.org, Sep 21 2010

 Issue 55400  has been merged into this issue.

Comment 19 by jcivelli@chromium.org, Sep 21 2010

Status: Fixed
Fixed in r60095 on trunk and in r60103 on M7 branch.

Comment 20 by bugdro...@gmail.com, Sep 21 2010

The following revision refers to this bug:
    http://src.chromium.org/viewvc/chrome?view=rev&revision=60103

------------------------------------------------------------------------
r60103 | jcivelli@chromium.org | Tue Sep 21 14:15:03 PDT 2010

Changed paths:
 M http://src.chromium.org/viewvc/chrome/branches/517/src/chrome/browser/translate/translate_manager.cc?r1=60103&r2=60102&pathrev=60103
 M http://src.chromium.org/viewvc/chrome/branches/517/src/chrome/browser/autofill/autofill_manager.cc?r1=60103&r2=60102&pathrev=60103
 M http://src.chromium.org/viewvc/chrome/branches/517/src/chrome/browser/autofill/autofill_manager.h?r1=60103&r2=60102&pathrev=60103
 M http://src.chromium.org/viewvc/chrome/branches/517/src/chrome/browser/autofill/autofill_cc_infobar_delegate.cc?r1=60103&r2=60102&pathrev=60103

Landing r60095 to the M7 branch.
Original review:
http://codereview.chromium.org/3466006/show

Fix crasher with autofill infobar.
The "save credit card" information was deleted by the AutofillManager when the form is submitted but was still pointed to by the TabContents, causing a crasher when navigating.

BUG= 50428 
TEST=See steps in 56238. 
TBR=jhawkins

Review URL: http://codereview.chromium.org/3413026
------------------------------------------------------------------------

Comment 21 by infe...@chromium.org, Sep 21 2010

Labels: -Restrict-View-SecurityTeam Restrict-View-SecurityNotify SecSeverity-Critical
Status: FixUnreleased

Comment 22 by sunandt@chromium.org, Sep 21 2010

Shouldn't this be merged to M6 branch as well as we are seeing some reports of Chrome crashing whit similar steps(submitting again when infobar is present)? See issue 55686

Comment 23 by infe...@chromium.org, Sep 21 2010

Sunand, we won't have another security patch for v6. So, that is why merge to v6 is not required. If we do plan for one, we will try to get this in.

Comment 24 by sunandt@chromium.org, Sep 22 2010

Issue 55686 has been merged into this issue.

Comment 25 by jcivelli@chromium.org, Sep 22 2010

 Issue 54736  has been merged into this issue.

Comment 26 by sunandt@chromium.org, Oct 5 2010

 Issue 57991  has been merged into this issue.

Comment 27 by sunandt@chromium.org, Oct 7 2010

Issue 58314 has been merged into this issue.

Comment 28 by sunandt@chromium.org, Oct 12 2010

 Issue 58875  has been merged into this issue.

Comment 29 by sunandt@chromium.org, Oct 15 2010

 Issue 59339  has been merged into this issue.

Comment 30 by scarybea...@gmail.com, Nov 3 2010

Labels: -Restrict-View-SecurityNotify
Status: Fixed

Comment 31 by lafo...@chromium.org, Mar 18 2011

Labels: -Regression bulkmove Type-Regression
Possibly a variant of  Issue 47669 .  Broken out because that issue is closed, and this is happening on the Mac dev channel.  I believe that the fix for that issue is in 472.4, so logging a new issue for triage purposes.

http://crash/reportdetail?reportid=702236afa258a1a1

Thread 0 *CRASHED* ( EXC_BAD_ACCESS / KERN_PROTECTION_FAILURE @ 0x00000000 )

0xa07616a4			
0x005fe1b6	 [Google Chrome Framework	 - tab_contents.cc:1462]	TabContents::ExpireInfoBars
0x00600931	 [Google Chrome Framework	 - tab_contents.cc:3008]	TabContents::Observe
0x00062b2b	 [Google Chrome Framework	 - notification_service.cc:119]	NotificationService::Notify
0x005e99e3	 [Google Chrome Framework	 - navigation_controller.cc:1073]	NavigationController::NotifyNavigationEntryCommitted
0x005ed17b	 [Google Chrome Framework	 - navigation_controller.cc:592]	NavigationController::RendererDidNavigate
0x0060535c	 [Google Chrome Framework	 - tab_contents.cc:2323]	TabContents::DidNavigate
0x004e4684	 [Google Chrome Framework	 - render_view_host.cc:987]	RenderViewHost::OnMsgNavigate
0x004e7798	 [Google Chrome Framework	 - render_view_host.cc:709]	RenderViewHost::OnMessageReceived
0x004c9eb2	 [Google Chrome Framework	 - browser_render_process_host.cc:844]	BrowserRenderProcessHost::OnMessageReceived
0x00f3a9ea	 [Google Chrome Framework	 - ../base/tuple.h:422]	RunnableMethod&lt;IPC::ChannelProxy::Context,void (IPC::ChannelProxy::Context::*)(const IPC::Message&amp;),Tuple1&lt;IPC::Message&gt; &gt;::Run
0x0078984b	 [Google Chrome Framework	 - message_loop.cc:409]	MessageLoop::RunTask
0x007899fd	 [Google Chrome Framework	 - message_loop.cc:418]	MessageLoop::DeferOrRunPendingTask
0x0078aa6a	 [Google Chrome Framework	 - message_loop.cc:525]	MessageLoop::DoWork
0x007b6af3	 [Google Chrome Framework	 - message_pump_mac.mm:291]	base::MessagePumpCFRunLoopBase::RunWorkSource
0x95f6c15a	 [CoreFoundation	 + 0x0003f15a]	__CFRunLoopDoSources0
0x95f69c1e	 [CoreFoundation	 + 0x0003cc1e]	__CFRunLoopRun
0x95f690f3	 [CoreFoundation	 + 0x0003c0f3]	CFRunLoopRunSpecific
0x95f68f20	 [CoreFoundation	 + 0x0003bf20]	CFRunLoopRunInMode
0x93fe30fb	 [HIToolbox	 + 0x000350fb]	RunCurrentEventLoopInMode
0x93fe2eb0	 [HIToolbox	 + 0x00034eb0]	ReceiveNextEventCommon
0x93fe2d35	 [HIToolbox	 + 0x00034d35]	BlockUntilNextEventMatchingListInMode
0x94658134	 [AppKit	 + 0x00048134]	_DPSNextEvent
0x94657975	 [AppKit	 + 0x00047975]	-[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
0x94619bee	 [AppKit	 + 0x00009bee]	-[NSApplication run]
0x007b659c	 [Google Chrome Framework	 - message_pump_mac.mm:677]	base::MessagePumpNSApplication::DoRun
0x007b5d29	 [Google Chrome Framework	 - message_pump_mac.mm:213]	base::MessagePumpCFRunLoopBase::Run
0x0078a423	 [Google Chrome Framework	 - message_loop.cc:257]	MessageLoop::Run
0x001483b7	 [Google Chrome Framework	 - browser_main.cc:355]	BrowserMain
0x00009fa1	 [Google Chrome Framework	 - chrome_dll_main.cc:889]	ChromeMain
0x00001f57	 [Google Chrome	 - chrome_exe_main.mm:16]	main

Comment 32 by lafo...@chromium.org, Mar 19 2011

Labels: -Crash Stability-Crash
Possibly a variant of  Issue 47669 .  Broken out because that issue is closed, and this is happening on the Mac dev channel.  I believe that the fix for that issue is in 472.4, so logging a new issue for triage purposes.

http://crash/reportdetail?reportid=702236afa258a1a1

Thread 0 *CRASHED* ( EXC_BAD_ACCESS / KERN_PROTECTION_FAILURE @ 0x00000000 )

0xa07616a4			
0x005fe1b6	 [Google Chrome Framework	 - tab_contents.cc:1462]	TabContents::ExpireInfoBars
0x00600931	 [Google Chrome Framework	 - tab_contents.cc:3008]	TabContents::Observe
0x00062b2b	 [Google Chrome Framework	 - notification_service.cc:119]	NotificationService::Notify
0x005e99e3	 [Google Chrome Framework	 - navigation_controller.cc:1073]	NavigationController::NotifyNavigationEntryCommitted
0x005ed17b	 [Google Chrome Framework	 - navigation_controller.cc:592]	NavigationController::RendererDidNavigate
0x0060535c	 [Google Chrome Framework	 - tab_contents.cc:2323]	TabContents::DidNavigate
0x004e4684	 [Google Chrome Framework	 - render_view_host.cc:987]	RenderViewHost::OnMsgNavigate
0x004e7798	 [Google Chrome Framework	 - render_view_host.cc:709]	RenderViewHost::OnMessageReceived
0x004c9eb2	 [Google Chrome Framework	 - browser_render_process_host.cc:844]	BrowserRenderProcessHost::OnMessageReceived
0x00f3a9ea	 [Google Chrome Framework	 - ../base/tuple.h:422]	RunnableMethod&lt;IPC::ChannelProxy::Context,void (IPC::ChannelProxy::Context::*)(const IPC::Message&amp;),Tuple1&lt;IPC::Message&gt; &gt;::Run
0x0078984b	 [Google Chrome Framework	 - message_loop.cc:409]	MessageLoop::RunTask
0x007899fd	 [Google Chrome Framework	 - message_loop.cc:418]	MessageLoop::DeferOrRunPendingTask
0x0078aa6a	 [Google Chrome Framework	 - message_loop.cc:525]	MessageLoop::DoWork
0x007b6af3	 [Google Chrome Framework	 - message_pump_mac.mm:291]	base::MessagePumpCFRunLoopBase::RunWorkSource
0x95f6c15a	 [CoreFoundation	 + 0x0003f15a]	__CFRunLoopDoSources0
0x95f69c1e	 [CoreFoundation	 + 0x0003cc1e]	__CFRunLoopRun
0x95f690f3	 [CoreFoundation	 + 0x0003c0f3]	CFRunLoopRunSpecific
0x95f68f20	 [CoreFoundation	 + 0x0003bf20]	CFRunLoopRunInMode
0x93fe30fb	 [HIToolbox	 + 0x000350fb]	RunCurrentEventLoopInMode
0x93fe2eb0	 [HIToolbox	 + 0x00034eb0]	ReceiveNextEventCommon
0x93fe2d35	 [HIToolbox	 + 0x00034d35]	BlockUntilNextEventMatchingListInMode
0x94658134	 [AppKit	 + 0x00048134]	_DPSNextEvent
0x94657975	 [AppKit	 + 0x00047975]	-[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
0x94619bee	 [AppKit	 + 0x00009bee]	-[NSApplication run]
0x007b659c	 [Google Chrome Framework	 - message_pump_mac.mm:677]	base::MessagePumpNSApplication::DoRun
0x007b5d29	 [Google Chrome Framework	 - message_pump_mac.mm:213]	base::MessagePumpCFRunLoopBase::Run
0x0078a423	 [Google Chrome Framework	 - message_loop.cc:257]	MessageLoop::Run
0x001483b7	 [Google Chrome Framework	 - browser_main.cc:355]	BrowserMain
0x00009fa1	 [Google Chrome Framework	 - chrome_dll_main.cc:889]	ChromeMain
0x00001f57	 [Google Chrome	 - chrome_exe_main.mm:16]	main

Comment 33 by jsc...@chromium.org, Mar 21 2011

Labels: Type-Security

Comment 34 by jsc...@chromium.org, Oct 5 2011

Labels: SecImpacts-Stable
Batch update.

Comment 35 by bugdroid1@chromium.org, Oct 13 2012

Project Member
Labels: Restrict-AddIssueComment-Commit
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.

Comment 36 by bugdroid1@chromium.org, Mar 10 2013

Project Member
Labels: -Area-UI -Mstone-6 -SecSeverity-Critical -Type-Security -SecImpacts-Stable Security-Impact-Stable M-6 Cr-UI Type-Bug-Security Security-Severity-Critical

Comment 37 by bugdroid1@chromium.org, Mar 13 2013

Project Member
Labels: -Restrict-AddIssueComment-Commit Restrict-AddIssueComment-EditIssue

Comment 38 by bugdroid1@chromium.org, Mar 21 2013

Project Member
Labels: -Security-Impact-Stable Security_Impact-Stable

Comment 39 by bugdroid1@chromium.org, Mar 21 2013

Project Member
Labels: -Security-Severity-Critical Security_Severity-Critical

Comment 40 by sheriffbot@chromium.org, Oct 1 2016

Project Member
This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 41 by sheriffbot@chromium.org, Oct 2 2016

Project Member
This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 42 by mbarbe...@chromium.org, Oct 2 2016

Labels: allpublic

Comment 43 by sheriffbot@chromium.org, Jul 28 2018

Project Member
Labels: -Pri-1 Pri-0

Sign in to add a comment