Previous Thread
Next Thread
Print Thread
Page 1 of 2 1 2
#110202 - 07/06/17 10:38 PM QMC2 mame_xml_cache_metadata update crash  
Joined: Jul 2017
Posts: 8
simon0117 Offline
Member
simon0117  Offline
Member

Joined: Jul 2017
Posts: 8
I was running QMC2 for mac OS X in January this year. I decided to install the latest release, 0.186 . Seemed to run fine IIRC. Then I also installed MAME 0187 and configured QMC2 to the correct MAME directory/executable. Now when I launch QMC2 I get a lot of warnings and after a couple of minutes it crashes.


Code
17:28:45.569: M.A.M.E. Catalog / Launcher II v0.186 (Qt 4.8.7, SDLMAME, Darwin x86_64)
17:28:45.596: Phonon features enabled - using Phonon v4.4.0
17:28:45.597: SDL joystick support enabled - using SDL v2.0.4
17:28:45.597: processing global emulator configuration
17:28:45.600: creating template configuration map
17:28:45.626: template info: emulator = SDLMAME, version = 0.186, format = 0.2.9
17:28:46.007: image cache size set to 64 MB
17:28:46.123: shortcut map is clean
17:28:46.124: joystick map is clean
17:28:46.825: WARNING: failed to fetch 'dtd' from XML cache database: query = 'SELECT dtd FROM mame_xml_cache_metadata WHERE row=0', error = 'No query Unable to fetch row'
17:28:46.839: WARNING: failed to fetch 'id' from XML cache database: query = 'SELECT id FROM mame_xml_cache WHERE id=:id LIMIT 1', error = ' Parameter count mismatch'
17:28:46.840: WARNING: failed to fetch 'xml' from XML cache database: query = 'SELECT xml FROM mame_xml_cache WHERE id=:id', error = ' Parameter count mismatch'
17:28:46.851: WARNING: failed to fetch 'id' from XML cache database: query = 'SELECT id FROM mame_xml_cache WHERE id=:id LIMIT 1', error = ' Parameter count mismatch'
17:28:46.852: WARNING: failed to fetch 'xml' from XML cache database: query = 'SELECT xml FROM mame_xml_cache WHERE id=:id', error = ' Parameter count mismatch'
17:28:46.865: WARNING: failed to fetch 'id' from XML cache database: query = 'SELECT id FROM mame_xml_cache WHERE id=:id LIMIT 1', error = ' Parameter count mismatch'
17:28:46.866: WARNING: failed to fetch 'xml' from XML cache database: query = 'SELECT xml FROM mame_xml_cache WHERE id=:id', error = ' Parameter count mismatch'
...
...
17:31:28.183: WARNING: failed to fetch 'id' from XML cache database: query = 'SELECT id FROM mame_xml_cache WHERE id=:id LIMIT 1', error = ' Parameter count mismatch'
17:31:28.184: WARNING: failed to fetch 'xml' from XML cache database: query = 'SELECT xml FROM mame_xml_cache WHERE id=:id', error = ' Parameter count mismatch'
17:31:28.193: done (loading XML data and recreating cache, elapsed time = 02:42.643)
17:31:28.196: WARNING: can't open ROM state cache, please check ROMs
17:31:28.197: processing machine list
17:31:28.204: pre-caching icons from directory
17:31:28.243: done (pre-caching icons from directory, elapsed time = 00:00.037)
17:31:28.244: 0 icons loaded
17:31:28.245: parsing machine data and recreating machine list cache
17:31:28.247: WARNING: failed to remove machine list database: query = 'DROP INDEX IF EXISTS mame_machine_list_index', error = 'database disk image is malformed Unable to execute statement'
17:31:28.249: WARNING: failed to fetch 'emu_version' from machine list database: query = 'SELECT emu_version FROM mame_machine_list_metadata WHERE row=0', error = 'No query Unable to fetch row'
17:31:28.251: WARNING: failed to fetch 'qmc2_version' from machine list database: query = 'SELECT qmc2_version FROM mame_machine_list_metadata WHERE row=0', error = 'No query Unable to fetch row'
17:31:28.252: WARNING: failed to fetch 'machinelist_version' from machine list database: query = 'SELECT machinelist_version FROM mame_machine_list_metadata WHERE row=0', error = 'No query Unable to fetch row'
17:31:28.254: WARNING: failed to fetch row count from XML cache database: query = 'SELECT COUNT(*) FROM mame_xml_cache', error = 'database disk image is malformed Unable to execute statement'
17:31:28.256: sorting machine list by machine description in ascending order
17:31:28.258: done (processing machine list, elapsed time = 00:00.060)
17:31:28.259: 200 machines, 0 BIOS sets and 0 devices loaded
17:31:28.260: WARNING: machine list cache is out of date, invalidating machine list cache
17:31:28.262: WARNING: failed to remove machine list database: query = 'DROP INDEX IF EXISTS mame_machine_list_index', error = 'database disk image is malformed Unable to execute statement'
17:31:28.263: ROM state info: L:200 C:? M:? I:? N:? U:0
17:31:28.265: WARNING: ROM state cache is incomplete or not up to date, please re-check ROMs
17:31:28.266: applying ROM state filter
17:31:28.269: done (applying ROM state filter, elapsed time = 00:00.002)
17:31:28.270: loading favorites and play history
17:31:28.283: done (loading favorites and play history)
17:31:28.284: total start-up time: 02:42.715


It used to crash before, but this time I brought up the Options dialog to mess around with the MAME directory settings to go back to the previous version, this time QMC2 completed but no ROMs or even Favorites listed.

I'll try and mess around with previous version of MAME and other stuff later, but hopefully someone can explain what's going wrong here and how it should be fixed. And the "correct" update procedure (for mac OS X) would be appreciated.

#110203 - 07/06/17 10:46 PM Re: QMC2 mame_xml_cache_metadata update crash [Re: simon0117]  
Joined: Jul 2017
Posts: 8
simon0117 Offline
Member
simon0117  Offline
Member

Joined: Jul 2017
Posts: 8
FWIW it crashed again when I restarted it. Here's the error report (start of it)

Code
Process:               qmc2-sdlmame [21161]
Path:                  /Applications/qmc2/qmc2-sdlmame.app/Contents/MacOS/qmc2-sdlmame
Identifier:            net.batcom-it.qmc2.qmc2-sdlmame
Version:               0.186 (0)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           qmc2-sdlmame [21161]
User ID:               501

Date/Time:             2017-07-06 17:43:43.018 -0500
OS Version:            Mac OS X 10.12.5 (16F73)
Report Version:        12
Anonymous UUID:        413CD336-A86D-ECDC-754B-531FE68C8083

Sleep/Wake UUID:       B67223BE-F1A9-453A-90D3-5F60C340DEC6

Time Awake Since Boot: 120000 seconds
Time Since Wake:       72000 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000008
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [0]

VM Regions Near 0x8:
--> 
    __TEXT                 0000000100000000-0000000100ac0000 [ 10.8M] r-x/rwx SM=COW  /Applications/qmc2/qmc2-sdlmame.app/Contents/MacOS/qmc2-sdlmame

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   QtCore                        	0x0000000100d74e4a QProcess::readAllStandardOutput() + 16
1   net.batcom-it.qmc2.qmc2-sdlmame	0x0000000100249775 MachineList::loadReadyReadStandardOutput() + 453
2   QtCore                        	0x0000000100de7d93 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) + 2207
3   QtCore                        	0x0000000100d7395d 0x100cd1000 + 665949
4   QtCore                        	0x0000000100d75be9 0x100cd1000 + 674793
5   QtCore                        	0x0000000100de7d93 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) + 2207
6   QtCore                        	0x0000000100e291d4 QSocketNotifier::activated(int) + 60
7   QtCore                        	0x0000000100dec843 QSocketNotifier::event(QEvent*) + 387
8   QtGui                         	0x000000010256155e QApplicationPrivate::notify_helper(QObject*, QEvent*) + 194
9   QtGui                         	0x0000000102563eb4 QApplication::notify(QObject*, QEvent*) + 6146
10  QtCore                        	0x0000000100dd34f6 QCoreApplication::notifyInternal(QObject*, QEvent*) + 118
11  QtGui                         	0x000000010251e126 0x1024e7000 + 225574
12  com.apple.CoreFoundation      	0x00007fffcf2df889 __CFSocketPerformV0 + 985
13  com.apple.CoreFoundation      	0x00007fffcf2c1321 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
14  com.apple.CoreFoundation      	0x00007fffcf2a2197 __CFRunLoopDoSources0 + 423
15  com.apple.CoreFoundation      	0x00007fffcf2a1716 __CFRunLoopRun + 934
16  com.apple.CoreFoundation      	0x00007fffcf2a1114 CFRunLoopRunSpecific + 420
17  com.apple.HIToolbox           	0x00007fffce802ebc RunCurrentEventLoopInMode + 240
18  com.apple.HIToolbox           	0x00007fffce802cf1 ReceiveNextEventCommon + 432
19  com.apple.HIToolbox           	0x00007fffce802b26 _BlockUntilNextEventMatchingListInModeWithFilter + 71
20  com.apple.AppKit              	0x00007fffccd9ba54 _DPSNextEvent + 1120
21  com.apple.AppKit              	0x00007fffcd5177ee -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 2796
22  com.apple.AppKit              	0x00007fffccd903db -[NSApplication run] + 926
23  QtGui                         	0x000000010251eace 0x1024e7000 + 228046
24  QtCore                        	0x0000000100dd0bc7 QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 77
25  QtCore                        	0x0000000100dd0d41 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 365
26  QtCore                        	0x0000000100dd394b QCoreApplication::exec() + 199
27  net.batcom-it.qmc2.qmc2-sdlmame	0x000000010009f3ac main + 4540
28  net.batcom-it.qmc2.qmc2-sdlmame	0x0000000100006264 start + 52

#110207 - 07/07/17 01:31 PM Re: QMC2 mame_xml_cache_metadata update crash [Re: simon0117]  
Joined: May 2008
Posts: 4,838
qmc2 Offline
qmc2  Offline

Very Senior Member

Joined: May 2008
Posts: 4,838
Germany
I'm unable to test it on Mac OS X myself, but it looks like there were some issues with the SQLite3 module as it couldn't work with the XML cache DB and/or the database got corrupted somehow.

Please try running "/Applications/qmc2/qmc2-sdlmame.app/Contents/MacOS/qmc2-sdlmame -cc" from command line. This will recreate/reset all emulator related caches, including some databases.

If that doesn't help I would need access to a Mac which will take a few days.


A mind is like a parachute. It doesn't work unless it's open. [Frank Zappa]

We're searching for QMC2 translators and support for existing translations. Interested? See here!
#110236 - 07/09/17 04:23 PM Re: QMC2 mame_xml_cache_metadata update crash [Re: qmc2]  
Joined: Jul 2017
Posts: 8
simon0117 Offline
Member
simon0117  Offline
Member

Joined: Jul 2017
Posts: 8
I still got a segfault from the command line. The stack trace seems slightly different.

Code
Process:               qmc2-sdlmame [56729]
Path:                  /Applications/qmc2/qmc2-sdlmame.app/Contents/MacOS/qmc2-sdlmame
Identifier:            net.batcom-it.qmc2.qmc2-sdlmame
Version:               0.186 (0)
Code Type:             X86-64 (Native)
Parent Process:        bash [1238]
Responsible:           qmc2-sdlmame [56729]
User ID:               501

Date/Time:             2017-07-09 11:18:59.150 -0500
OS Version:            Mac OS X 10.12.5 (16F73)
Report Version:        12
Anonymous UUID:        413CD336-A86D-ECDC-754B-531FE68C8083

Sleep/Wake UUID:       B3472ABD-D658-4A9A-BB62-60BA0CB4D4B3

Time Awake Since Boot: 350000 seconds
Time Since Wake:       150000 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000008
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [0]

VM Regions Near 0x8:
--> 
    __TEXT                 0000000100000000-0000000100ac0000 [ 10.8M] r-x/rwx SM=COW  /Applications/qmc2/qmc2-sdlmame.app/Contents/MacOS/qmc2-sdlmame

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   QtCore                        	0x0000000100d74e4a QProcess::readAllStandardOutput() + 16
1   net.batcom-it.qmc2.qmc2-sdlmame	0x0000000100249775 MachineList::loadReadyReadStandardOutput() + 453
2   QtCore                        	0x0000000100de7d93 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) + 2207
3   QtCore                        	0x0000000100d7395d 0x100cd1000 + 665949
4   QtCore                        	0x0000000100d75be9 0x100cd1000 + 674793
5   QtCore                        	0x0000000100de7d93 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) + 2207
6   QtCore                        	0x0000000100e291d4 QSocketNotifier::activated(int) + 60
7   QtCore                        	0x0000000100dec843 QSocketNotifier::event(QEvent*) + 387
8   QtGui                         	0x000000010256155e QApplicationPrivate::notify_helper(QObject*, QEvent*) + 194
9   QtGui                         	0x0000000102563eb4 QApplication::notify(QObject*, QEvent*) + 6146
10  QtCore                        	0x0000000100dd34f6 QCoreApplication::notifyInternal(QObject*, QEvent*) + 118
11  QtGui                         	0x000000010251e126 0x1024e7000 + 225574
12  com.apple.CoreFoundation      	0x00007fffcf2df889 __CFSocketPerformV0 + 985
13  com.apple.CoreFoundation      	0x00007fffcf2c1321 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
14  com.apple.CoreFoundation      	0x00007fffcf2a2197 __CFRunLoopDoSources0 + 423
15  com.apple.CoreFoundation      	0x00007fffcf2a1716 __CFRunLoopRun + 934
16  com.apple.CoreFoundation      	0x00007fffcf2a1114 CFRunLoopRunSpecific + 420
17  com.apple.HIToolbox           	0x00007fffce802ebc RunCurrentEventLoopInMode + 240
18  com.apple.HIToolbox           	0x00007fffce802cf1 ReceiveNextEventCommon + 432
19  com.apple.HIToolbox           	0x00007fffce802b26 _BlockUntilNextEventMatchingListInModeWithFilter + 71
20  com.apple.AppKit              	0x00007fffccd9ba54 _DPSNextEvent + 1120
21  com.apple.AppKit              	0x00007fffcd5177ee -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 2796
22  com.apple.AppKit              	0x00007fffccd903db -[NSApplication run] + 926
23  QtGui                         	0x000000010251eace 0x1024e7000 + 228046
24  QtCore                        	0x0000000100dd0bc7 QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 77
25  QtCore                        	0x0000000100dd0d41 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 365
26  QtCore                        	0x0000000100dd394b QCoreApplication::exec() + 199
27  net.batcom-it.qmc2.qmc2-sdlmame	0x000000010009f3ac main + 4540
28  net.batcom-it.qmc2.qmc2-sdlmame	0x0000000100006264 start + 52

#110322 - 07/17/17 03:29 AM Re: QMC2 mame_xml_cache_metadata update crash [Re: qmc2]  
Joined: Jul 2017
Posts: 8
simon0117 Offline
Member
simon0117  Offline
Member

Joined: Jul 2017
Posts: 8
Is there anything else I can do to troubleshoot this?

#110330 - 07/17/17 02:23 PM Re: QMC2 mame_xml_cache_metadata update crash [Re: simon0117]  
Joined: May 2008
Posts: 4,838
qmc2 Offline
qmc2  Offline

Very Senior Member

Joined: May 2008
Posts: 4,838
Germany
Could you also post the front-end log from running "qmc2-sdlmame -cc", please? Judging from the above strack traces it's apparently crashing while reading / parsing the output from "mame -listxml" which is unexpected.

Can anyone else on Mac OS X reproduce this?


A mind is like a parachute. It doesn't work unless it's open. [Frank Zappa]

We're searching for QMC2 translators and support for existing translations. Interested? See here!
#110346 - 07/17/17 10:59 PM Re: QMC2 mame_xml_cache_metadata update crash [Re: qmc2]  
Joined: Jul 2017
Posts: 8
simon0117 Offline
Member
simon0117  Offline
Member

Joined: Jul 2017
Posts: 8
What is the front-end log? You mean the console output?

Code
$ /Applications/qmc2/qmc2-sdlmame.app/Contents/MacOS/qmc2-sdlmame -cc
Segmentation fault: 11

#110349 - 07/18/17 10:36 AM Re: QMC2 mame_xml_cache_metadata update crash [Re: simon0117]  
Joined: May 2008
Posts: 4,838
qmc2 Offline
qmc2  Offline

Very Senior Member

Joined: May 2008
Posts: 4,838
Germany
The front-end log is stored in the file ~/Library/Application Support/qmc2/qmc2-sdlmame.log. If the segmentation fault happens "late enough" it may contain some hints...

I meanwhile contacted David (our Mac OS X package maintainer) about it. He's currently busy & on the road but he'll test it himself at the weekend.


A mind is like a parachute. It doesn't work unless it's open. [Frank Zappa]

We're searching for QMC2 translators and support for existing translations. Interested? See here!
#110372 - 07/20/17 11:59 PM Re: QMC2 mame_xml_cache_metadata update crash [Re: qmc2]  
Joined: Jul 2017
Posts: 8
simon0117 Offline
Member
simon0117  Offline
Member

Joined: Jul 2017
Posts: 8
Thanks for the info. The log file is basically the same as I put in my original post.

Code
18:51:32.468: WARNING: failed to fetch row count from XML cache database: query = 'SELECT COUNT(*) FROM mame_xml_cache', error = 'database disk image is malformed Unable to execute statement'
18:51:32.471: sorting machine list by machine description in ascending order
18:51:32.473: done (processing machine list, elapsed time = 00:00.072)
18:51:32.478: 265 machines, 0 BIOS sets and 0 devices loaded
18:51:32.480: WARNING: machine list cache is out of date, invalidating machine list cache
18:51:32.482: WARNING: failed to remove machine list database: query = 'DROP INDEX IF EXISTS mame_machine_list_index', error = 'database disk image is malformed Unable to execute statement'
18:51:32.484: ROM state info: L:265 C:? M:? I:? N:? U:0
18:51:32.485: WARNING: ROM state cache is incomplete or not up to date, please re-check ROMs
18:51:32.486: applying ROM state filter
18:51:32.504: done (applying ROM state filter, elapsed time = 00:00.016)
18:51:32.507: loading favorites and play history
18:51:32.516: done (loading favorites and play history)
18:51:32.517: total start-up time: 03:12.676


Note that I have a lot more than 265 ROMs

Are you sure this is a mac OS X thing? Could it be tested with a previous version of MAME from January and switching to the latest?

I don't suppose I can attach files to posts here. I'd be happy to share db or xml files if you let me know where and how.

#110386 - 07/21/17 11:30 AM Re: QMC2 mame_xml_cache_metadata update crash [Re: simon0117]  
Joined: May 2008
Posts: 4,838
qmc2 Offline
qmc2  Offline

Very Senior Member

Joined: May 2008
Posts: 4,838
Germany
So there's still something wrong with the XML cache DB. I thought that starting with "-cc" (cache clear) would fix that, but it apparently can't reset the DB (= drop tables & indexes) when the DB file is somehow corrupt. I dunno what might have caused it, but I doubt it has something to do with switching to the newer MAME version. You could however remove the DB file completely so it will be recreated from scratch during the next start-up ("rm ~/Library/Application Support/qmc2/mame-xml-cache.db").


A mind is like a parachute. It doesn't work unless it's open. [Frank Zappa]

We're searching for QMC2 translators and support for existing translations. Interested? See here!
#110390 - 07/21/17 02:35 PM Re: QMC2 mame_xml_cache_metadata update crash [Re: simon0117]  
Joined: May 2008
Posts: 4,838
qmc2 Offline
qmc2  Offline

Very Senior Member

Joined: May 2008
Posts: 4,838
Germany
Originally Posted by qmc2
So there's still something wrong with the XML cache DB. I thought that starting with "-cc" (cache clear) would fix that, but it apparently can't reset the DB (= drop tables & indexes) when the DB file is somehow corrupt. I dunno what might have caused it, but I doubt it has something to do with switching to the newer MAME version. You could however remove the DB file completely so it will be recreated from scratch during the next start-up ("rm ~/Library/Application Support/qmc2/mame-xml-cache.db").

Oh, and since your "machine list DB" file also seems to be corrupt, please remove that as well smile ("rm ~/Library/Application Support/qmc2/mame-machine-list.db").


A mind is like a parachute. It doesn't work unless it's open. [Frank Zappa]

We're searching for QMC2 translators and support for existing translations. Interested? See here!
#110398 - 07/22/17 04:14 PM Re: QMC2 mame_xml_cache_metadata update crash [Re: qmc2]  
Joined: Jul 2017
Posts: 8
simon0117 Offline
Member
simon0117  Offline
Member

Joined: Jul 2017
Posts: 8
Trashing those 2 files seemed to work, thanks. It says I should rescan my ROMs though, which is fine.

Not sure if it's related to this issue or not, but I launched a machine (Time Pilot) and my high scores were gone, i.e. didn't load from the last saved state. I assume it's somewhere in my previous MAME directory. But when I looked at my MAME folders along with the new mame0187-64bit folder was a folder named mame0187\-64bit containing cfg and sta folders. My working directory configured in QMC2 is /Users/simon/mame0187-64bit/

What is the suggested upgrade path for new versions of MAME and new versions of QMC2? It's still current a mystery why my DB files got corrupted after I attempted to upgrade both of these apps.

#110404 - 07/23/17 08:29 AM Re: QMC2 mame_xml_cache_metadata update crash [Re: simon0117]  
Joined: May 2008
Posts: 4,838
qmc2 Offline
qmc2  Offline

Very Senior Member

Joined: May 2008
Posts: 4,838
Germany
Originally Posted by simon0117
What is the suggested upgrade path for new versions of MAME and new versions of QMC2? It's still current a mystery why my DB files got corrupted after I attempted to upgrade both of these apps.

Well, the best upgrade method would be to just install the newer MAME version, point QMC2 to it if required (i.e. I build MAME from source and thus always use the same folder, but that's no requirement) and QMC2 will auto-detect that it's a new version and that it has to recreate some caches.


A mind is like a parachute. It doesn't work unless it's open. [Frank Zappa]

We're searching for QMC2 translators and support for existing translations. Interested? See here!
Page 1 of 2 1 2

Moderated by  qmc2 

Who's Online Now
0 registered members (), 17 guests, and 3 spiders.
Key: Admin, Global Mod, Mod
Shout Box
Forum Statistics
Forums9
Topics8,425
Posts109,185
Members4,759
Most Online225
May 26th, 2014
Powered by UBB.threads™ PHP Forum Software 7.6.0
Page Time: 0.033s Queries: 14 (0.010s) Memory: 5.0592 MB (Peak: 5.3120 MB) Zlib enabled. Server Time: 2017-10-17 06:00:49 UTC