Cocos2d crash on iOS9 simulator - cocos2d-iphone

2015-10-26 21:30:19.093 QP[4494:55623] 39:
OpenGL error GL_INVALID_VALUE detected at -[CCGraphicsBufferGLUnsynchronized setup] 121
2015-10-26 21:30:19.096 QP[4494:55623] *** Assertion failure in -[CCRenderStateGL initWithBlendMode:shader:shaderUniforms:copyUniforms:], /Users/quantum/code/fuck/quantumpilot/qp/Source/libs/cocos2d-iphone/cocos2d/CCRendererBasicTypes.m:313
2015-10-26 21:30:19.139 QP[4494:55623] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'CCRenderState: Shader is nil'
Why is this happening? Works fine on my 8.4.1 device. Will test on 9.1 device.
EDIT
From http://forum.cocos2d-objc.org/t/xcode-7-ios9-beta/17346/20
added to static NSString *CCShaderHeader in CCShader.m
#"#ifdef GL_ES\n"
#"#ifdef GL_OES_standard_derivatives\n"
#"#extension GL_OES_standard_derivatives : enable\n"
#"#endif\n"
#"#endif\n"
removed from CCDrawNode.m
#"#ifdef GL_ES\n"
#"#extension GL_OES_standard_derivatives : enable\n"
#"#endif\n"
#"\n"
fixes it. Arcane.

Related

G4GDMLParser Evaluator : syntax error C++

I am trying to read a GDML file with G4GDMLParser:
...
G4GDMLParser parser;
parser.Read(G4Str_Filename, fValidate);
But it gives an error:
...
G4GDML: Reading materials...
G4GDML: Reading solids...
Evaluator : syntax error
-------- EEEE ------- G4Exception-START -------- EEEE -------
*** G4Exception : InvalidExpression
issued by : G4GDMLEvaluator::Evaluate()
Error in expression: 40.0
*** Fatal Exception *** core dump ***
**** Track information is not available at this moment
**** Step information is not available at this moment
-------- EEEE -------- G4Exception-END --------- EEEE -------
*** G4Exception: Aborting execution ***
Signal: SIGABRT (Aborted)
I tried putting GDML file next to the executable but it didnt help.
I found it problem is My locale TR uses " , "not " . " for floats just set your locale somewhere in your code;
std::setlocale(LC_ALL, "en_US.UTF-8");
std::setlocale(LC_NUMERIC, "en_US.UTF-8");

WSO2 IS Unable to compile class for JSP

I'm using WSO2 IS 5.10 with docker and after making a change to the image, which has nothing to do with JSPs, opening the dashboard on the service provider list I see a white screen.
In wso2 log I found errors like this:
Servlet.service() for servlet [bridgeservlet] threw exception org.apache.jasper.JasperException: Unable to compile class for JSP:
An error occurred at line: [17] in the generated java file: [/home/wso2carbon/wso2is-5.10.0/lib/tomcat/work/Catalina/localhost/ROOT/proxytemp/hc_1893914628/org/apache/jsp/application/list_002dservice_002dproviders_jsp.java]
Only a type can be imported. org.wso2.carbon.identity.application.common.model.xsd.ApplicationBasicInfo resolves to a package
An error occurred at line: [118] in the jsp file: [/application/list-service-providers.jsp]
ApplicationBasicInfo cannot be resolved to a type
115: <%
116: String BUNDLE = "org.wso2.carbon.identity.application.mgt.ui.i18n.Resources";
117: ResourceBundle resourceBundle = ResourceBundle.getBundle(BUNDLE, request.getLocale());
118: ApplicationBasicInfo[] applications = null;
119:
120: String filterString = request.getParameter(ApplicationMgtUIConstants.SP_NAME_FILTER);
121: filterString = ApplicationMgtUIUtil.resolveFilterString(filterString);
this disappears when restarting the image.
I’d like to know what it’s due to

Sporadic failure in GLX

I am running OpenGL in headless mode with Xserver and invoking this api multiple times: https://github.com/RobotLocomotion/drake/blob/74292cacd1c42d6b3e682dc836254cdb834ea2e6/geometry/render/render_engine_vtk.cc#L311
Sporadically but almost always there is a
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 154 (GLX)
Minor opcode of failed request: 3 (X_GLXCreateContext)
Value in failed request: 0x0
Serial number of failed request: 61
Current serial number in output stream: 62
glxinfo:
glxinfo
name of display: :0
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 50 requests (50 known processed) with 0 events remaining.
Last lines of /var/log/Xorg.0.log logs:
[ 47757.261] (EE) Backtrace:
[ 47757.261] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x557e48dd2acd]
[ 47757.261] (EE) 1: /usr/lib/xorg/Xorg (0x557e48c1a000+0x1bc869) [0x557e48dd6869]
[ 47757.261] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f4cbddc7000+0x128a0) [0x7f4cbddd98a0]
[ 47757.261] (EE) 3: /usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so (0x7f4cba768000+0x479100) [0x7f4cbabe1100]
[ 47757.261] (EE)
[ 47757.262] (EE) Segmentation fault at address 0x8
[ 47757.262] (EE)
Fatal server error:
[ 47757.262] (EE) Caught signal 11 (Segmentation fault). Server aborting
Machine: 18.04.2-Ubuntu
NVIDIA-SMI 440.100 Driver Version: 440.100 CUDA Version: 10.2
Can someone please let me know what next to debug here?
I also see this in my own CI:
[ 18228.470] (EE) Backtrace:
[ 18228.470] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x55e0ca9fcacd]
[ 18228.470] (EE) 1: /usr/lib/xorg/Xorg (0x55e0ca844000+0x1bc869) [0x55e0caa00869]
[ 18228.470] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fce3e7d6000+0x128a0) [0x7fce3e7e88a0]
[ 18228.470] (EE) 3: /usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so (0x7fce3b177000+0x479100) [0x7fce3b5f0100]
[ 18228.470] (EE)
[ 18228.470] (EE) Segmentation fault at address 0x8
Different ASLR, but same low order bytes in the trace.
I'm using xorg-server 2:1.19.6-1ubuntu4.4.
[ 17925.887] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 17925.887] compiled for 1.6.99.901, module version = 1.0.0
[ 17925.887] Module class: X.Org Video Driver
[ 17925.887] (II) NVIDIA dlloader X Driver 440.100 Fri May 29 08:21:27 UTC 2020
I have not yet been able to debug this, unfortunately.
My off-the-cuff experience (not yet substantiated by data) is that this got much, much more frequent when Ubuntu force-upgraded everyone from nvidia 430 to nvidia 440 a few months ago.

Couldn't load realm-jni: findLibrary returned null

I'm writing an app and as a DB I've use Realm. Everything was fine, until the app was published. Now I've faced with this error on some devices:
java.lang.ExceptionInInitializerError
at io.realm.Realm.<init>(Realm.java:199)
at io.realm.Realm.createAndValidate(Realm.java:585)
at io.realm.Realm.create(Realm.java:554)
at io.realm.Realm.getInstance(Realm.java:527)
at com.magisto.utils.RealmUtils.createRealmInstance(RealmUtils.java:22)
at com.magisto.infrastructure.viewcount.repository.RealmViewStorage.<init>(RealmViewStorage.java:26)
at com.magisto.infrastructure.module.ViewStorageModule.provideViewStorage(ViewStorageModule.java:19)
at com.magisto.infrastructure.module.ViewStorageModule_ProvideViewStorageFactory.get(ViewStorageModule_ProvideViewStorageFactory.java:23)
at com.magisto.infrastructure.module.ViewStorageModule_ProvideViewStorageFactory.get(ViewStorageModule_ProvideViewStorageFactory.java:9)
at com.magisto.service.background.ViewCountingService.onHandleIntent(ViewCountingService.java:70)
at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:65)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.os.HandlerThread.run(HandlerThread.java:60)
Caused by: java.lang.UnsatisfiedLinkError: Couldn't load realm-jni: findLibrary returned null
at java.lang.Runtime.loadLibrary(Runtime.java:365)
at java.lang.System.loadLibrary(System.java:535)
at io.realm.internal.RealmCore.loadLibrary(RealmCore.java:144)
at io.realm.internal.SharedGroup.<clinit>(SharedGroup.java:35)
at io.realm.Realm.<init>(Realm.java:199)
at io.realm.Realm.createAndValidate(Realm.java:585)
at io.realm.Realm.create(Realm.java:554)
at io.realm.Realm.getInstance(Realm.java:527)
at com.magisto.utils.RealmUtils.createRealmInstance(RealmUtils.java:22)
at com.magisto.infrastructure.viewcount.repository.RealmViewStorage.<init>(RealmViewStorage.java:26)
at com.magisto.infrastructure.module.ViewStorageModule.provideViewStorage(ViewStorageModule.java:19)
at com.magisto.infrastructure.module.ViewStorageModule_ProvideViewStorageFactory.get(ViewStorageModule_ProvideViewStorageFactory.java:23)
at com.magisto.infrastructure.module.ViewStorageModule_ProvideViewStorageFactory.get(ViewStorageModule_ProvideViewStorageFactory.java:9)
at com.magisto.service.background.ViewCountingService.onHandleIntent(ViewCountingService.java:70)
at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:65)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.os.HandlerThread.run(HandlerThread.java:60)
I've used Realm version 0.82.0 from jcenter. The issue is was found on Samsung S4 mini, Samsung S5, Samsung Tab 3 7.0, and several other devices. How can I fix it?

repeatedly getting uncaught exception in firebug

my project suddenly was started to throwing exception in firebug,I've not added any new thing,I'm confused,the error:
uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMNSHTMLTextAreaElement.selectionStart]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: http://codeblogging.net/static/js/plugins.js :: :: line 99" data: no]
Line 0
I've just used django-tinymce in my project,but there was no problem until now,I removed the refrences to tinymce.js and tinymce-setup.js,but no difference!I really don't know what has happend!!
I finally updated firefox to 12 version and updated firebug to a compatible version,too.