New issue
Advanced search Search tips

Issue 881631 link

Starred by 5 users
Status: Untriaged
Owner: ----
Cc:
rsesek@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Chrome triggers photo library access permission prompt at startup

Project Member Reported by reillyg@chromium.org, Sep 7 
Chrome Version: 69.0.3497.81	
OS: macOS 10.14 Mojave

What steps will reproduce the problem?
(1) Start Chrome.
(2)
(3)

What is the expected result?

No out-of-context permission prompts.

What happens instead?

"Google Chrome" would like to access your photos.

I believe that this issue is triggered by the Media Galleries code but do not have a machine running Mojave on which to attempt to reproduce. This report comes from a friend.

Comment 1 by reillyg@chromium.org, Sep 7

806027957_71837.jpg
14.7 KB View Download

Comment 2 by meh...@chromium.org, Nov 28 

 Issue 909733  has been merged into this issue.

Comment 3 by meh...@chromium.org, Nov 28

Cc: rsesek@chromium.org
Labels: -Pri-3 Pri-2
rsesek@: Any idea what is happening here? Searching for "mac photos" I found issue 850193. Could that one be related? Thanks :)

Comment 4 by pbos@chromium.org, Nov 28

on-startup-google-chrome-access-photos
234 KB View Download

Comment 5 by rsesek@chromium.org, Nov 28 

Thanks, I think that's coming from this thread. Why are we even accessing these files on startup when there's no user-initiated request for them?

    1647 Thread_12664: TaskSchedulerForegroundWorker
    + 1647 thread_start  (in libsystem_pthread.dylib) + 13  [0x7fff6bbfb445]
    +   1647 _pthread_start  (in libsystem_pthread.dylib) + 70  [0x7fff6bbff2a7]
    +     1647 _pthread_body  (in libsystem_pthread.dylib) + 126  [0x7fff6bbfc339]
    +       1647 base::(anonymous namespace)::ThreadFunc(void*)  (in Google Chrome Framework)  load address 0x109280000 + 0x285ac97  [platform_thread_posix.cc:83]
    +         1647 base::internal::SchedulerWorker::RunPooledWorker()  (in Google Chrome Framework)  load address 0x109280000 + 0x2812d74  [scheduler_worker.cc:0]
    +           1647 base::internal::SchedulerWorker::RunWorker()  (in Google Chrome Framework)  load address 0x109280000 + 0x2812fb3  [type_traits:4515]
    +             1647 base::internal::TaskTracker::RunAndPopNextTask(scoped_refptr<base::internal::Sequence>, base::internal::CanScheduleSequenceObserver*)  (in Google Chrome Framework)  load address 0x109280000 + 0x281aa8e  [task_tracker.cc:503]
    +               1647 base::internal::TaskTrackerPosix::RunOrSkipTask(base::internal::Task, base::internal::Sequence*, base::TaskTraits const&, bool)  (in Google Chrome Framework)  load address 0x109280000 + 0x285a819  [task_tracker_posix.cc:24]
    +                 1647 base::internal::TaskTracker::RunOrSkipTask(base::internal::Task, base::internal::Sequence*, base::TaskTraits const&, bool)  (in Google Chrome Framework)  load address 0x109280000 + 0x281b151  [trace_event.h:1231]
    +                   1647 base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*)  (in Google Chrome Framework)  load address 0x109280000 + 0x27a39f5  [callback.h:99]
    +                     1647 base::internal::Invoker<base::internal::BindState<void (NativeMediaFileUtil::Core::*)(std::__1::unique_ptr<storage::FileSystemOperationContext, std::__1::default_delete<storage::FileSystemOperationContext> >, storage::FileSystemURL const&, base::RepeatingCallback<void (base::File::Error, std::__1::vector<filesystem::mojom::DirectoryEntry, std::__1::allocator<filesystem::mojom::DirectoryEntry> >, bool)>), base::internal::UnretainedWrapper<NativeMediaFileUtil::Core>, std::__1::unique_ptr<storage::FileSystemOperationContext, std::__1::default_delete<storage::FileSystemOperationContext> >, storage::FileSystemURL, base::RepeatingCallback<void (base::File::Error, std::__1::vector<filesystem::mojom::DirectoryEntry, std::__1::allocator<filesystem::mojom::DirectoryEntry> >, bool)> >, void ()>::RunOnce(base::internal::BindStateBase*)  (in Google Chrome Framework)  load address 0x109280000 + 0x25e9352  [callback_internal.h:178]
    +                       1647 NativeMediaFileUtil::Core::ReadDirectoryOnTaskRunnerThread(std::__1::unique_ptr<storage::FileSystemOperationContext, std::__1::default_delete<storage::FileSystemOperationContext> >, storage::FileSystemURL const&, base::RepeatingCallback<void (base::File::Error, std::__1::vector<filesystem::mojom::DirectoryEntry, std::__1::allocator<filesystem::mojom::DirectoryEntry> >, bool)>)  (in Google Chrome Framework)  load address 0x109280000 + 0x25e7a0c  [native_media_file_util.cc:550]
    +                         1647 NativeMediaFileUtil::Core::ReadDirectorySync(storage::FileSystemOperationContext*, storage::FileSystemURL const&, std::__1::vector<filesystem::mojom::DirectoryEntry, std::__1::allocator<filesystem::mojom::DirectoryEntry> >*)  (in Google Chrome Framework)  load address 0x109280000 + 0x25e8c36  [string:1413]
    +                           1647 base::FileEnumerator::Next()  (in Google Chrome Framework)  load address 0x109280000 + 0x285402e  [file_enumerator_posix.cc:0]
    +                             1647 __opendir2$INODE64  (in libsystem_c.dylib) + 49  [0x7fff6ba8111d]
    +                               1647 __open_nocancel  (in libsystem_kernel.dylib) + 10  [0x7fff6bb43b6e]
►

Sign in to add a comment