Changing the cookies policy leading to a crash of the ChromeIOThread



  • Changing the cookies policy and reloading a page (like this forum) crash my application:

    Process:         Demobrowser [585]
    Path:            /Users/USER/*/Demobrowser.app/Contents/MacOS/Demobrowser
    Identifier:      com.trolltech.DemoBrowser
    Version:         0
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [158]
    Responsible:     Demobrowser [585]
    User ID:         501
    
    Date/Time:       2017-01-20 11:37:22.323 +0100
    OS Version:      Mac OS X 10.9.5 (13F1134)
    Report Version:  11
    Anonymous UUID:  11371FC9-671B-614C-6529-56520F6DD7AA
    
    
    Crashed Thread:  13  Chrome_IOThread
    
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: EXC_I386_GPFLT
    
    Thread 0:: CrBrowserMain  Dispatch queue: com.apple.main-thread
    0   libsystem_kernel.dylib        	0x0000000110928a1a mach_msg_trap + 10
    1   libsystem_kernel.dylib        	0x0000000110927d18 mach_msg + 64
    2   com.apple.CoreFoundation      	0x000000010cfedf15 __CFRunLoopServiceMachPort + 181
    3   com.apple.CoreFoundation      	0x000000010cfed539 __CFRunLoopRun + 1161
    4   com.apple.CoreFoundation      	0x000000010cfece75 CFRunLoopRunSpecific + 309
    5   com.apple.HIToolbox           	0x000000010e2aaa0d RunCurrentEventLoopInMode + 226
    6   com.apple.HIToolbox           	0x000000010e2aa7b7 ReceiveNextEventCommon + 479
    7   com.apple.HIToolbox           	0x000000010e2aa5bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
    8   com.apple.AppKit              	0x000000010bc9224e _DPSNextEvent + 1434
    9   com.apple.AppKit              	0x000000010bc9189b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
    10  com.apple.AppKit              	0x000000010bc8599c -[NSApplication run] + 553
    11  libqcocoa.dylib               	0x00000001185096bf QCocoaEventDispatcher::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 2143
    12  org.qt-project.QtCore         	0x000000010a0c59d1 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 401
    13  org.qt-project.QtCore         	0x000000010a0c9c35 QCoreApplication::exec() + 341
    14  com.trolltech.DemoBrowser     	0x0000000104f71097 main + 183 (main.cpp:64)
    15  libdyld.dylib                 	0x000000011078e5fd start + 1
    
    
    Thread 13 Crashed:: Chrome_IOThread
    0   ???                           	0x00000001077b5e50 0 + 4420492880
    1   ???                           	0x00000001077b4891 0 + 4420487313
    2   ???                           	0x00000001077aef40 0 + 4420464448
    3   ???                           	0x00000001077b07e5 0 + 4420470757
    4   ???                           	0x00000001078ee6e0 0 + 4421773024
    5   ???                           	0x00000001078efd90 0 + 4421778832
    6   ???                           	0x00000001078f0aeb 0 + 4421782251
    7   ???                           	0x00000001078e7c9e 0 + 4421745822
    8   ???                           	0x0000000105e5c1c8 0 + 4393910728
    9   ???                           	0x00000001079bf555 0 + 4422628693
    10  ???                           	0x0000000105e5c588 0 + 4393911688
    11  ???                           	0x0000000105e92d33 0 + 4394134835
    12  ???                           	0x0000000105e8200d 0 + 4394065933
    13  ???                           	0x0000000106aa5858 0 + 4406794328
    14  ???                           	0x0000000105eb13e9 0 + 4394259433
    15  ???                           	0x0000000105ead1dc 0 + 4394242524
    16  libsystem_pthread.dylib       	0x0000000110a37899 _pthread_body + 138
    17  libsystem_pthread.dylib       	0x0000000110a3772a _pthread_start + 137
    18  libsystem_pthread.dylib       	0x0000000110a3bfc9 thread_start + 13
    

    I tried the same thing with the DemoBrowser and it crashs as well ...
    The only possible way is to relaunch the application after modifing the cookies settings in the Preferences dialog.

    May i fill a bug report ?
    Qt 5.7.1 OSX 10.9.5


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.