PhantomJS 1.9.8 crash depends on moon position

I wrote a script which opens a given page and produces a har file. On some sites phantomjs 1.9.8 with the official binary is crashing on my sabayon linux. I am not able to reproduce the crash with the same binary on debian wheezy.
I now minimized the script until the crash disappeared and added back code until the phantomjs is crashing again.
I tested it with the alexa top 10 pages of Germany. On gmx.net and web.de phantomjs crashes frequently, but not on every test.
Bellow you can find the crash trace. Ask me to get a pcap of the request responsible for the crash and/or the script.
Operating system: Linux
                  0.0.0 Linux 3.12.0-sabayon #1 SMP Mon Oct 13 02:47:39 UTC 2014 x86_64
CPU: amd64
     family 6 model 42 stepping 7
     4 CPUs

Crash reason:  SIGSEGV
Crash address: 0x8

Thread 0 (crashed)
 0  0x7f95b400860f
    rbx = 0x00007f95fb6ce980   r12 = 0x0000000000000200
    r13 = 0x00007f95fb6ce980   r14 = 0xffff000000000000
    r15 = 0xffff000000000002   rip = 0x00007f95b400860f
    rsp = 0x00007fff92a82d10   rbp = 0x00007fff92a82db0
    Found by: given as instruction pointer in context
 1  libc-2.17.so + 0x3aa5bf
    rip = 0x00007f95fedeb5c0   rsp = 0x00007fff92a82d30
    rbp = 0x00007fff92a82db0
    Found by: stack scanning
 2  phantomjs!JSC::Interpreter::executeCall [JITCode.h : 77 + 0x16]
    rip = 0x0000000000f2e476   rsp = 0x00007fff92a82dc0
    Found by: stack scanning
 3  phantomjs!JSC::call [CallData.cpp : 38 + 0x21]
    rbx = 0x00007fff92a82ff0   r12 = 0x00007f95fb69fe20
    r13 = 0x00007f95fa9751d0   r14 = 0x00007f95fb6a4150
    r15 = 0x00007f9600197820   rip = 0x0000000000f72a1d
    rsp = 0x00007fff92a82e90   rbp = 0x00007f95a3ce0990
    Found by: call frame info
 4  phantomjs!JSC::Bindings::QtConnectionObject::execute [qt_runtime.cpp : 1863 + 0x17]
    rbx = 0x00007fff92a82ff0   r12 = 0x00007f95fb69fe20
    r13 = 0x00007f95fa9751d0   r14 = 0x00007f95fb6a4150
    r15 = 0x00007f9600197820   rip = 0x0000000000542fce
    rsp = 0x00007fff92a82ea0   rbp = 0x00007f95a3ce0990
    Found by: call frame info
 5  phantomjs!JSC::Bindings::QtConnectionObject::qt_metacall [qt_runtime.cpp : 1807 + 0xa]
    rbx = 0x0000000000000000   r12 = 0x00007fff92a83280
    r13 = 0x00000000038d1d70   r14 = 0x0000000000000004
    r15 = 0x0000000003903d90   rip = 0x0000000000543a0c
    rsp = 0x00007fff92a83120   rbp = 0x0000000000000000
    Found by: call frame info
 6  phantomjs!QMetaObject::activate [qobject.cpp : 3555 + 0x1f]
    rbx = 0x0000000000000004   r12 = 0x00000000038d4e01
    r13 = 0x0000000000000000   r14 = 0x0000000000000004
    r15 = 0x0000000003903d90   rip = 0x0000000001cf7260
    rsp = 0x00007fff92a83150   rbp = 0x00000000038d1d70
    Found by: call frame info
 7  phantomjs!WebPage::resourceRequested [moc_webpage.cpp : 456 + 0x4]
    rbx = 0x0000000000000004   r12 = 0x00000000038d4e00
    r13 = 0x000000000046a310   r14 = 0x0000000000000006
    r15 = 0x0000000003905be0   rip = 0x000000000046a1a5
    rsp = 0x00007fff92a83270   rbp = 0x00007fff92a83510
    Found by: call frame info
 8  phantomjs!WebPage::qt_static_metacall [moc_webpage.cpp : 213 + 0xf]
    rbx = 0x0000000000000004   r12 = 0x00000000038d4e00
    r13 = 0x000000000046a310   r14 = 0x0000000000000006
    r15 = 0x0000000003905be0   rip = 0x000000000046ab8c
    rsp = 0x00007fff92a832b0   rbp = 0x00007fff92a83510
    Found by: call frame info
 9  phantomjs!QMetaObject::activate [qobject.cpp : 3539 + 0x1e]
    rbx = 0x0000000000000004   r12 = 0x00007fff92a83801
    r13 = 0x000000000046a310   r14 = 0x0000000000000006
    r15 = 0x0000000003905be0   rip = 0x0000000001cf6ff8
    rsp = 0x00007fff92a833e0   rbp = 0x00000000038d4e00
    Found by: call frame info
10  phantomjs!NetworkAccessManager::resourceRequested [moc_networkaccessmanager.cpp : 264 + 0x4]
    rbx = 0x00007fff92a836a0   r12 = 0x00007fff92a838a0
    r13 = 0x00007fff92a83720   r14 = 0x00007fff92a835e0
    r15 = 0x00007fff92a83750   rip = 0x000000000046c5f2
    rsp = 0x00007fff92a83500   rbp = 0x00007fff92a83690
    Found by: call frame info
11  phantomjs!NetworkAccessManager::createRequest [networkaccessmanager.cpp : 240 + 0x22]
    rbx = 0x00007fff92a836a0   r12 = 0x00007fff92a838a0
    r13 = 0x00007fff92a83720   r14 = 0x00007fff92a835e0
    r15 = 0x00007fff92a83750   rip = 0x000000000042d137
    rsp = 0x00007fff92a83540   rbp = 0x00007fff92a83690
    Found by: call frame info
12  phantomjs!QNetworkAccessManager::get [qnetworkaccessmanager.cpp : 598 + 0xc]
    rbx = 0x00000000039032b0   r12 = 0x00000000041dc6d8
    r13 = 0x0000000003e4b4c0   r14 = 0x00000000039032b0
    r15 = 0x0000000000000000   rip = 0x0000000001b0ef74
    rsp = 0x00007fff92a839c0   rbp = 0x00000000041dc6b0
    Found by: call frame info
13  phantomjs!WebCore::QNetworkReplyHandler::sendNetworkRequest [QNetworkReplyHandler.cpp : 634 + 0xa]
    rbx = 0x00007fff92a83a10   r12 = 0x00000000041dc6d8
    r13 = 0x0000000003e4b4c0   r14 = 0x00000000039032b0
    r15 = 0x0000000000000000   rip = 0x0000000000adcdb2
    rsp = 0x00007fff92a839d0   rbp = 0x00000000041dc6b0
    Found by: call frame info
14  phantomjs!WebCore::QNetworkReplyHandler::start [QNetworkReplyHandler.cpp : 673 + 0x14]
    rbx = 0x00007f95f8267580   r12 = 0x00000000041dc6e8
    r13 = 0x00007f95f8267588   r14 = 0x00000000041dc6e8
    r15 = 0x00000000041dc6b0   rip = 0x0000000000add8ec
    rsp = 0x00007fff92a83b10   rbp = 0x00000000041dc6b0
    Found by: call frame info
15  phantomjs!WebCore::QNetworkReplyHandlerCallQueue::flush [QNetworkReplyHandler.cpp : 198 + 0x28]
    rbx = 0x0000000003b252f8   r12 = 0x00000000041dc6e8
    r13 = 0x00007f95f8267588   r14 = 0x00000000041dc6e8
    r15 = 0x00000000041dc6b0   rip = 0x0000000000adab81
    rsp = 0x00007fff92a83b40   rbp = 0x0000000003b252e0
    Found by: call frame info
16  phantomjs!WebCore::QNetworkReplyHandler::QNetworkReplyHandler [QNetworkReplyHandler.cpp : 409 + 0x21]
    rbx = 0x00007fff92a83bc0   r12 = 0x00000000041dc6e8
    r13 = 0x00007f95f8267588   r14 = 0x00000000041dc6d8
    r15 = 0x00000000041dc708   rip = 0x0000000000adc49f
    rsp = 0x00007fff92a83b90   rbp = 0x00000000041dc6b0
    Found by: call frame info
17  phantomjs!WebCore::ResourceHandle::start [ResourceHandleQt.cpp : 100 + 0x20]
    rbx = 0x00000000041dc6b0   r12 = 0x00007f95f82c69c0
    r13 = 0x00007f95f82c69d0   r14 = 0x0000000000000000
    r15 = 0x0000000000000001   rip = 0x0000000000ad85f1
    rsp = 0x00007fff92a83c10   rbp = 0x00007f95f8267580
    Found by: call frame info
18  phantomjs!WebCore::ResourceHandle::create [ResourceHandle.cpp : 71 + 0xc]
    rbx = 0x00007f95f82c69c0   r12 = 0x00007fff92a83d00
    r13 = 0x00007f95fb277c00   r14 = 0x0000000000000000
    r15 = 0x0000000000000001   rip = 0x000000000097755d
    rsp = 0x00007fff92a83c80   rbp = 0x00007f95fb277d00
    Found by: call frame info
19  phantomjs!WebCore::ResourceLoader::start [ResourceLoader.cpp : 164 + 0x2c]
    rbx = 0x0000000000000001   r12 = 0x00007f95fb277c00
    r13 = 0x00007f95fb277d00   r14 = 0x0000000000000001
    r15 = 0x00000000040e3310   rip = 0x0000000000887e8b
    rsp = 0x00007fff92a83ce0   rbp = 0x00007f95fb277c00
    Found by: call frame info
20  phantomjs!WebCore::ResourceLoadScheduler::servePendingRequests [ResourceLoadScheduler.cpp : 201 + 0x7]
    rbx = 0x00007f95fb145808   r12 = 0x00007f95fb277c00
    r13 = 0x00000000040e3300   r14 = 0x0000000000000001
    r15 = 0x00000000040e3310   rip = 0x000000000088bf06
    rsp = 0x00007fff92a83d40   rbp = 0x00007f95fb145808
    Found by: call frame info
21  phantomjs!WebCore::ResourceLoadScheduler::scheduleSubresourceLoad [ResourceLoadScheduler.cpp : 91 + 0xd]
    rbx = 0x00007f95fb277c00   r12 = 0x0000000000000001
    r13 = 0x000000000389ab50   r14 = 0x00007f96001c50c0
    r15 = 0x00007fff92a83e20   rip = 0x000000000088d2e9
    rsp = 0x00007fff92a83d90   rbp = 0x00007fff92a83f70
    Found by: call frame info
22  phantomjs!WebCore::CachedResourceRequest::load [CachedResourceRequest.cpp : 125 + 0x42]
    rbx = 0x0000000000000001   r12 = 0x00007f95fae02400
    r13 = 0x00007f95a308e000   r14 = 0x00007f96001c50c0
    r15 = 0x00007fff92a83e20   rip = 0x000000000113d9c6
    rsp = 0x00007fff92a83de0   rbp = 0x0000000000000001
    Found by: call frame info
23  phantomjs!WebCore::CachedResourceLoader::load [CachedResourceLoader.cpp : 541 + 0x7]
    rbx = 0x00007f96001c50c0   r12 = 0x0000000000000001
    r13 = 0x0000000000000000   r14 = 0x0000000004060b60
    r15 = 0x0000000004060b38   rip = 0x0000000000838fad
    rsp = 0x00007fff92a83fd0   rbp = 0x0000000000000001
    Found by: call frame info
24  phantomjs!WebCore::CachedResource::load [CachedResource.cpp : 133 + 0x4]
    rbx = 0x00007f95a308e000   r12 = 0x0000000000000001
    r13 = 0x0000000000000000   r14 = 0x0000000004060b60
    r15 = 0x0000000004060b38   rip = 0x000000000082ec63
    rsp = 0x00007fff92a84010   rbp = 0x0000000000000001
    Found by: call frame info
25  phantomjs!WebCore::CachedResourceLoader::loadResource [CachedResourceLoader.cpp : 393 + 0x12]
    rbx = 0x00000000ffffffff   r12 = 0x0000000000000001
    r13 = 0x0000000000000000   r14 = 0x0000000004060b60
    r15 = 0x0000000004060b38   rip = 0x000000000083b7b5
    rsp = 0x00007fff92a84020   rbp = 0x0000000000000001
    Found by: call frame info
26  phantomjs!WebCore::CachedResourceLoader::requestResource [CachedResourceLoader.cpp : 332 + 0x1c]
    rbx = 0x00007f95fb15a380   r12 = 0x0000000000000001
    r13 = 0x0000000000000000   r14 = 0x0000000004060b60
    r15 = 0x0000000004060b38   rip = 0x000000000083e33b
    rsp = 0x00007fff92a840a0   rbp = 0x0000000000000000
    Found by: call frame info
27  phantomjs!WebCore::CachedResourceLoader::requestImage [CachedResourceLoader.cpp : 137 + 0x1a]
    rbx = 0x00007f95fae02400   r12 = 0x00007f96001c50c0
    r13 = 0x00007f95fae17800   r14 = 0x0000000004060b60
    r15 = 0x0000000004060b38   rip = 0x000000000083f1ab
    rsp = 0x00007fff92a841d0   rbp = 0x00007fff92a842e0
    Found by: call frame info
28  phantomjs!WebCore::ImageLoader::updateFromElement [ImageLoader.cpp : 175 + 0x28]
    rbx = 0x00007fff92a842e0   r12 = 0x0000000000000000
    r13 = 0x00007f95fae17800   r14 = 0x0000000004060b60
    r15 = 0x0000000004060b38   rip = 0x0000000000872926
    rsp = 0x00007fff92a84250   rbp = 0x0000000004060b48
    Found by: call frame info
29  phantomjs!WebCore::HTMLImageElement::parseMappedAttribute [HTMLImageElement.cpp : 108 + 0x8]
    rbx = 0x0000000000000001   r12 = 0x0000000004060ad0
    r13 = 0x0000000004060ad0   r14 = 0x0000000000000000
    r15 = 0x0000000004060b38   rip = 0x000000000077ec10
    rsp = 0x00007fff92a84340   rbp = 0x00007f95fabc56c0
    Found by: call frame info
30  phantomjs!WebCore::StyledElement::attributeChanged [StyledElement.cpp : 188 + 0xf]
    rbx = 0x0000000000000001   r12 = 0x00007f95fabc56c0
    r13 = 0x0000000004060ad0   r14 = 0x0000000000000000
    r15 = 0x0000000004060b38   rip = 0x00000000010735a4
    rsp = 0x00007fff92a84440   rbp = 0x0000000000000001
    Found by: call frame info
31  phantomjs!WebCore::Element::setAttributeMap [Element.cpp : 851 + 0x16]
    rbx = 0x0000000000000000   r12 = 0x00007fff92a84570
    r13 = 0x00007f95fabc5740   r14 = 0x0000000000000000
    r15 = 0x0000000004060b38   rip = 0x0000000000635188
    rsp = 0x00007fff92a844e0   rbp = 0x00007fff92a84760
    Found by: call frame info
32  phantomjs!WebCore::HTMLConstructionSite::createHTMLElement [HTMLConstructionSite.cpp : 379 + 0x7]
    rbx = 0x00007f95a3afd3a8   r12 = 0x0000000004060ad0
    r13 = 0x00007fff92a845c0   r14 = 0x00007f95a3dc8120
    r15 = 0x00007fff92a847f0   rip = 0x00000000010f7478
    rsp = 0x00007fff92a84550   rbp = 0x00007fff92a84760
    Found by: call frame info
33  phantomjs!WebCore::HTMLConstructionSite::insertSelfClosingHTMLElement [HTMLConstructionSite.cpp : 295 + 0xc]
    rbx = 0x00007fff92a845c0   r12 = 0x00007f95a3afd3a8
    r13 = 0x0000000002a9de18   r14 = 0x00007f95a3dc8120
    r15 = 0x00007fff92a847f0   rip = 0x00000000010f918d
    rsp = 0x00007fff92a845b0   rbp = 0x00007fff92a84760
    Found by: call frame info
34  phantomjs!WebCore::HTMLTreeBuilder::processStartTagForInBody [HTMLTreeBuilder.cpp : 908 + 0xa]
    rbx = 0x00007f95a3afd3a8   r12 = 0x00007f95a3afd380
    r13 = 0x0000000002a9de18   r14 = 0x00007f95a3dc8120
    r15 = 0x00007fff92a847f0   rip = 0x00000000007da206
    rsp = 0x00007fff92a845f0   rbp = 0x00007fff92a84760
    Found by: call frame info
35  phantomjs!WebCore::HTMLTreeBuilder::processStartTag [HTMLTreeBuilder.cpp : 1334 + 0xa]
    rbx = 0x00007fff92a84760   r12 = 0x00007fff92a84760
    r13 = 0x00007f95a3dc70d0   r14 = 0x00007f95a3dc8120
    r15 = 0x00007fff92a847f0   rip = 0x00000000007db2db
    rsp = 0x00007fff92a84680   rbp = 0x00007f95a3afd380
    Found by: call frame info
36  phantomjs!WebCore::HTMLTreeBuilder::processToken [HTMLTreeBuilder.cpp : 479 + 0x4]
    rbx = 0x00007fff92a84760   r12 = 0x00007f95a3dc70c0
    r13 = 0x00007f95a3dc70d0   r14 = 0x00007f95a3dc8120
    r15 = 0x00007fff92a847f0   rip = 0x00000000007dccec
    rsp = 0x00007fff92a84730   rbp = 0x00007f95a3afd380
    Found by: call frame info
37  phantomjs!WebCore::HTMLTreeBuilder::constructTreeFromToken [HTMLTreeBuilder.cpp : 460 + 0xa]
    rbx = 0x00007f95a3dc70a8   r12 = 0x00007f95a3dc70c0
    r13 = 0x00007f95a3dc70d0   r14 = 0x00007f95a3dc8120
    r15 = 0x00007fff92a847f0   rip = 0x00000000007dcf1b
    rsp = 0x00007fff92a84760   rbp = 0x00007f95a3afd380
    Found by: call frame info
38  phantomjs!WebCore::HTMLDocumentParser::pumpTokenizer [HTMLDocumentParser.cpp : 276 + 0x7]
    rbx = 0x00007f95a3dc70a8   r12 = 0x00007f95a3dc80a8
    r13 = 0x00007f95a3dc7038   r14 = 0x00007f95a3dc8120
    r15 = 0x00007fff92a847f0   rip = 0x00000000007b68d7
    rsp = 0x00007fff92a847d0   rbp = 0x00007f95a3dc7000
    Found by: call frame info
39  phantomjs!WebCore::HTMLDocumentParser::insert [HTMLDocumentParser.cpp : 175 + 0xc]
    rbx = 0x00007f95a3dc7000   r12 = 0x00007fff92a859d0
    r13 = 0x0000000000000001   r14 = 0x00007fff92a85930
    r15 = 0x00007fff92a85b0c   rip = 0x00000000007b7033
    rsp = 0x00007fff92a84870   rbp = 0x00007f95a3dc7000
    Found by: call frame info
40  phantomjs!WebCore::HTMLDocumentParser::parseDocumentFragment [HTMLDocumentParser.cpp : 561 + 0x1]
    rbx = 0x0000000000000000   r12 = 0x00000000000001dc
    r13 = 0x0000000003b13800   r14 = 0x00007fff92a85b00
    r15 = 0x00007fff92a85b0c   rip = 0x00000000007ba2e8
    rsp = 0x00007fff92a859d0   rbp = 0x00007f95a3dc7000
    Found by: call frame info
41  phantomjs!WebCore::createFragmentFromSource [HTMLElement.cpp : 344 + 0xf]
    rbx = 0x000000000397a890   r12 = 0x0000000003b13800
    r13 = 0x00007fff92a85ac0   r14 = 0x00007fff92a85b00
    r15 = 0x00007fff92a85b0c   rip = 0x000000000076817d
    rsp = 0x00007fff92a85a70   rbp = 0x00007f95fae17800
    Found by: call frame info
42  phantomjs!WebCore::HTMLElement::setInnerHTML [HTMLElement.cpp : 358 + 0x7]
    rbx = 0x00007fff92a85b0c   r12 = 0x000000000397a890
    r13 = 0x00007f95a3b63d40   r14 = 0x00007f95a3cebdd0
    r15 = 0x00007fff92a85c20   rip = 0x000000000076e84a
    rsp = 0x00007fff92a85ac0   rbp = 0x000000000397a890
    Found by: call frame info
43  phantomjs!WebCore::setJSHTMLElementInnerHTML [JSHTMLElement.cpp : 432 + 0x14]
    rbx = 0x00007f95fb6ce690   r12 = 0x000000000397a890
    r13 = 0x00007f95a3b63d40   r14 = 0x00007f95a3cebdd0
    r15 = 0x00007fff92a85c20   rip = 0x0000000000c6297d
    rsp = 0x00007fff92a85b00   rbp = 0x00007f95fb6ce690
    Found by: call frame info
44  phantomjs!WebCore::JSHTMLElement::put [Lookup.h : 319 + 0xb]
    rbx = 0x00007f95fb6ce690   r12 = 0x00007f95fae03148
    r13 = 0x00007f95a3b63d40   r14 = 0x00007f95a3cebdd0
    r15 = 0x00007fff92a85c20   rip = 0x0000000000c61680
    rsp = 0x00007fff92a85b30   rbp = 0x00007fff92a85c20
    Found by: call frame info
45  phantomjs!WebCore::JSHTMLDivElement::put [Lookup.h : 334 + 0x13]
    rbx = 0x00007f95fb6ce690   r12 = 0x00007f95fae03148
    r13 = 0x00007f95a3b63d40   r14 = 0x00007f95a3cebdd0
    r15 = 0x00007fff92a85c20   rip = 0x000000000135b4d3
    rsp = 0x00007fff92a85ba0   rbp = 0x00007fff92a85c20
    Found by: call frame info
46  phantomjs!JSC::cti_op_put_by_id [JSObject.h : 804 + 0x5]
    rbx = 0x00007fff92a85c90   r12 = 0x00007f95fb6ce690
    r13 = 0x00007f95fae03148   r14 = 0x00007fff92a85c98
    r15 = 0x00007fff92a85c20   rip = 0x0000000000f59776
    rsp = 0x00007fff92a85c10   rbp = 0x00007fff92a85c88
    Found by: call frame info
47  0x7f95b408da8d
    rbx = 0x00007f95b408d8c3   r12 = 0x000000000003b902
    r13 = 0x00007f95fb6ce690   r14 = 0xffff000000000000
    r15 = 0xffff000000000002   rip = 0x00007f95b408da8e
    rsp = 0x00007fff92a85c90   rbp = 0x00007fff92a85d30
    Found by: call frame info
48  phantomjs!JSC::Interpreter::executeCall [JITCode.h : 77 + 0x16]
    rip = 0x0000000000f2e476   rsp = 0x00007fff92a85d40
    Found by: stack scanning
49  phantomjs!JSC::call [CallData.cpp : 38 + 0x21]
    rbx = 0x00007f96001aa850   r12 = 0x0000000000000002
    r13 = 0x00007f95fad2df90   r14 = 0x00007f95fb167ea0
    r15 = 0x00007f95fb6a43d0   rip = 0x0000000000f72a1d
    rsp = 0x00007fff92a85e10   rbp = 0x00007f95fae178d0
    Found by: call frame info
50  phantomjs!WebCore::JSEventListener::handleEvent [JSMainThreadExecState.h : 48 + 0xc]
    rbx = 0x00007f96001aa850   r12 = 0x0000000000000002
    r13 = 0x00007f95fad2df90   r14 = 0x00007f95fb167ea0
    r15 = 0x00007f95fb6a43d0   rip = 0x00000000010042c3
    rsp = 0x00007fff92a85e20   rbp = 0x00007f95fae178d0
    Found by: call frame info
51  phantomjs!WebCore::EventTarget::fireEventListeners [EventTarget.cpp : 360 + 0x1b]
    rbx = 0x00007f95fad2df90   r12 = 0x00007f95fb167ea0
    r13 = 0x00007f95fae17800   r14 = 0x00007f95fade40a8
    r15 = 0x00007f95fac6d988   rip = 0x000000000063c4e1
    rsp = 0x00007fff92a86090   rbp = 0x0000000001003b30
    Found by: call frame info
52  phantomjs!WebCore::EventTarget::fireEventListeners [EventTarget.cpp : 329 + 0x11]
    rbx = 0x00007f95fae17800   r12 = 0x00007fff92a86230
    r13 = 0x00007fff92a86250   r14 = 0x00007f95fae17800
    r15 = 0x00007fff92a86268   rip = 0x000000000063d663
    rsp = 0x00007fff92a86110   rbp = 0x00007f95fb167ea0
    Found by: call frame info
53  phantomjs!WebCore::EventDispatcher::dispatchEvent [EventDispatcher.cpp : 306 + 0xc]
    rbx = 0x00007f95fae17800   r12 = 0x00007fff92a86230
    r13 = 0x00007fff92a86250   r14 = 0x00007f95fae17800
    r15 = 0x00007fff92a86268   rip = 0x000000000063a13b
    rsp = 0x00007fff92a86130   rbp = 0x00007f95fae17800
    Found by: call frame info
54  phantomjs!WebCore::EventDispatchMediator::dispatchEvent [Event.cpp : 313 + 0xa]
    rbx = 0x00007fff92a862b0   r12 = 0x00007f95fae17800
    r13 = 0x000000000064caf0   r14 = 0x00000000000b864b
    r15 = 0x00007fff92a86ab0   rip = 0x0000000000637484
    rsp = 0x00007fff92a86230   rbp = 0x00007f95fae17800
    Found by: call frame info
55  phantomjs!WebCore::EventDispatcher::dispatchEvent [EventDispatcher.cpp : 53 + 0xb]
    rbx = 0x00007fff92a862b0   r12 = 0x00007f95fae17800
    r13 = 0x000000000064caf0   r14 = 0x00000000000b864b
    r15 = 0x00007fff92a86ab0   rip = 0x000000000063bd02
    rsp = 0x00007fff92a86250   rbp = 0x00007f95fae17800
    Found by: call frame info
56  phantomjs!WebCore::Node::dispatchEvent [Node.cpp : 2818 + 0xf]
    rbx = 0x00007f96001d0de0   r12 = 0x00007f95fae17800
    r13 = 0x000000000064caf0   r14 = 0x00000000000b864b
    r15 = 0x00007fff92a86ab0   rip = 0x000000000064cb20
    rsp = 0x00007fff92a862b0   rbp = 0x00007f95fae17800
    Found by: call frame info
57  phantomjs!WebCore::Document::finishedParsing [Document.cpp : 4222 + 0x8]
    rbx = 0x00007f96001d0de0   r12 = 0x00007f95fae17800
    r13 = 0x000000000064caf0   r14 = 0x00000000000b864b
    r15 = 0x00007fff92a86ab0   rip = 0x000000000060b463
    rsp = 0x00007fff92a862f0   rbp = 0x00007f95fb167ea0
    Found by: call frame info
58  phantomjs!WebCore::HTMLDocumentParser::prepareToStopParsing [HTMLDocumentParser.cpp : 378 + 0xb]
    rbx = 0x00007f96001d3200   r12 = 0x0000000000000000
    r13 = 0x00000000035dfab0   r14 = 0x00000000000b864b
    r15 = 0x00007fff92a86ab0   rip = 0x00000000007b71c7
    rsp = 0x00007fff92a86330   rbp = 0x0000000000000001
    Found by: call frame info
59  phantomjs!WebCore::HTMLDocumentParser::resumeParsingAfterYield [HTMLDocumentParser.cpp : 412 + 0x8]
    rbx = 0x00007f96001d3200   r12 = 0x0000000000000000
    r13 = 0x00000000035dfab0   r14 = 0x00000000000b864b
    r15 = 0x00007fff92a86ab0   rip = 0x00000000007b6ac6
    rsp = 0x00007fff92a86350   rbp = 0x0000000000000001
    Found by: call frame info
60  phantomjs!WebCore::ThreadTimers::sharedTimerFiredInternal [ThreadTimers.cpp : 112 + 0x8]
    rbx = 0x00007f95fb5c7ac0   r12 = 0x0000000000000000
    r13 = 0x00000000035dfab0   r14 = 0x00000000000b864b
    r15 = 0x00007fff92a86ab0   rip = 0x0000000000993a83
    rsp = 0x00007fff92a86370   rbp = 0x00007f96001bf7a8
    Found by: call frame info
61  phantomjs!QObject::event [qobject.cpp : 1156 + 0x8]
    rbx = 0x00000000038a7660   r12 = 0x00007fff92a86ab0
    r13 = 0x00000000035dfab0   r14 = 0x00000000000b864b
    r15 = 0x00007fff92a86ab0   rip = 0x0000000001cefcc4
    rsp = 0x00007fff92a863b0   rbp = 0x00000000038a7660
    Found by: call frame info
62  phantomjs!QApplicationPrivate::notify_helper [qapplication.cpp : 4562 + 0xc]
    rbx = 0x00007fff92a86d30   r12 = 0x00007fff92a86ab0
    r13 = 0x00000000035dfab0   r14 = 0x00000000000b864b
    r15 = 0x00007fff92a86ab0   rip = 0x00000000015dedaf
    rsp = 0x00007fff92a86550   rbp = 0x00000000038a7660
    Found by: call frame info
63  phantomjs!QApplication::notify [qapplication.cpp : 4423 + 0x17]
    rbx = 0x00007fff92a86d30   r12 = 0x00007fff92a86ab0
    r13 = 0x00007fff92a86d30   r14 = 0x00000000000b864b
    r15 = 0x00007fff92a86ab0   rip = 0x00000000015e7a3b
    rsp = 0x00007fff92a86580   rbp = 0x00000000038a7660
    Found by: call frame info
64  phantomjs!QCoreApplication::notifyInternal [qcoreapplication.cpp : 946 + 0x2]
    rbx = 0x00000000035dd1c0   r12 = 0x00007fff92a86ab0
    r13 = 0x00007fff92a86d30   r14 = 0x00000000000b864b
    r15 = 0x00007fff92a86ab0   rip = 0x0000000001cde4d4
    rsp = 0x00007fff92a86a50   rbp = 0x00000000038a7660
    Found by: call frame info
65  phantomjs!QTimerInfoList::activateTimers [qcoreapplication.h : 231 + 0x14]
    rbx = 0x00000000035e1898   r12 = 0x0000000000000000
    r13 = 0x0000000000000000   r14 = 0x00000000000b864b
    r15 = 0x00007fff92a86ab0   rip = 0x0000000001d07fcd
    rsp = 0x00007fff92a86aa0   rbp = 0x000000000002f382
    Found by: call frame info
66  phantomjs!QEventDispatcherUNIX::processEvents [qeventdispatcher_unix.cpp : 941 + 0x7]
    rbx = 0x0000000000000001   r12 = 0x00007fff92a86b80
    r13 = 0x00000000035dc560   r14 = 0x0000000000000000
    r15 = 0x00000000035dd2d8   rip = 0x0000000001d081e0
    rsp = 0x00007fff92a86b30   rbp = 0x00000000035e1030
    Found by: call frame info
67  phantomjs!QEventDispatcherQPA::processEvents [qeventdispatcher_qpa.cpp : 246 + 0x4]
    rbx = 0x0000000003907e30   r12 = 0x0000000000000000
    r13 = 0x00000000035dc560   r14 = 0x00007fff92a86bc0
    r15 = 0x00000000035dd2d8   rip = 0x000000000163a7a4
    rsp = 0x00007fff92a86b80   rbp = 0x00000000035e1030
    Found by: call frame info
68  phantomjs!QEventLoop::processEvents [qeventloop.cpp : 149 + 0x1]
    rbx = 0x0000000003907e30   r12 = 0x00007fff92a86c50
    r13 = 0x00007fff92a86c60   r14 = 0x00000000035dd230
    r15 = 0x00000000035dd2d8   rip = 0x0000000001cdd5b5
    rsp = 0x00007fff92a86bc0   rbp = 0x00007fff92a86c00
    Found by: call frame info
69  phantomjs!QEventLoop::exec [qeventloop.cpp : 200 + 0x4]
    rbx = 0x0000000003907e30   r12 = 0x00007fff92a86c50
    r13 = 0x00007fff92a86c60   r14 = 0x00000000035dd230
    r15 = 0x00000000035dd2d8   rip = 0x0000000001cdda18
    rsp = 0x00007fff92a86bf0   rbp = 0x00007fff92a86d30
    Found by: call frame info
70  phantomjs!QCoreApplication::exec [qcoreapplication.cpp : 1218 + 0x4]
    rbx = 0x00000000035dd1c0   r12 = 0x00007fff92a86d30
    r13 = 0x00007fff92a86ee8   r14 = 0x00007fff92a86ca0
    r15 = 0x0000000000000000   rip = 0x0000000001cdf8cb
    rsp = 0x00007fff92a86c50   rbp = 0x00000000035dd1c0
    Found by: call frame info
71  phantomjs!main [main.cpp : 121 + 0x4]
    rbx = 0x000000000366a940   r12 = 0x00007fff92a86d30
    r13 = 0x00007fff92a86ee8   r14 = 0x00007fff92a86ca0
    r15 = 0x0000000000000000   rip = 0x0000000000427db2
    rsp = 0x00007fff92a86c90   rbp = 0x00007fff92a86ec8
    Found by: call frame info
72  libc-2.17.so + 0x24c44
    rbx = 0x0000000000000000   r12 = 0x0000000000407cc0
    r13 = 0x00007fff92a86ec0   r14 = 0x0000000000000000
    r15 = 0x0000000000000000   rip = 0x00007f95fea65c45
    rsp = 0x00007fff92a86df0   rbp = 0x0000000000000000
    Found by: call frame info
73  phantomjs + 0x27b5f
    rip = 0x0000000000427b60   rsp = 0x00007fff92a86e10
    Found by: stack scanning

Thread 1
 0  libc-2.17.so + 0xbd13d
    rbx = 0x00007f95fcad7cd0   r12 = 0x0000000002a76160
    r13 = 0x00007f95ff645680   r14 = 0x0000000000001000
    r15 = 0x00007f95fcad8700   rip = 0x00007f95feafe13d
    rsp = 0x00007f95fcad7cb0   rbp = 0x00000000ffffffff
    Found by: given as instruction pointer in context
 1  libc-2.17.so + 0xbcfe0
    rip = 0x00007f95feafdfe1   rsp = 0x00007f95fcad7cc0
    Found by: stack scanning
 2  libc-2.17.so + 0x11aaf
    rip = 0x00007f95fea52ab0   rsp = 0x00007f95fcad7d68
    Found by: stack scanning
 3  phantomjs + 0x18b5d6f
    rip = 0x0000000001cb5d70   rsp = 0x00007f95fcad7dd8
    Found by: stack scanning
 4  libc-2.17.so + 0x11aaf
    rip = 0x00007f95fea52ab0   rsp = 0x00007f95fcad7de8
    Found by: stack scanning
 5  libc-2.17.so + 0x13f6f
    rip = 0x00007f95fea54f70   rsp = 0x00007f95fcad7e18
    Found by: stack scanning
 6  libpthread-2.17.so + 0x10b0f
    rip = 0x00007f95ff643b10   rsp = 0x00007f95fcad7e68
    Found by: stack scanning
 7  phantomjs!WTF::TCMalloc_PageHeap::scavengerThread [FastMalloc.cpp : 2499 + 0x4]
    rip = 0x00000000004ddb2e   rsp = 0x00007f95fcad7e90
    Found by: stack scanning
 8  phantomjs!WTF::TCMalloc_PageHeap::runScavengerThread [FastMalloc.cpp : 1618 + 0x4]
    rbx = 0x0000000000000000   r12 = 0x0000000000000000
    r13 = 0x00007f95ff645680   r14 = 0x0000000000001000
    r15 = 0x00007f95fcad8700   rip = 0x00000000004ddd99
    rsp = 0x00007f95fcad7f10   rbp = 0x0000000000000000
    Found by: call frame info
 9  libpthread-2.17.so + 0x8f39
    rbx = 0x0000000000000000   r12 = 0x0000000000000000
    r13 = 0x00007f95ff645680   r14 = 0x0000000000001000
    r15 = 0x00007f95fcad8700   rip = 0x00007f95ff63bf3a
    rsp = 0x00007f95fcad7f20   rbp = 0x0000000000000000
    Found by: call frame info
10  libpthread-2.17.so + 0x1267f
    rip = 0x00007f95ff645680   rsp = 0x00007f95fcad7f50
    Found by: stack scanning
11  libc-2.17.so + 0xede8c
    rip = 0x00007f95feb2ee8d   rsp = 0x00007f95fcad7fc0
    Found by: stack scanning

Thread 2
 0  libc-2.17.so + 0xe6823
    rbx = 0x0000000000000000   r12 = 0x00007f95fc2cedf0
    r13 = 0x0000000000000008   r14 = 0x00007f95f4000a98
    r15 = 0x00007f95f4000d30   rip = 0x00007f95feb27823
    rsp = 0x00007f95fc2cebc0   rbp = 0x00007f95f40008e0
    Found by: given as instruction pointer in context
 1  phantomjs!qt_safe_select [qcore_unix.cpp : 83 + 0x15]
    rip = 0x0000000001d06427   rsp = 0x00007f95fc2cebd0
    Found by: stack scanning
 2  phantomjs!QEventDispatcherUNIXPrivate::doSelect [qeventdispatcher_unix.cpp : 223 + 0xd]
    rbx = 0x00007f95f40012b0   r12 = 0x00007f95fc2cedf0
    r13 = 0x00007f95f40008e0   r14 = 0x0000000000000000
    r15 = 0x00007f95f4000d30   rip = 0x0000000001d076e7
    rsp = 0x00007f95fc2cec60   rbp = 0x00007f95f40008e0
    Found by: call frame info
 3  phantomjs!QEventDispatcherUNIX::processEvents [qeventdispatcher_unix.cpp : 937 + 0x4]
    rbx = 0x00007f95f40012b0   r12 = 0x00007f95fc2cedf0
    r13 = 0x00007f95f40008c0   r14 = 0x0000000000000001
    r15 = 0x00000000035ed788   rip = 0x0000000001d08192
    rsp = 0x00007f95fc2ceda0   rbp = 0x00007f95f40008e0
    Found by: call frame info
 4  phantomjs!QEventLoop::processEvents [qeventloop.cpp : 149 + 0x1]
    rbx = 0x00007f95f40012b0   r12 = 0x00007f95fc2cee80
    r13 = 0x00007f95fc2cee90   r14 = 0x00000000035dd230
    r15 = 0x00000000035ed788   rip = 0x0000000001cdd5b5
    rsp = 0x00007f95fc2cedf0   rbp = 0x00007f95fc2cee30
    Found by: call frame info
 5  phantomjs!QEventLoop::exec [qeventloop.cpp : 200 + 0x4]
    rbx = 0x00007f95f40012b0   r12 = 0x00007f95fc2cee80
    r13 = 0x00007f95fc2cee90   r14 = 0x00000000035dd230
    r15 = 0x00000000035ed788   rip = 0x0000000001cdda18
    rsp = 0x00007f95fc2cee20   rbp = 0x00007fff92a86d30
    Found by: call frame info
 6  phantomjs!QThread::exec [qthread.cpp : 542 + 0xc]
    rbx = 0x00000000035ed700   r12 = 0x00000000035ed788
    r13 = 0x0000000000000001   r14 = 0x0000000000001000
    r15 = 0x00007f95fc2cf700   rip = 0x0000000001bdfef6
    rsp = 0x00007f95fc2cee80   rbp = 0x00000000035ed788
    Found by: call frame info
 7  phantomjs!QThreadPrivate::start [qthread_unix.cpp : 338 + 0x9]
    rbx = 0x00000000035ed788   r12 = 0x00000000035ed010
    r13 = 0x0000000000000001   r14 = 0x0000000000001000
    r15 = 0x00007f95fc2cf700   rip = 0x0000000001be2dc2
    rsp = 0x00007f95fc2ceed0   rbp = 0x00000000036729f0
    Found by: call frame info
 8  libpthread-2.17.so + 0x8f39
    rbx = 0x0000000000000000   r12 = 0x0000000000000000
    r13 = 0x00007fff92a86210   r14 = 0x0000000000001000
    r15 = 0x00007f95fc2cf700   rip = 0x00007f95ff63bf3a
    rsp = 0x00007f95fc2cef20   rbp = 0x0000000000000000
    Found by: call frame info
 9  libc-2.17.so + 0xede8c
    rip = 0x00007f95feb2ee8d   rsp = 0x00007f95fc2cefc0
    Found by: stack scanning

Thread 3
 0  libc-2.17.so + 0xe6823
    rbx = 0x00007f95fa968da0   r12 = 0x000000000002f382
    r13 = 0x000000000000003e   r14 = 0x00007f95ac000a98
    r15 = 0x00007f95ac000d30   rip = 0x00007f95feb27823
    rsp = 0x00007f95fa968bc0   rbp = 0x00000000000defd7
    Found by: given as instruction pointer in context
 1  phantomjs!qt_safe_select [qcore_unix.cpp : 93 + 0x16]
    rip = 0x0000000001d06328   rsp = 0x00007f95fa968bd0
    Found by: stack scanning
 2  phantomjs!QEventDispatcherUNIXPrivate::doSelect [qeventdispatcher_unix.cpp : 223 + 0xd]
    rbx = 0x00007f95ac0012b0   r12 = 0x00007f95fa968df0
    r13 = 0x00007f95ac0008e0   r14 = 0x00007f95fa968da0
    r15 = 0x00007f95ac000d30   rip = 0x0000000001d076e7
    rsp = 0x00007f95fa968c60   rbp = 0x00007f95ac0008e0
    Found by: call frame info
 3  phantomjs!QEventDispatcherUNIX::processEvents [qeventdispatcher_unix.cpp : 937 + 0x4]
    rbx = 0x00007f95ac0012b0   r12 = 0x00007f95fa968df0
    r13 = 0x00007f95ac0008c0   r14 = 0x0000000000000001
    r15 = 0x000000000390ae98   rip = 0x0000000001d08192
    rsp = 0x00007f95fa968da0   rbp = 0x00007f95ac0008e0
    Found by: call frame info
 4  phantomjs!QEventLoop::processEvents [qeventloop.cpp : 149 + 0x1]
    rbx = 0x00007f95ac0012b0   r12 = 0x00007f95fa968e80
    r13 = 0x00007f95fa968e90   r14 = 0x00000000035dd230
    r15 = 0x000000000390ae98   rip = 0x0000000001cdd5b5
    rsp = 0x00007f95fa968df0   rbp = 0x00007f95fa968e30
    Found by: call frame info
 5  phantomjs!QEventLoop::exec [qeventloop.cpp : 200 + 0x4]
    rbx = 0x00007f95ac0012b0   r12 = 0x00007f95fa968e80
    r13 = 0x00007f95fa968e90   r14 = 0x00000000035dd230
    r15 = 0x000000000390ae98   rip = 0x0000000001cdda18
    rsp = 0x00007f95fa968e20   rbp = 0x00007fff92a86d30
    Found by: call frame info
 6  phantomjs!QThread::exec [qthread.cpp : 542 + 0xc]
    rbx = 0x000000000390ae10   r12 = 0x000000000390ae98
    r13 = 0x0000000000000001   r14 = 0x0000000000001000
    r15 = 0x00007f95fa969700   rip = 0x0000000001bdfef6
    rsp = 0x00007f95fa968e80   rbp = 0x000000000390ae98
    Found by: call frame info
 7  phantomjs!QThreadPrivate::start [qthread_unix.cpp : 338 + 0x9]
    rbx = 0x000000000390ae98   r12 = 0x000000000390af50
    r13 = 0x0000000000000001   r14 = 0x0000000000001000
    r15 = 0x00007f95fa969700   rip = 0x0000000001be2dc2
    rsp = 0x00007f95fa968ed0   rbp = 0x000000000390adf0
    Found by: call frame info
 8  libpthread-2.17.so + 0x8f39
    rbx = 0x0000000000000000   r12 = 0x0000000000000000
    r13 = 0x00007fff92a829c0   r14 = 0x0000000000001000
    r15 = 0x00007f95fa969700   rip = 0x00007f95ff63bf3a
    rsp = 0x00007f95fa968f20   rbp = 0x0000000000000000
    Found by: call frame info
 9  libc-2.17.so + 0xede8c
    rip = 0x00007f95feb2ee8d   rsp = 0x00007f95fa968fc0
    Found by: stack scanning

Thread 4
 0  libpthread-2.17.so + 0xd0de
    rbx = 0x00007f95ac0054c0   r12 = 0x0000000000000020
    r13 = 0x00007f95fa167e30   r14 = 0xffffffffffffff92
    r15 = 0x00007f95ac005400   rip = 0x00007f95ff6400de
    rsp = 0x00007f95fa167db0   rbp = 0x00007f95ac005790
    Found by: given as instruction pointer in context
 1  phantomjs!QWaitCondition::wait [qwaitcondition_unix.cpp : 84 + 0x7]
    rip = 0x0000000001be3ad7   rsp = 0x00007f95fa167e10
    Found by: stack scanning
 2  phantomjs!QThreadPoolThread::run [qthreadpool.cpp : 141 + 0x1d]
    rbx = 0x00007f95ac0053e0   r12 = 0x00007f95ac005469
    r13 = 0x0000000000000002   r14 = 0x00007f95ac08e3e0
    r15 = 0x00007f95fa168700   rip = 0x0000000001bd793d
    rsp = 0x00007f95fa167e90   rbp = 0x00007f95ac005790
    Found by: call frame info
 3  phantomjs!QThreadPrivate::start [qthread_unix.cpp : 338 + 0x9]
    rbx = 0x00007f95b00012b0   r12 = 0x00007f95ac005930
    r13 = 0x0000000000000001   r14 = 0x0000000000001000
    r15 = 0x00007f95fa168700   rip = 0x0000000001be2dc2
    rsp = 0x00007f95fa167ed0   rbp = 0x00007f95ac005790
    Found by: call frame info
 4  libpthread-2.17.so + 0x8f39
    rbx = 0x0000000000000000   r12 = 0x0000000000000000
    r13 = 0x00007f95fa967600   r14 = 0x0000000000001000
    r15 = 0x00007f95fa168700   rip = 0x00007f95ff63bf3a
    rsp = 0x00007f95fa167f20   rbp = 0x0000000000000000
    Found by: call frame info
 5  libc-2.17.so + 0xede8c
    rip = 0x00007f95feb2ee8d   rsp = 0x00007f95fa167fc0
    Found by: stack scanning

Thread 5
 0  libpthread-2.17.so + 0xd0de
    rbx = 0x00007f95ac0054c0   r12 = 0x000000000000001a
    r13 = 0x00007f95f93dfe30   r14 = 0xffffffffffffff92
    r15 = 0x00007f95ac005400   rip = 0x00007f95ff6400de
    rsp = 0x00007f95f93dfdb0   rbp = 0x00007f95ac01ed00
    Found by: given as instruction pointer in context
 1  phantomjs!QWaitCondition::wait [qwaitcondition_unix.cpp : 84 + 0x7]
    rip = 0x0000000001be3ad7   rsp = 0x00007f95f93dfe10
    Found by: stack scanning
 2  phantomjs!QThreadPoolThread::run [qthreadpool.cpp : 141 + 0x1d]
    rbx = 0x00007f95ac0053e0   r12 = 0x00007f95ac005469
    r13 = 0x0000000000000002   r14 = 0x00007f95ac03a570
    r15 = 0x00007f95f93e0700   rip = 0x0000000001bd793d
    rsp = 0x00007f95f93dfe90   rbp = 0x00007f95ac01ed00
    Found by: call frame info
 3  phantomjs!QThreadPrivate::start [qthread_unix.cpp : 338 + 0x9]
    rbx = 0x00007f95a40012b0   r12 = 0x00007f95ac01f0d0
    r13 = 0x0000000000000001   r14 = 0x0000000000001000
    r15 = 0x00007f95f93e0700   rip = 0x0000000001be2dc2
    rsp = 0x00007f95f93dfed0   rbp = 0x00007f95ac01ed00
    Found by: call frame info
 4  libpthread-2.17.so + 0x8f39
    rbx = 0x0000000000000000   r12 = 0x0000000000000000
    r13 = 0x00007f95fa967600   r14 = 0x0000000000001000
    r15 = 0x00007f95f93e0700   rip = 0x00007f95ff63bf3a
    rsp = 0x00007f95f93dff20   rbp = 0x0000000000000000
    Found by: call frame info
 5  libc-2.17.so + 0xede8c
    rip = 0x00007f95feb2ee8d   rsp = 0x00007f95f93dffc0
    Found by: stack scanning

Thread 6
 0  libpthread-2.17.so + 0xd0de
    rbx = 0x00007f95ac0054c0   r12 = 0x000000000000001d
    r13 = 0x00007f95f8bdee30   r14 = 0xffffffffffffff92
    r15 = 0x00007f95ac005400   rip = 0x00007f95ff6400de
    rsp = 0x00007f95f8bdedb0   rbp = 0x00007f95ac00e6a0
    Found by: given as instruction pointer in context
 1  phantomjs!QWaitCondition::wait [qwaitcondition_unix.cpp : 84 + 0x7]
    rip = 0x0000000001be3ad7   rsp = 0x00007f95f8bdee10
    Found by: stack scanning
 2  phantomjs!QThreadPoolThread::run [qthreadpool.cpp : 141 + 0x1d]
    rbx = 0x00007f95ac0053e0   r12 = 0x00007f95ac005469
    r13 = 0x0000000000000002   r14 = 0x00007f95ac0759f0
    r15 = 0x00007f95f8bdf700   rip = 0x0000000001bd793d
    rsp = 0x00007f95f8bdee90   rbp = 0x00007f95ac00e6a0
    Found by: call frame info
 3  phantomjs!QThreadPrivate::start [qthread_unix.cpp : 338 + 0x9]
    rbx = 0x00007f95a80012b0   r12 = 0x00007f95ac00e980
    r13 = 0x0000000000000001   r14 = 0x0000000000001000
    r15 = 0x00007f95f8bdf700   rip = 0x0000000001be2dc2
    rsp = 0x00007f95f8bdeed0   rbp = 0x00007f95ac00e6a0
    Found by: call frame info
 4  libpthread-2.17.so + 0x8f39
    rbx = 0x0000000000000000   r12 = 0x0000000000000000
    r13 = 0x00007f95fa967600   r14 = 0x0000000000001000
    r15 = 0x00007f95f8bdf700   rip = 0x00007f95ff63bf3a
    rsp = 0x00007f95f8bdef20   rbp = 0x0000000000000000
    Found by: call frame info
 5  libc-2.17.so + 0xede8c
    rip = 0x00007f95feb2ee8d   rsp = 0x00007f95f8bdefc0
    Found by: stack scanning

Thread 7
 0  libpthread-2.17.so + 0xd0de
    rbx = 0x00007f95ac0054c0   r12 = 0x000000000000001e
    r13 = 0x00007f95a3a01e30   r14 = 0xffffffffffffff92
    r15 = 0x00007f95ac005400   rip = 0x00007f95ff6400de
    rsp = 0x00007f95a3a01db0   rbp = 0x00007f95ac03bb40
    Found by: given as instruction pointer in context
 1  phantomjs!QWaitCondition::wait [qwaitcondition_unix.cpp : 84 + 0x7]
    rip = 0x0000000001be3ad7   rsp = 0x00007f95a3a01e10
    rbp = 0x00007f95ac03bb40
    Found by: stack scanning
 2  phantomjs!QThreadPoolThread::run [qthreadpool.cpp : 141 + 0x1d]
    rbx = 0x00007f95ac0053e0   r12 = 0x00007f95ac005469
    r13 = 0x0000000000000002   r14 = 0x00007f95ac06ba30
    r15 = 0x00007f95a3a02700   rip = 0x0000000001bd793d
    rsp = 0x00007f95a3a01e90   rbp = 0x00007f95ac03bb40
    Found by: call frame info
 3  phantomjs!QThreadPrivate::start [qthread_unix.cpp : 338 + 0x9]
    rbx = 0x00007f959c0012b0   r12 = 0x00007f95ac03bf30
    r13 = 0x0000000000000001   r14 = 0x0000000000001000
    r15 = 0x00007f95a3a02700   rip = 0x0000000001be2dc2
    rsp = 0x00007f95a3a01ed0   rbp = 0x00007f95ac03bb40
    Found by: call frame info
 4  libpthread-2.17.so + 0x8f39
    rbx = 0x0000000000000000   r12 = 0x0000000000000000
    r13 = 0x00007f95fa967600   r14 = 0x0000000000001000
    r15 = 0x00007f95a3a02700   rip = 0x00007f95ff63bf3a
    rsp = 0x00007f95a3a01f20   rbp = 0x0000000000000000
    Found by: call frame info
 5  libc-2.17.so + 0xede8c
    rip = 0x00007f95feb2ee8d   rsp = 0x00007f95a3a01fc0
    Found by: stack scanning

Loaded modules:
0x00400000 - 0x0268dfff  phantomjs  ???  (main)
0x7f95a3faa000 - 0x7f95a3ffffff  LiberationSans-Regular.ttf  ???
0x7f95f804e000 - 0x7f95f80a3fff  arialbd.ttf  ???
0x7f95f8315000 - 0x7f95f833afff  verdanab.ttf  ???
0x7f95f833b000 - 0x7f95f8394fff  arial.ttf  ???
0x7f95f83a3000 - 0x7f95f83d0fff  verdana.ttf  ???
0x7f95f9501000 - 0x7f95f9706fff  libnss_dns-2.17.so  ???
0x7f95f9707000 - 0x7f95f9913fff  libnss_files-2.17.so  ???
0x7f95fcad9000 - 0x7f95fccedfff  libresolv-2.17.so  ???
0x7f95fccf0000 - 0x7f95fcef3fff  libkeyutils.so.1.5  ???
0x7f95fcef4000 - 0x7f95fd101fff  libkrb5support.so.0.1  ???
0x7f95fd102000 - 0x7f95fd305fff  libcom_err.so.2.1  ???
0x7f95fd306000 - 0x7f95fd538fff  libk5crypto.so.3.1  ???
0x7f95fd539000 - 0x7f95fd81cfff  libkrb5.so.3.3  ???
0x7f95fd81d000 - 0x7f95fda79fff  libssl.so.0.9.8  ???
0x7f95fda7a000 - 0x7f95fde09fff  libcrypto.so.0.9.8  ???
0x7f95fde0d000 - 0x7f95fe1bafff  locale-archive  ???
0x7f95fe1bb000 - 0x7f95fe3e4fff  libexpat.so.1.6.0  ???
0x7f95fe3e5000 - 0x7f95fe619fff  libpng16.so.16.13.0  ???
0x7f95fe61a000 - 0x7f95fe82afff  libbz2.so.1.0.6  ???
0x7f95fe82b000 - 0x7f95fea40fff  libz.so.1.2.8  ???
0x7f95fea41000 - 0x7f95fedecfff  libc-2.17.so  ???
0x7f95fedf1000 - 0x7f95ff008fff  libgcc_s.so.1  ???
0x7f95ff009000 - 0x7f95ff306fff  libm-2.17.so  ???
0x7f95ff307000 - 0x7f95ff61efff  libstdc++.so.6.0.19  ???
0x7f95ff633000 - 0x7f95ff84bfff  libpthread-2.17.so  ???
0x7f95ff850000 - 0x7f95ffa57fff  librt-2.17.so  ???
0x7f95ffa58000 - 0x7f95ffc5bfff  libdl-2.17.so  ???
0x7f95ffc5c000 - 0x7f95ffe98fff  libfontconfig.so.1.8.0  ???
0x7f95ffe99000 - 0x7f960015afff  libfreetype.so.6.11.2  ???
0x7f960015b000 - 0x7f960017cfff  ld-2.17.so  ???
0x7f960029e000 - 0x7f96002a4fff  gconv-modules.cache  ???
0x7f96002a5000 - 0x7f96002cafff  libc.mo  ???
0x7f96002cb000 - 0x7f96002cffff  f55bbeb01d684dc5b5f7b2c347cc42d9-le64.cache-4  ???
0x7f96002d0000 - 0x7f96002d3fff  76fa4b957c916922374347f144bde9da-le64.cache-4  ???
0x7f96002d4000 - 0x7f96002d6fff  b2d431a31d342c7b6b32ea8a8f796c86-le64.cache-4  ???
0x7f96002d7000 - 0x7f96002eafff  8d4af663993b81a124ee82e610bb31f9-le64.cache-4  ???
0x7f96002eb000 - 0x7f96002ebfff  e61abf8156cc476151baa07d67337cae-le64.cache-4  ???
0x7f96002ec000 - 0x7f96002f9fff  d722f191fc173fb8c13c8ea6f285de40-le64.cache-4  ???
0x7f96002fa000 - 0x7f960031dfff  0ab7af1fb3bdf18d804b641fb2a04792-le64.cache-4  ???
0x7f9600327000 - 0x7f960032bfff  a595ca43be94766bbfe429f07fba82d0-le64.cache-4  ???
0x7f960032c000 - 0x7f9600331fff  b7b96da43d018c777cd824110a0f12ee-le64.cache-4  ???
0x7f9600332000 - 0x7f960033cfff  12b26b760a24f8b4feb03ad48a333a72-le64.cache-4  ???
0x7f960033d000 - 0x7f9600341fff  1649608eb9b8f94c6b3224be69857e3b-le64.cache-4  ???
0x7f9600342000 - 0x7f960035ffff  4b5cf4386f1cde02a336ba961b4ac82d-le64.cache-4  ???
0x7f9600360000 - 0x7f9600360fff  6ba42ae0000f58711b5caaf10d690066-le64.cache-4  ???
0x7f9600361000 - 0x7f9600367fff  61c91b4f4892ffae4bc0efef540a1e5d-le64.cache-4  ???
0x7f9600368000 - 0x7f9600377fff  f73c51d6200a78c2054c26a5b2398976-le64.cache-4  ???
0x7f9600378000 - 0x7f960037afff  aa055bd841cd05e30be12eda90497fe3-le64.cache-4  ???
0x7fff92ab4000 - 0x7fff92ab5fff  linux-gate.so  ???

It looks like I stumbled upon the same "moon" issue here https://github.com/ariya/phantomjs/issues/12978 :(

¿Can't we hold the moon on some position?

Please upgrade to PhantomJS 2.0. 1.9.x is no longer supported, and known to have many crasher bugs that are fixed in 2.0.


applyPatches should fail if can't apply a patch

On applyPatches, if a patch can't be applied it's just notified to the user. This should call inmediatly to completed() and raise the full application of patches as a failure.

I've fixed this on issue #130.

I disagree. The user should decide how they want to handle this. They may want to have everything possible apply and be notified about what did not.

I was thinking about this posibility too, but the point is that if there
are several chunks on the diff, failing one of them then it doesn't makes
sense to apply the other, the patch only makes sense to be applied at once
as a single item.
El 21/8/2016 20:38, "Kevin Decker"<EMAIL_ADDRESS>escribió:

I disagree. The user should decide how they want to handle this. They may
want to have everything possible apply and be notified about what did not.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kpdecker/jsdiff/issues/131#issuecomment-241273829,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAgfvswxopCWa1llTBih1CNLk9jdw5EDks5qiJsIgaJpZM4JpS2J
.

That's exactly what fuzzy diffing is, is it not? Regardless, I don't want
the library to make this decision for the user when they can do it
themselves.
On Sun, Aug 21, 2016 at 1:41 PM Jesús Leganés Combarro <
<EMAIL_ADDRESS>wrote:

I was thinking about this posibility too, but the point is that if there
are several chunks on the diff, failing one of them then it doesn't makes
sense to apply the other, the patch only makes sense to be applied at once
as a single item.
El 21/8/2016 20:38, "Kevin Decker"<EMAIL_ADDRESS>escribió:

I disagree. The user should decide how they want to handle this. They may
want to have everything possible apply and be notified about what did
not.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kpdecker/jsdiff/issues/131#issuecomment-241273829,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AAgfvswxopCWa1llTBih1CNLk9jdw5EDks5qiJsIgaJpZM4JpS2J
.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/kpdecker/jsdiff/issues/131#issuecomment-241274018,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAL_JqjC7fLWuYfCg7mS39oE_1SEEHVuks5qiJvlgaJpZM4JpS2J
.

That's exactly what fuzzy diffing is, is it not?

No, fuzzy diffing is about one patch can't be directly applied on the
position it's originally defined, what I'm talking about here are the
chunks inside a single patch: if a chunk can't be applied, the full patch
must be discarded because it can be applied.

Regardless, I don't want
the library to make this decision for the user when they can do it
themselves.

I disagree on that, but it's your library. Just curious, can you give a use
case where an user would not want to discard a chunk of a patch that can't
be applied and apply the patch partially?

Perhaps I'm not understanding what the input data is here. Since you're going to have to write a test to get coverage on this, how about showing me the test input that would cause this.

Sorry, I did not remember what this API did exactly. My argument is slightly different, but still had the same outcome. Since this is not atomic, if a particular file fails but the ones prior to it succeed, then the system will be left in an indeterminate state that the API is not smart enough to recover from, as some file may have been changed and others not. By simply throwing vs. returning a list of the files that have failed, the caller is also not able to recover from the error.

the system will be left in an indeterminate state that the API is not smart enough to recover from

It could be done... but I admit it would not be so simple.

By simply throwing vs. returning a list of the files that have failed, the caller is also not able to recover from the error

This list should be done by the user anyway, isn't it? The API is not giving it...


Run a specific piece of code

Good afternoon, how are you?
I would like to know if it is possible to execute a specific piece of code instead of executing the whole code.
Currently I use the :RunFile command, but I would like to be able to select a piece of code in VISUAL MODE and run it.
Is it possible to do this?
Congratulations on your plugin, it is just perfect :)

Thank you for the beautiful words, it is not in my plans to implement this, since I do not use this function, but maybe you can venture and do this RPL with pleasure I accept your PR.As I told you, I don't usually use this characteristic perhaps in the future, try to implement it

Good afternoon @CRAG666 , thanks for the reply.
Unfortunately at the moment I don't have much affinity with the Lua language, so much that my init.vim is all in vimscript 😅.
But thanks anyway, thanks again for your great plugin and have a great day :)
OBS: If someone see this Issue having the same problem, what I did to be able to run it was install the ipython and open a side terminal with it open, so I could copy the piece of code I want to test and paste it in :)


Allow CUDA architecture to be specified as cmake option

As discussed on Discord: when building on a research cluster, CUDA+cuDNN are present but no GPU is attached, so the build fails. This change allows the user to specify the architecture as a command line option, e.g.
cmake -DDARKNET_CUDA_ARCHITECTURES="60;70" ..

Thank you.  Your fix was merged into v3-dev.


Chapter 2.2: Infinite boot loop

Ok, this one actually isn't my fault. I set up a full-fledged 64-bit Linux VM and installed all the dependencies for building. But QEMU is again, showing an infinite boot loop. First I thought that I did something horribly wrong, so I replaced my source files with the ones provided in chapter 2.2 - Still no avail! It seems that the issue in chapter 2.2 breaks every single chapter ahead of that.
Everything works just fine up until chapter 2.1 by the way.

Hi @HackerDaGreat57, I am unable to reproduce this issue, and since I don't have anything to go on besides "infinite loop" I'm afraid there's nothing I can do to help you. The code for the bootloader in Chapter 2.2 is identical to earlier chapters, so you may want to try using the debugger script to figure out what is going wrong.
In the future, I will need more detailed information about the issue in order to help fix it. The only supported use case is when the files are in the repository on the latest version of the master branch. If you are moving files around or copying their contents elsewhere, then it is your responsibility to ensure that these files work with your environment. To validate the chapter as it was originally written, you can run $ git fetch; git reset --hard origin/master followed by git clean -fdx. If the problem persists, you may have other issues with QEMU which I will not be able to solve.


Unexpected test case for eth_syncing PRC

Current Behavior
The test case for eth_syncing may be wrong:
https://github.com/axonweb3/axon/blob/6fe5777e0b4a9b994dc84a56a00005745fd05085/tests/e2e/src/eth_syncing.test.js#L5-L19
Expected Behavior
eth_syncing is supposed to return an object with sync status data or FALSE,

return False|Boolean when the node is not syncing
or return the following fields
startingBlock: QUANTITY - The block at which the import started (will only be reset, after the sync reached his head)
currentBlock: QUANTITY - The current block, same as eth_blockNumber
highestBlock: QUANTITY - The estimated highest block

See https://ethereum.org/en/developers/docs/apis/json-rpc/#eth_syncing
Relevant log output
> curl --location --request POST 'https://rpc-alphanet-axon.ckbapp.dev/' \
--header 'Content-Type: application/json' \
--header 'Accept: */*' \
--data-raw '{
    "id": 42,
    "jsonrpc": "2.0",
    "method": "eth_syncing",
    "params": []
}'

# Result
{"jsonrpc":"2.0","result":false,"id":42}

https://github.com/axonweb3/axon/blob/6fe5777e0b4a9b994dc84a56a00005745fd05085/core/consensus/src/synchronization.rs#L543-L566


Provider help topics are missing

Steps to reproduce

First, run Update-Help from an elevated / sudo prompt to ensure that the latest topics have been downloaded.

# This works in WinPS.
Get-Help -Category provider Environment

Expected behavior
The Environment PS provider's help topic should print.
Actual behavior
An error about a missing file is reported.
Get-Help : System.Management.Automation.dll-Help.xml
At line:1 char:1
+ Get-Help -Category Provider Environment
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : OpenError: (:) [Get-Help], FileNotFoundException
+ FullyQualifiedErrorId : LoadHelpFileForTargetFailed,Microsoft.PowerShell.Commands.GetHelpCommand

Environment data
PowerShell Core v6.1.0 on macOS 10.14
PowerShell Core v6.1.0 on Ubuntu 16.04.5 LTS
PowerShell Core v6.1.0 on Microsoft Windows 10 Pro (64-bit; Version 1803, OS Build: 17134.165)

I can't find any Provider help in v7.2.2 on Win10 21H2 x64 either, though I can see the docs online.
eg Both of the following do not return the expected docs
Get-Help -Category Provider
Get-Help -Name *filesystem*

Both the above work in Windows PowerShell 5.1.

This is due to the PowerShell team migrating the docs from the help xml to about topics. I don't agree with the change but its still there technically but breaks the -Category parameter search.
Get-Help about*provider*

Name                              Category  Module                    Synopsis
----                              --------  ------                    --------
about_Alias_Provider              HelpFile
about_Certificate_Provider        HelpFile
about_Environment_Provider        HelpFile
about_FileSystem_Provider         HelpFile
about_Function_Provider           HelpFile
about_Providers                   HelpFile
about_Registry_Provider           HelpFile
about_Variable_Provider           HelpFile
about_WSMan_Provider              HelpFile

This is due to the PowerShell team migrating the docs from the help xml to about topics.
Get-Help about*provider*

Name                              Category  Module                    Synopsis
----                              --------  ------                    --------
about_Alias_Provider              HelpFile

Even after "Get-Module -ListAvailable | Update-Help -Force", your command above still gives me no results in PS 7.2.6?!

Thank you @mklement0 -- as mentioned this was due to a migration to about topics.  Get-Help *provider* should provide the expected results.


use_websockets seems to be no longer working

It seems the webpage option to switch between websockets and ajax is no longer supported. From my tests, even if I set use_websockets=False, justpy still opens websockets and all event communication goes through that.
I am thinking of usecase where a websocket connection is not activated until user credentials are verified but it no longer feasible.

We need to update the docs here at https://justpy.io/reference/webpage/. The docs says use_websockets = False should be set
on WebPage instance. But we only check the class variable --
context = {
            "request": request,
            "page_id": load_page.page_id,
            "justpy_dict": json.dumps(page_dict, default=str),
            "use_websockets": json.dumps(WebPage.use_websockets),
            "options": template_options,
            "page_options": page_options,
            "html": load_page.html,
            "frontend_engine_type": FRONTEND_ENGINE_TYPE,
            "frontend_engine_libs": FRONTEND_ENGINE_LIBS
        }

I will create a pull request with updated docs.

@sandeep-gh  thank you for pointing out this problem

This is really legacy ugly.  Currently
import justpy as jp

will already invoke
def justpy(
    func=None,
    *,
    start_server: bool = True,
    websockets: bool = True,
    host: str = HOST,
    port: int = PORT,
    startup=None,
    init_server: bool = True,
    **kwargs,
):

the test reveals that it doesn't work as expected right now the html is
 let justpy_core=new JustpyCore(
                this, // window
                0, // page_id
                'JustPy', // title
                'true', // use_websockets

when explicitly having set WebPage.use_websockets to False.
Global variable are so evil ...

Yes, shouldn't be using global variables. For now, being able to set use_websockets per page is probably best.
Once, the entry point to justpy is settled a bit, a global option to turn off websocket for the entire duration of app can also be given.

see #685


Make PREFIX used after .conf include

Proposed solution for issue #478

That wouldn't work afaict (haven't actually tested it), bacaus of this:
https://github.com/YosysHQ/yosys/pull/1051/files#diff-b67911656ef5d18c4ae36cb6741b7965R68
LDFLAGS := $(LDFLAGS) -L$(LIBDIR)

You are moving LIBDIR after this line, and because its using := it means $(LIBDIR) is being evaluated right there.

Ah you are right, missed that one, will investigate other options


Error dmall

An error occurred while running the command: ReferenceError: Permissions is not defined

i Gotted This Issue
Solve This

Use the github issues tab and please document your issue properly
Sent from my iPhone

On Feb 29, 2020, at 2:19 AM, Mahmudul-Hasan-Mahin<EMAIL_ADDRESS>wrote:

i Gotted This Issue
Solve This
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

More than likely you haven't set up the bot properly. I just deployed it myself without issues. Feel free to declare another issue if you still have this error, however next time please enter more information, especially including what you have done to set up the bot so far.


Fix bugs

The following changes have been made to this PR:

[x] Replaced price with course duration in the form filed
[x] Disabled all those dates that are already passed now the user can't select a date from the past
[x] Fixed linter errors

Hello @Atifzada
Great job! There is nothing else to say other than... It's time to merge it :shipit:
Congratulations!
🥳

Highlights

No linter errors :heavy_check_mark:
Code working as intended

Cheers and Happy coding!
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.


Use the default theme when creating a theme with extendTheme

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
The parent theme is passed to createTheme, so that its values can be arbitrarily used in the new theme. This doesn't seem to be possible with the new extendTheme API.
Examples 🌈
const theme = extendTheme({
  colorSchemes: {
    light: {
      palette: {
        extra: { main: '#d14836', contrastText: '#fff' },
      },
    },
    dark: {
      palette: {
        extra: defaultTheme.colorSchemes.dark.palette.primary, // how do I do this?
      },
    },
  },
});

Motivation 🔦
No response

It doesn't look like this bug report has enough info for one of us to reproduce it.
Please provide a CodeSandbox (https://mui.com/r/issue-template), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem.
Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve

How do I migrate code like this to CssVarsProvider and extendTheme?
<ThemeProvider theme={outerTheme => createTheme({ ...outerTheme, typography: { fontSize: 12 } })}>
...
</ThemeProvider>

I believe you can do the following:
import { Experimental_CssVarsProvider as CssVarsProvider } from '@mui/material/styles';
import { experimental_extendTheme as extendTheme } from '@mui/material/styles';

const defaultTheme = extendTheme();

const theme = extendTheme({
  colorSchemes: {
    light: {
      palette: {
        extra: { main: '#d14836', contrastText: '#fff' },
      },
    },
    dark: {
      palette: {
        extra: defaultTheme.colorSchemes.dark.palette.primary,
      },
    },
  },
});

export default function App() {
  <CssVarsProvider theme={theme}>...</CssVarsProvider>;
}

Does this work for you?

Yes, sorry, I wasn't clear. The theme prop can be a function in ThemeProvider but not in CssVarsProvider. So how do I migrate code like this to CssVarsProvider and extendTheme?
<ThemeProvider theme={outerTheme => createTheme({ ...outerTheme, typography: { fontSize: 12 } })}>
...
</ThemeProvider>

Do you have two ThemeProvider's? One being the outer one?

I think @siriwatknp is working on it in https://github.com/mui/material-ui/pull/35277. You can also see the discussion here: https://github.com/mui/material-ui/discussions/30485#discussioncomment-1917195

Since you are using extendTheme, I assume that you are using CSS variables.
You can do this:
const theme = extendTheme({
  colorSchemes: {
    light: {
      palette: {
        extra: { main: '#d14836', contrastText: '#fff' },
      },
    },
    dark: {
      palette: {
        // when mode changes to `dark`, the value of `var(--mui-palette-primary-main)` will be `theme.colorSchemes.dark.palette.primary`.
        extra: 'var(--mui-palette-primary-main)',
      },
    },
  },
});

Note that if you have custom cssVarPrefix, you should replace mui with that value, e.g.:
const theme = extendTheme({
  cssVarPrefix: 'custom',
  colorSchemes: {
    light: {
      palette: {
        extra: { main: '#d14836', contrastText: '#fff' },
      },
    },
    dark: {
      palette: {
        // when mode changes to `dark`, the value of `var(--mui-palette-primary-main)` will be `theme.colorSchemes.dark.palette.primary`.
        extra: 'var(--custom-palette-primary-main)',
      },
    },
  },
});

@siriwatknp What's the recommended way to migrate the following code?
<ThemeProvider theme={outerTheme => createTheme({ ...outerTheme, typography: { fontSize: 12 } })}>
...
</ThemeProvider>

@siriwatknp What's the recommended way to migrate the following code?
<ThemeProvider theme={outerTheme => createTheme({ ...outerTheme, typography: { fontSize: 12 } })}>
...
</ThemeProvider>

Do you mind sharing the full code via CodeSandbox? That way I can explain which part you have to change.


Codeunit 22 - Event: OnBeforeCheckItemTracking - change signature

Please change the signature of OnBeforeCheckItemTracking in Codeunit 22:
Before:
procedure CheckItemTracking()
var
    IsHandled: Boolean;
begin
    IsHandled := false;
    OnBeforeCheckItemTracking(ItemJnlLine, ItemTrackingSetup, IsHandled);
    if IsHandled then
        exit;

[..]

[IntegrationEvent(false, false)]
local procedure OnBeforeCheckItemTracking(ItemJournalLine: Record "Item Journal Line"; ItemTrackingSetup: Record "Item Tracking Setup"; var IsHandled: Boolean)
begin
end;

Suggestion:
procedure CheckItemTracking()
var
    IsHandled: Boolean;
begin
    IsHandled := false;
    OnBeforeCheckItemTracking(ItemJnlLine, ItemTrackingSetup, TempTrackingSpecification, IsHandled);
    if IsHandled then
        exit;

[..]

[IntegrationEvent(false, false)]
local procedure OnBeforeCheckItemTracking(ItemJournalLine: Record "Item Journal Line"; ItemTrackingSetup: Record "Item Tracking Setup"; var TempTrackingSpecification: Record "Tracking Specification" temporary; var IsHandled: Boolean)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


fix(batch): release epoch at the end of the distributed query if it contains lookup join

I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
This section will be used as the commit message. Please do not leave this empty!
Please explain IN DETAIL what the changes are in this PR and why they are needed:

As title.

Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Documentation
If your pull request contains user-facing changes, please specify the types of the changes, and create a release note. Otherwise, please feel free to remove this section.
Types of user-facing changes
Please keep the types that apply to your changes, and remove those that do not apply.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note
Please create a release note for your changes. In the release note, focus on the impact on users, and mention the environment or conditions where the impact may occur.
Refer to a related PR or issue link (optional)
https://github.com/risingwavelabs/risingwave/issues/6979

This seems to be a workable fix, however, it will definitely defer the release of the pinned snapshot. 🤔 Is it possible to also record the stages with lookup join?

Even if we find out the stage of the lookup join, we can't release the pinned snapshot right after it gets scheduled. Previously we tried to release the pinned snapshot right after all scan iterators were created. I think as long as we hold the iterators, the storage can't release its corresponding epoch which is almost equivalent with releasing the epoch at the end of the query, because in most cases scan iterators end with the same time as the whole query.

Makes sense. I've recalled it wrong since long ago, the table scan did not pin a specific version, and it's the frontend's responsibility to pin the snapshot for the whole process. 🤣

BTW, is it possible to still eagerly unpin the snapshot if there's no lookup join? Anyway, let's get this fix merged now.

It is still possible to unpin the snapshot if there's no lookup join.

Discussed with @chenzl25 offline. Lookup join will create storage iterators during its exeuction, not during scheduling. Based on the current interface, I cannot think of a way to do early epoch unpin in this case. To do that, we may need to do either of the following:

Expose the seek interface for storage table iterator. Lookup join can create the iterator during scheduling and call seek during its execution. However, since we use stream for storage table iterator, seek is counter-intuitive.
Expose the concept of storage version and allow upper layer to create multiple iterators on top of a version. This needs a bigger refactor and adds burden on the upper layer to unpin version.

IMO, we can delay epoch unpin if the query has lookup join for now, given that we don't expect batch query to run for a long time in the serving use cases. We can optimize it when we do see long running batch queries in the future.

I have reimplemented in this way, only delay epoch unpin for lookup join. Please take a lookup again. @BugenZhao @BowenXiao1999

@BowenXiao1999
I forget the intention of the old implementation,
We probably wanted to make sure that compaction can still happen -> new version, but the version/snapshot held by the iterator cannot be vacuumed.
Can't remember exactly......


Company ledger - when click on unbilled project redirect to unbilled project

Describe the bug

when click on unbilled project in company ledger page it redirects to transaction page but it should redirect to unbilled project

Screenshots

Video
https://www.berrycast.com/conversations/ed043a69-7c1f-5865-a87a-07a3d2167ff3
Post
https://community.easycloudbooks.com/t/Questions or Bugs/bca44e96-22e6-42c2-a124-839cc9997288

As stated before,
Unbilled Projects is part of Transaction Module, it is fully interlinked due to Selection and Create bill from it functionality on Unbilled Project Section,
so Direct to Un billed Project is not possible.


V5 - AKSampler will not stop sounding and keep repeating the note indefinitely.

We had to migrate our usage of AudioKit from version 4 to version 5 due compile issues with Xcode 12 (iOS 14), which will be the new standard in a couple weeks and will be the only version allowed to publish apps to the app store.
With this version 5 we have the problem that the note/sound never stop sounding and being repeated really fast.
I've tried the CocoaPods version of version 5 and the development and master branch of audiokit of version 5, with all the same result as described above.
The only interaction we are doing with the AKSampler are the following:
AKSampler.releaseDuration
AKSampler.masterVolume
AKSampler.loadSFZ(path:fileName:)
AKSampler.play(noteNumber:velocity:) <-- called when the user touches a button
AKSampler.stop(noteNumber:) <-- called when the user no longer touches a button "releases"
AKSampler Settings
attackDuration: 0.0
holdDuration: 0.0
decayDuration: 0.0
sustainLevel: 1.0
releaseHoldDuration: 0.0
releaseDuration: 0.8

Could this issue be looked after, since we are quite reliant upon the usage of AudioKit in our app and it will become a big impediment once iOS 14 is released. Otherwise version 4 should be made compatible with Xcode 12, if there are plans for that it would be appreciated to be aware of it.
Linked Issue
https://github.com/AudioKit/AudioKit/issues/2136

Yeah, that's on my radar, and I can have a look at it over the next few days.

Do you think you could create a bare bones project showing the issue or share your code with me? It would just be easier and quicker for me to work on a project.


How to take heap snapshot with version 0.31.3?

Environment

Component
Version

Node.js
v16.14.2

Client (Chrome/Chromium/...)
NodeJS

OS running Node.js
Mac V12.4

OS running the client
N/A

chrome-remote-interface
0.31.3

Is the client running in a container? NO
Description
I'm currently debugging a NodeJS program that runs with node --inspect index.js and connect with CDP as following example. and the HeapProfiler seems deprecated from the type definition. I'm wondering how can I take Heap snapshot with current version of chrome-remote-interface.
Example
const CDP = require('chrome-remote-interface');

async function example() {
  const _debugger = await cdp({ port: 9229 }) // default node debugging port
  _debugger.HeapProfiler.addHeapSnapshotChunk
}

example();

and the HeapProfiler seems deprecated from the type definition

Where does exactly is this written?

and the HeapProfiler seems deprecated from the type definition

Where does exactly is this written?

Plesase refer to this https://chromedevtools.github.io/devtools-protocol/tot/HeapProfiler/

Nowhere it says that HeapProfiler is deprecated...


Programmatically get default branch name

At the moment this is hard-coded as "main" but I think we can get the default branch out and pass that as fallback argument to determine_ref

Does this work with graphQL - if so do this

I can't find a way of doing this with git2r - I think this works:

It adds gert as an imports (but that is already required as we import devtools which depends on usethis which imports gert) - also I think we should move to using gert anyway
(Note usethis has a function git_branch_default which may be helpful)

Closing in favour of https://github.com/openpharma/staged.dependencies/issues/134


Adding alert dialogue for confirmation of deletion of temp. files in setting..

adding an alert dialogue in setting for confirmation of deletion of temp. files ..

for issue #391


Update a comment to reflect the possible values for the LITANI environment variable

Issue #, if available:
Description of changes:
Making an update as suggested by @markrtuttle here.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thanks, Angelo.


Player icon can be transparent

  for (i = 0; i < gameData.playerCount; i++) {     gameData.Players.push(       new Player(i, '#' + (((1 << 24) * Math.random()) | 0).toString(16))     );   }
When generating a color to represent the player, the color can be transparent. This affects the ability to see the player on the game board and leads them to only be represented by the player icon border.

const generateRandomColor = () => {
  let options = '0123456789ABCDEF';
  let color = '#';
  for (let index = 0; index < 6; index++) {
    color += options[Math.floor(Math.random() * 16)];
  }

  return color;
};

Added new generateRandomColor function which, hopefully, going forward should only generate valid hexadecimal color codes. Ideally, this should fix the issue of occasional transparency.
Commit: https://github.com/arevi/Kill-Doctor-Lucky-Web-Port/commit/3e2dbd0c08ff4e8a7cb0afa04a1f72fe69e5e363

Cool solution, also tested this and verified that it works.

Have not witnessed any transparent character emblems since testing this fix.


Relax version constraint on bitfield

0.13.2 is still used by other crates in the ecosystem (cortex-m, atsamd-hal). Since the breaking changes in bitfield 0.14 do not affect mcan internals, the choice can be left to the user crate.

Counter arguments:

Now, mcan does not use bitfield API that differs between 0.13.x and 0.14.x but it might by accident introduce code that does and it might get overlooked in CI.
Considering that crate is basically just a set of macros, extra code that comes from having multiple versions of bitfield in the same application are negligible.
mcan should not care about potential dependees using different versions of bitfield

I suggest not merging this change.

Yes, those seem like good enough reasons not to do this.


chore: bump func from 0.18 to 0.21

Changes

:broom: add formulae for versions 0.19, 0.20 and 0.21
:broom: make func 0.21.2 the latest

/kind enhancement
Fixes: https://github.com/knative-sandbox/kn-plugin-func/issues/794
Release Note
Adds versions 0.19, 0.20 and 0.21 of func

@rhuss ty for the feedback - obviously I was unaware! Updated now, ptal.


HASTAC latest post widget not updating with most recent

Jackie Cahill reached out because the HASTAC "latest posts" widget is showing posts from 2022 and she can't get it to sort them from newest to oldest. We have had a similar issue with this before.

HASTAC uses the WP RSS Aggregator plugin to combine feeds from its sub sites into a single feed for display on the frontpage. WP RSS Aggregator is causing a fatal error because it uses a library that some other plugin is also using and doesn't check for that. I'm working on a fix.

Fixed.


Major refactor.

Because I wanted to Get :poop: Done, I wasn't too concerned about the
quality of the code. And I always thought "I can just refactor it
later." But, as it turns out, the more junk you throw on a pile, the
harder it is to fix.
 Namely:

keyboards
interrupts
the pic crate

And changes what's there a bit. For starters, vga's kprintln is now in
the kernel itself.
We also have a new KernelContext struct. This will hold all of the state
for the kernel, and our first bit of state is the vga driver. Instead of
a single, global kernel lock, we'll choose a lock for each bit of
relevant state.
We can even keep it entirely on the stack of kmain, rather than having
it available globally. The only thing that might not work for that is
the panic handler; I'm not sure what to do there.

This is very interesting! 💃

Gonna :shipit:
This code will live in the git history, we'll get it back in at some point :)

Oo fun! New code to read


Proposal: Enable customization of namespace and type name suffixes for the generated implementation types.

In C++/WinRT 1.0 and 2.0, implementation types are generated with the same name as the projected types in the implementation and factory_implementation namespaces.
Example:
// MyClass.idl
namespace MyNamespace
{
    [default_interface]
    runtimeclass MyClass
    {
        MyClass();
    }
}

// MyClass.h
#pragma once

#include "MyClass.g.h"

namespace winrt::MyNamespace::implementation
{
    struct MyClass : MyClassT<MyClass>
    {
        MyClass() = default;
    };
}

namespace winrt::MyNamespace::factory_implementation
{
    struct MyClass : MyClassT<MyClass, implementation::MyClass>
    {
    };
}

Problem statement
The fact that there are two types with the same name, is confusing to many engineers and requires careful examination of the included headers to determine if an implementation or a projected type would be instantiated.
A possible solution is to fully qualify the type. This is the approach that the code generated by cppwinrt.exe takes, but has various problems:

The generated implementation stubs only fully qualify types implemented within the same component.
It is only required for types implemented within the same component, requiring engineers to know if a type they use is implemented in the same component or not.
It is counter-productive to write fully qualified type names as namespaces can be quite long.
Stack allocations cannot be detected within a coroutine, see limitation of heuristic below.

Evidence of the problem
There is evidence that this is in fact a problem for component authors.
In C++/WinRT 2.0 a heuristic was added for debug builds to assert when an implementation type is created on the stack, see https://docs.microsoft.com/en-us/windows/uwp/cpp-and-winrt-apis/news#help-with-diagnosing-stack-allocations. However, as mentioned in the linked document, this doesn't work for coroutines.
Various bugs on my team were caused by engineers making this mistake or accidentally forgetting to fully qualify the type.
The Windows UI Library team doesn't seem to be using the implementation namespace for their implementation types, though it is unclear if that is because of this problem.
Proposal
The proposal is to allow customization of the namespace and type names for the implementation types using two new command line parameters for cppwinrt.exe:

-component_namespace_suffix: Namespace suffix used for the namespace for the implementation types. This would default to implementation as that's what the V1 and V2 behavior is.

-component_type_suffix: Type suffix used for the name of the implementation types. This would default to empty string as in C++/WinRT V1 and V2 implementation types have the same name as the projected types.

This would allow for differentiating the implementation types by type name instaed of by namespace name. A project type MyClass could have an implementation type MyClassImpl (I picked Impl as it resembles the pImpl idiom).
Examples
Current C++/WinRT V1/V2 behavior would be achieved using the defaults or by specifying -component_namespace_suffix "implementation".
Using -component_namespace_suffix "" and -component_type_suffix "Impl", would generate the following:
// MyClass.h
#pragma once

#include "MyClass.g.h"

namespace winrt::MyNamespace
{
    struct MyClassImpl : MyClassImplT<MyClassImpl>
    {
        MyClassImpl() = default;
    };
}

namespace winrt::MyNamespace::factory
{
    struct MyClassImpl : MyClassImplT<MyClassImpl, implementation::MyClassImpl>
    {
    };
}

I can contribute this, but would like to get feedback from other C++/WinRT users and the C++/WinRT team first.

Thanks for sending out the proposal before a PR! It's agreat way of collecting feedback before you invest a lot of time on an implementation. It sounds good to me. I'd also be interested in whether this would help @jevansaks adopt the generated module.g.cpp implementation. My only initial feedback would be to use lower_case option names as in -component_type_suffix Impl.

Updated with lower_case option names. I'm still thinking through options to see if this is the right set of knobs to expose.

Does XamlCompiler currently assume anything for the C++/WinRT generated code about the type names? I assume it does. @danzil ?

I'd also be interested in whether this would help @jevansaks Jevan Saks FTE adopt the generated module.g.cpp implementation.

It would help but I don't think it solves it because module.g.cpp assumes two things about my implementation:

The naming convention of the implementation header files
The namespace and naming convention of implementation types.

This proposal would help # 2 but not # 1 (yet). Also our convention is that implementation types live in the global namespace so I don't think a simple "suffix" fully solves # 2 for us.
@jlaanstra would there also be a -component_factory_namespace parameter? Or do we assume that factory types live in ::factory under the -component_namespace_suffix?

Thanks @jevansaks, C++/WinRT 2.0 solves # 1 so this would get us closer. We'd potentially need this proposal to also support your global namespace approach.

@jevansaks Current proposal doesn't include anything for the factory namespace. Do you think it's important to have that?

What I see in module.g.cpp today (I'm using cppwinrt.exe out of the SDK still) is that it assumes my factory types are in winrt::Foo::Bar::factory_implementation::Baz. So I only care about the factory namespace if module.g.cpp continues to care about it in this proposal.

When you use /opt in C++/WinRT 2.0 the module.g.cpp doesn't even care about that. It only looks the linker to resolve a function named void* winrt_make_Namespace_Name(). This avoids both the compiler rebuild and the dependence on any particular namespace/name for the actual implementation type. This function must simply return a pointer to the factory and you can define that wherever you like. For example:
void* winrt_make_Namespace_Name()
{
    return winrt::detach_abi(winrt::make<MyCustomNamedFactory>());
}

The only thought I still have is: Should we actually allow customization of the suffix names or should we force implementation if you use the namespace suffix and Impl if you use the type suffix?

If Jevan is happy generating his DLL exports and ignore the generated module.g.cpp that's also OK.
Yes, I'd still need to see a compelling case for more flexibility as it adds complexity and a support cost. I actually like the more uniform binary model. Default is what we have today "implementation" namespace and the alternative is "-Impl" name.

The only name that the Xaml Compiler assumes for C++\WinRT is the namespace "implementation" and the reason for that is because we didn't have uniform type construction at that time (i.e. local types still needed winrt::make while projection types would activate using their constructor).

Good point. Thanks Daniel. Now that C++/WinRT provides uniform construction, this becomes far less confusing. I am also addressing the limitations in the ability for C++/WinRT to detect and diagnose stack allocation errors at compile time and 100% of the time. Perhaps there is then less reason to support this degree of customization and avoid the added the complexity.

@danzil @kennykerr I assume the xaml compiler will switch to use uniform construction when running with C++/WinRT 2? I still feel there is value in having easy distinguishable type names for implementation types.

Yes, @danzil and I are starting to talk about the design for the next major update to the Xaml compiler.

I still feel there is value in having easy distinguishable type names for implementation types.

The question is whether there is enough value to warrant the added complexity. I don't think there is and if you really want to go that route you can still do what Jevan has done and name it whatever you like.

The question is whether there is enough value to warrant the added complexity. I don't think there is and if you really want to go that route you can still do what Jevan has done and name it whatever you like.

I'll definitely give that a try and see how much extra code I have to write to make that work.


New9

Fixes #662
Describe the changes you have made in this pr -
Moved privacy controller from logix controller to seperate controller.

Coverage decreased (-0.3%) to 82.975% when pulling 4a5f06050a092dd39cc1e51807862955827e3dae on mohit-003:new9 into 6f6dfff8fae733634c375b33e74d5232147c7452 on CircuitVerse:master.

@alanjsph Please review my task.

Done @ankitkataria


ci(macos): install ccache when needed

This change is

Added install of pkg-config also, which vcpkg needs during the quickstart-cmake build


[VS Code] Live Share extension failed to initialize, try to reload the VSCode window and try again.

Error:
Live Share extension failed to initialize, try to reload the VSCode window and try again.
Steps to Reproduce:

Version Data

extensionName
VSLS

extensionVersion
0.3.514

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.25.1

platformName
Linux

platformVersion
4.15.0-30-generic

Thanks for reporting this! Could you try uninstalling and reinstalling the extension? That may help unblock this issue. We’re tracking this issue via #660, so I’m going to close this as a duplicate in order to consolidate the conversation. But let us know if the mentioned workaround helps. Thanks!


Need a example for share screen outside the app

From https://stackoverflow.com/questions/63572116/tok-box-screen-sharing-is-not-working-outside-my-app/63572744#63572744, I can see a comment from the Tokbox team that you're working on a sample application that shares screen entire device's screen outside of the app (Like Facebook Messenger app). Hope I can see this example soon.

Thanks, @ngocson952006.
I spoke to Product about your request: https://jira.vonage.com/browse/OPENTOK-49524.  Will keep you posted.

You can have a look here for some examples of using media projection on Android and ReplayKit on iOS to achieve global screenshare:
https://github.com/nick-vasic/opentok-react-native/blob/master/android/src/main/java/com/opentokreactnative/OTScreenCapturer.java and https://github.com/nick-vasic/opentok-react-native/blob/master/android/src/main/java/com/opentokreactnative/ScreenCaptureMediaProjectionService.java
iOS:
https://github.com/nick-vasic/opentok-react-native/blob/master/ios/OpenTokReactNative/OTScreenCapture.m