Jade runtime has stopped working

Forums for specific tips, techniques and example code
sit
Posts: 13
Joined: Mon Sep 29, 2014 6:53 pm

Jade runtime has stopped working

Postby sit » Wed Oct 01, 2014 12:15 pm

Every now and then usually after I compile or reorg Jade stops working and a pop up box says "Jade runtime has stopped working" and closes the program all together.
Does anyone know how to stop this from happening as it is time consuming and annoying to reopen jade all the time ?

User avatar
BeeJay
Posts: 311
Joined: Tue Jun 30, 2009 2:42 pm
Location: Christchurch, NZ

Re: Jade runtime has stopped working

Postby BeeJay » Thu Oct 02, 2014 10:20 am

It sounds like there is something environmental on your machine that is causing it to crash repeatedly like this. I can't remember the last time I had a problem like this occurring, and it's certainly not something I see as frequently as it sounds like it's occurring for you.

Is anything being logged in your windows event logs to indicate a reason for the crash?

Which version of Jade are you running and on which version of Windows?

Cheers,
BeeJay.

User avatar
ghosttie
Posts: 181
Joined: Sat Aug 15, 2009 1:25 am
Location: Atlanta, GA, USA
Contact:

Re: Jade runtime has stopped working

Postby ghosttie » Fri Oct 03, 2014 1:41 am

Are there crash logs/process dumps?
I have a catapult. Give me all the money or I will fling an enormous rock at your head.

User avatar
BeeJay
Posts: 311
Joined: Tue Jun 30, 2009 2:42 pm
Location: Christchurch, NZ

Re: Jade runtime has stopped working

Postby BeeJay » Fri Oct 03, 2014 7:12 am

Are there crash logs/process dumps?
Their earlier question about enabling AutoComplete would suggest they're on a version of Jade 7, so unfortunately there won't be any crashlogs only process dumps which makes it harder to see which libraries were on the stack at the time of the crash. :(

I also meant to ask on my first response is there anything being logged in the jommsg.log file around the time of one of these crashes that may help shed light on the reason for the crashing?

Cheers,
BeeJay.

sit
Posts: 13
Joined: Mon Sep 29, 2014 6:53 pm

Re: Jade runtime has stopped working

Postby sit » Fri Oct 03, 2014 2:19 pm

Hi Beejay

Here is the info you asked about

Event log on pc

Log Name: Application
Source: Application Error
Date: 3/10/2014 1:19:01 p.m.
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: T
Description:
Faulting application name: jade.exe, version: 7.0.4.4, time stamp: 0x4f4d9cbe
Faulting module name: jomos.dll, version: 7.0.4.4, time stamp: 0x4f4d9cf6
Exception code: 0xc0000005
Fault offset: 0x000000000002522b
Faulting process id: 0x33e4
Faulting application start time: 0x01cfde9f16599143
Faulting application path: C:\Jade70\bin\jade.exe
Faulting module path: C:\Jade70\bin\jomos.dll
Report Id: dfc92c3b-4a92-11e4-8284-303a6452a2a5
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-10-03T00:19:01.000000000Z" />
<EventRecordID>10238</EventRecordID>
<Channel>Application</Channel>
<Computer>T</Computer>
<Security />
</System>
<EventData>
<Data>jade.exe</Data>
<Data>7.0.4.4</Data>
<Data>4f4d9cbe</Data>
<Data>jomos.dll</Data>
<Data>7.0.4.4</Data>
<Data>4f4d9cf6</Data>
<Data>c0000005</Data>
<Data>000000000002522b</Data>
<Data>33e4</Data>
<Data>01cfde9f16599143</Data>
<Data>C:\Jade70\bin\jade.exe</Data>
<Data>C:\Jade70\bin\jomos.dll</Data>
<Data>dfc92c3b-4a92-11e4-8284-303a6452a2a5</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

jommsg2.log file

2014/10/03 13:15:11.520 033e4-2e04 PDB: Database Restart Recovery...
2014/10/03 13:15:11.645 033e4-2e04 PDB: Commencing REDO phase - forward scan from (13,3380179) ...
2014/10/03 13:15:11.707 033e4-2e04 PDB: Processing journal C:/Jade70/system/journals/current/db0000000013.log
2014/10/03 13:15:11.707 033e4-2e04 PDB: journal physical end of file = 67108864
2014/10/03 13:15:11.863 033e4-2e04 PDB: journal actual end of file = 3401512
2014/10/03 13:15:11.863 033e4-2e04 PDB: Timestamp of last commit record: 03 October 2014, 12:01:08
2014/10/03 13:15:11.910 033e4-2e04 PDB: Timestamp of last journal record: 03 October 2014, 12:01:08
2014/10/03 13:15:12.035 033e4-2e04 PDB: No transactions to undo
2014/10/03 13:15:12.035 033e4-2e04 PDB: 131 journal records processed
2014/10/03 13:15:12.035 033e4-2e04 PDB: 0 uncommitted transactions backed out
2014/10/03 13:15:12.035 033e4-2e04 PDB: 11 committed transactions recovered
2014/10/03 13:15:12.035 033e4-2e04 PDB: 0 previously aborted transactions scanned
2014/10/03 13:15:13.004 033e4-2e04 PDB: checkpoint flush elapsed time=0 ms
2014/10/03 13:15:13.035 033e4-2e04 PDB: checkpoint sync files elapsed time=32 ms
2014/10/03 13:15:13.098 033e4-2e04 PDB: <<Check Point>> LSN=(13,3401512), minRecoveryLSN=(13,3401512), farthestBackLSN=(13,3401512), elapsed time=208 ms, by: end recovery
2014/10/03 13:15:13.176 033e4-2e04 PDB: _environ[12] cfile state changed from assigned to deleted
2014/10/03 13:15:13.176 033e4-2e04 PDB: removed C:/Jade70/system/_environ.dat
2014/10/03 13:15:13.879 033e4-2e04 PDB: Database recovery complete - Elapsed Time = 00:00:02.234
2014/10/03 13:15:13.941 033e4-2e04 PDB: Update timestamp for _system.bin: 29 February 2012 16:08:50.053779
2014/10/03 13:15:14.645 033e4-2e04 PDB: <<LICENSE RESTRICTION>>: Total active database size restricted to 2GB
2014/10/03 13:15:14.645 033e4-2e04 PDB: Max DB users set to: 35
2014/10/03 13:15:14.723 033e4-2e04 TDB: Max DB users set to: 35
2014/10/03 13:15:15.770 033e4-1f50 PDB: <<LICENSE RESTRICTION>>: Total active database size restricted to 2GB
2014/10/03 13:15:15.910 033e4-1f50 PDB: _rootdef.dat[40] opened, add: 73728 file bytes, active db size=73728 bytes
2014/10/03 13:15:16.192 033e4-1f50 Jom: Initializing: scm=RootSchema, oid=[1.1], scmNo=1, lvl=1
2014/10/03 13:15:16.192 033e4-1f50 Jom: Initializing: scm=BankingModelSchema, scmOid=[1280.9], scmNo=100, superScmOid=[1.1], superScmNo=1 , lvl=2
2014/10/03 13:15:16.192 033e4-1f50 Jom: Initializing: scm=FlightPlaceModelSchema, scmOid=[1280.8], scmNo=102, superScmOid=[1.1], superScmNo=1 , lvl=2
2014/10/03 13:15:16.192 033e4-1f50 Jom: Initializing: Jade is present
2014/10/03 13:15:16.192 033e4-1f50 Jom: Remote node create: oid=[186.1], node=0x000000000430A040, id=clientNameForNow, type=5, cacheCoherency=false
2014/10/03 13:15:16.192 033e4-1f50 Jom: Local node create: oid=[186.1], node=0x0000000003C02F10, id=BIGRED1, type=5
2014/10/03 13:15:16.192 033e4-1f50 Jom: Background process initialized: 0x00000000042B0CD0, oid=[187.1]
2014/10/03 13:15:16.973 033e4-22b0 Jom: Local process sign-on: oid=[187.2], process=0x0000000023286E90, no=2, id=1, db=8880, type=1, (non-prodn), scm=JadeSchema, app=Jade
2014/10/03 13:15:17.395 033e4-2348 PDB: DiskCacheSweepTime= 300, DiskCacheSweepInterval= 700
2014/10/03 13:15:17.395 033e4-2348 PDB: DiskCacheFreeMemoryTarget= 536870912, DiskCacheMemorySampleInterval= 5000
2014/10/03 13:15:17.598 033e4-22b0 Jade: Jade client startup: user=BIGRED path=C:\Jade70\system multiUser=false
2014/10/03 13:15:21.348 033e4-22b0 PDB: flightPlace.dat[53] opened, add: 139264 file bytes, active db size=212992 bytes
2014/10/03 13:17:04.652 033e4-22b0 NoteDD: NDD::notifyCallback: NotifyQueueDepth decrement threshold info: notifyQueueDepth=1 for process [187.2]
2014/10/03 13:17:28.558 033e4-3200 PDB: Bank.dat[51] opened, add: 139264 file bytes, active db size=352256 bytes
2014/10/03 13:17:28.590 033e4-3200 Jom: Local process sign-on: oid=[187.3], process=0x0000000024A774D0, no=3, id=2, db=12800, type=2, (non-prodn), scm=BankingModelSchema, app=BankingModelSchema
2014/10/03 13:17:28.637 033e4-3200 JomLog: Unhandled SystemException: Key already used in this dictionary, see BankingModelSchema.log for details
2014/10/03 13:18:46.095 033e4-3200 JomLog: >>> Process Dump requested <<<
2014/10/03 13:18:46.110 033e4-3200 JomLog: Linked to C:\Windows\SYSTEM32\dbghelp.dll version: 6.3.9600.16520
2014/10/03 13:18:46.126 033e4-3200 JomLog: >>> Dumping Process memory and O/S handles ....
2014/10/03 13:18:58.970 033e4-3200 JomLog: >>> Process Dump complete, dump file: C:\Jade70\ProcessDumps\jade_20141003_131846_33e4.dmp <<<
2014/10/03 13:18:59.095 033e4-3200 JomLog: unhandledException: pass exception to system ...
2014/10/03 13:23:40.891 02f60-209c BIGRED: (jade) Version 7.0.04 - ANSI, OS Version: , Wow64: false, Architecture: x64-msoft-win64-ansi
2014/10/03 13:23:40.953 02f60-209c BIGRED: Invocation: "C:\Jade70\bin\jade.exe" path=C:\Jade70\system ini=C:\Jade70\system\jade.ini app=Jade server = singleUser
2014/10/03 13:23:40.875 02f60-209c JomLog: Unable to encode eOpSys @ 649; WIN32_NT / Version 6.2, SP 0.0, ProdType 1/101
2014/10/03 13:23:41.703 02f60-209c RPCMgr2: TransportIdlePollInterval = 120000 ms
2014/10/03 13:23:41.750 02f60-209c PDB: Database initialising with jomdb version: 7.0.04.4, ini=C:/Jade70/system/jade.ini
2014/10/03 13:23:41.750 02f60-209c PDB: Structural: sizeof(Record)=76, sizeof(RecTag)=5, OFFSETOF(Record,hdr.oid)=37, HistoryStateSize=32, ObjectHdrSize=50, CollectionBlockHdrSize=70
2014/10/03 13:23:41.750 02f60-209c PDB: System file directory: C:/Jade70/bin/
2014/10/03 13:23:41.750 02f60-209c PDB: <<INFO>> IO resource error handling: retry delay = 500ms, retry limit = 2
2014/10/03 13:23:41.828 02f60-2f88 PDB: BOT <DiskCache Background Flush>
2014/10/03 13:23:41.828 02f60-2f88 PDB: Background flush params: flush interval=1000
2014/10/03 13:23:41.828 02f60-1b04 PDB: BOT <DiskCache Worker>
2014/10/03 13:23:41.828 02f60-2f88 PDB: Background flush: GatherWrite enabled; blocks per write=128 (1048576 bytes)
2014/10/03 13:23:41.828 02f60-209c PDB: BCB size=80
2014/10/03 13:23:41.828 02f60-2fc0 PDB: BOT <Diskcache Prefetch>
2014/10/03 13:23:41.828 02f60-209c PDB: DiskCache: physical bytes=4221722624 bytes, pool size=268435456 bytes (32768 blocks), block size=8192 bytes
2014/10/03 13:23:41.828 02f60-209c PDB: DiskCache: segment size=67108864 (8192 blocks), segments allocated=4 (min=4, max=47)
2014/10/03 13:23:41.828 02f60-209c PDB: DiskCache: max files=2102, IOCBs=50, hash lock regions=128, hash spread bits=14
2014/10/03 13:23:41.828 02f60-209c PDB: DiskCache: warming fetch blocks=4, prefetch blocks=8
2014/10/03 13:23:41.828 02f60-209c PDB: DiskCache: buffer cleanup on exit disabled (default)
2014/10/03 13:23:41.828 02f60-2348 PDB: BOT <Database Worker>
2014/10/03 13:23:41.828 02f60-1be8 PDB: BOT <Audit Worker>
2014/10/03 13:23:41.828 02f60-2f84 PDB: BOT <Journal Worker>
2014/10/03 13:23:41.828 02f60-209c PDB: Database restarted after system failure
2014/10/03 13:23:41.828 02f60-209c PDB: ************************************************************************************************
2014/10/03 13:23:41.828 02f60-209c PDB: <<WARNING>> Journal directory: C:/Jade70/system/journals/current/
2014/10/03 13:23:41.828 02f60-209c PDB: <<WARNING>> Journal directory is located on the same volume as your Database
2014/10/03 13:23:41.828 02f60-209c PDB: Database performance compromised; audit I/O will compete with database I/O
2014/10/03 13:23:41.828 02f60-209c PDB: A media or disk subsystem failure may result in loss of database transaction journals
2014/10/03 13:23:41.828 02f60-209c PDB: In which case Restore and Roll-Foward Recovery through current journals may not be possible
2014/10/03 13:23:41.828 02f60-209c PDB: Change Transaction Journal Volume to improve the availability and performance of your Database
2014/10/03 13:23:41.828 02f60-209c PDB: ************************************************************************************************
2014/10/03 13:23:41.844 02f60-209c PDB: Delta logging enabled
2014/10/03 13:23:41.844 02f60-209c PDB: Current and Archive Journal directories are located on same volume
2014/10/03 13:23:41.844 02f60-209c PDB: Database: {3aab5a68-2042-e411-9b75-8cdcd46f93df} opened for update in recovery mode, last update jomdb version: 7.0.04.4
2014/10/03 13:23:41.860 02f60-209c PDB: Database Restart Recovery...
2014/10/03 13:23:41.907 02f60-209c PDB: Commencing REDO phase - forward scan from (13,3401512) ...
2014/10/03 13:23:41.938 02f60-209c PDB: Processing journal C:/Jade70/system/journals/current/db0000000013.log
2014/10/03 13:23:41.938 02f60-209c PDB: journal physical end of file = 67108864
2014/10/03 13:23:42.250 02f60-209c PDB: journal actual end of file = 3486586
2014/10/03 13:23:42.250 02f60-209c PDB: Timestamp of last commit record: 03 October 2014, 13:17:28
2014/10/03 13:23:42.266 02f60-209c PDB: Timestamp of last journal record: 03 October 2014, 13:17:28
2014/10/03 13:23:42.375 02f60-209c PDB: No transactions to undo
2014/10/03 13:23:42.375 02f60-209c PDB: 510 journal records processed
2014/10/03 13:23:42.375 02f60-209c PDB: 0 uncommitted transactions backed out
2014/10/03 13:23:42.375 02f60-209c PDB: 12 committed transactions recovered
2014/10/03 13:23:42.375 02f60-209c PDB: 0 previously aborted transactions scanned
2014/10/03 13:23:42.735 02f60-1b04 PDB: DiskCacheSweepTime= 300, DiskCacheSweepInterval= 700
2014/10/03 13:23:42.735 02f60-1b04 PDB: DiskCacheFreeMemoryTarget= 536870912, DiskCacheMemorySampleInterval= 5000
2014/10/03 13:23:42.860 02f60-209c PDB: checkpoint flush elapsed time=3 ms
2014/10/03 13:23:42.922 02f60-209c PDB: checkpoint sync files elapsed time=73 ms
2014/10/03 13:23:42.985 02f60-209c PDB: <<Check Point>> LSN=(13,3486586), minRecoveryLSN=(13,3486586), farthestBackLSN=(13,3486586), elapsed time=197 ms, by: end recovery
2014/10/03 13:23:43.047 02f60-209c PDB: _environ[12] cfile state changed from assigned to deleted
2014/10/03 13:23:43.078 02f60-209c PDB: removed C:/Jade70/system/_environ.dat
2014/10/03 13:23:43.578 02f60-209c PDB: Database recovery complete - Elapsed Time = 00:00:01.672
2014/10/03 13:23:43.625 02f60-209c PDB: Update timestamp for _system.bin: 29 February 2012 16:08:50.053779
2014/10/03 13:23:43.860 02f60-209c PDB: <<LICENSE RESTRICTION>>: Total active database size restricted to 2GB
2014/10/03 13:23:43.860 02f60-209c PDB: Max DB users set to: 35
2014/10/03 13:23:43.891 02f60-209c TDB: Max DB users set to: 35
2014/10/03 13:23:44.250 02f60-22d4 PDB: <<LICENSE RESTRICTION>>: Total active database size restricted to 2GB
2014/10/03 13:23:44.360 02f60-22d4 PDB: _rootdef.dat[40] opened, add: 73728 file bytes, active db size=73728 bytes
2014/10/03 13:23:44.547 02f60-22d4 Jom: Initializing: scm=RootSchema, oid=[1.1], scmNo=1, lvl=1
2014/10/03 13:23:44.547 02f60-22d4 Jom: Initializing: scm=BankingModelSchema, scmOid=[1280.9], scmNo=100, superScmOid=[1.1], superScmNo=1 , lvl=2
2014/10/03 13:23:44.547 02f60-22d4 Jom: Initializing: scm=FlightPlaceModelSchema, scmOid=[1280.8], scmNo=102, superScmOid=[1.1], superScmNo=1 , lvl=2
2014/10/03 13:23:44.547 02f60-22d4 Jom: Initializing: Jade is present
2014/10/03 13:23:44.547 02f60-22d4 Jom: Remote node create: oid=[186.1], node=0x0000000004C4A040, id=clientNameForNow, type=5, cacheCoherency=false
2014/10/03 13:23:44.563 02f60-22d4 Jom: Local node create: oid=[186.1], node=0x0000000002AD2F10, id=BIGRED1, type=5
2014/10/03 13:23:44.563 02f60-22d4 Jom: Background process initialized: 0x0000000004BF0CD0, oid=[187.1]
2014/10/03 13:23:45.672 02f60-2420 Jom: Local process sign-on: oid=[187.2], process=0x00000000241C6E90, no=2, id=1, db=9248, type=1, (non-prodn), scm=JadeSchema, app=Jade
2014/10/03 13:23:45.750 02f60-2420 Jade: Jade client startup: user=BIGRED path=C:\Jade70\system multiUser=false
2014/10/03 13:24:21.501 02f60-2420 PDB: flightPlace.dat[53] opened, add: 139264 file bytes, active db size=212992 bytes
2014/10/03 13:25:11.814 02f60-2420 PDB: bankingviewschema[52] added to control file
2014/10/03 13:25:11.814 02f60-2420 PDB: File: bankingviewschema was allocated slot index = 52
2014/10/03 13:25:11.861 02f60-22d4 Jom: notifySchemaAdded: oid=[1280.10], no=101, lvl=3
2014/10/03 13:25:11.892 02f60-22d4 NoteDD: NDD::notifyCallback: NotifyQueueDepth decrement threshold info: notifyQueueDepth=6 for process [0.0]
2014/10/03 13:25:12.001 02f60-2420 PDB: bankingviewschema.dat[52] opened, add: 73728 file bytes, active db size=286720 bytes
2014/10/03 13:25:12.314 02f60-2420 NoteDD: NDD::notifyCallback: NotifyQueueDepth decrement threshold info: notifyQueueDepth=15 for process [187.2]
2014/10/03 13:26:14.019 02f60-2420 PDB: flightplaceviewschema[54] added to control file
2014/10/03 13:26:14.019 02f60-2420 PDB: File: flightplaceviewschema was allocated slot index = 54
2014/10/03 13:26:14.034 02f60-22d4 Jom: notifySchemaAdded: oid=[1280.11], no=103, lvl=3
2014/10/03 13:26:14.113 02f60-2420 PDB: flightplaceviewschema.dat[54] opened, add: 73728 file bytes, active db size=425984 bytes
2014/10/03 13:27:16.161 02f60-209c Jom: Local process sign-on: oid=[187.3], process=0x00000000291D09C0, no=3, id=2, db=8348, type=4, (non-prodn), scm=JadeSchema, app=JadePainter
2014/10/03 14:37:34.525 02f60-209c NoteDD: NDD::notifyCallback: NotifyQueueDepth decrement threshold info: notifyQueueDepth=2 for process [187.3]

Thanks in advance

User avatar
BeeJay
Posts: 311
Joined: Tue Jun 30, 2009 2:42 pm
Location: Christchurch, NZ

Re: Jade runtime has stopped working

Postby BeeJay » Fri Oct 03, 2014 2:27 pm

Jade 7.0.04 is quite an old version of Jade 7. You may want to consider upgrading to the latest 7.0.09 release to see if that alleviates the issues you're encountering.

Out of interest, what Windows OS are you running on the machine where this regular crashing is occurring?

Cheers,
BeeJay.

sit
Posts: 13
Joined: Mon Sep 29, 2014 6:53 pm

Re: Jade runtime has stopped working

Postby sit » Fri Oct 03, 2014 2:33 pm

I'm running windows 8.1.

User avatar
BeeJay
Posts: 311
Joined: Tue Jun 30, 2009 2:42 pm
Location: Christchurch, NZ

Re: Jade runtime has stopped working

Postby BeeJay » Fri Oct 03, 2014 2:39 pm

In that case I would definitely try upgrading to Jade 7.0.09 to see if that corrects your crashing problem as the first release of Jade 'officially qualified' to run on Windows 8.1 is Jade 7.0.09, according to the following page on the Jade Website:

http://jade.co.nz/jade/op_reqs7.htm

Cheers,
BeeJay.

sit
Posts: 13
Joined: Mon Sep 29, 2014 6:53 pm

Re: Jade runtime has stopped working

Postby sit » Fri Oct 03, 2014 2:47 pm

We all (students )got the same version from our teacher at tech so I didn't get to choose which one would have been most appropriate for my system.

Thanks

Toni

User avatar
BeeJay
Posts: 311
Joined: Tue Jun 30, 2009 2:42 pm
Location: Christchurch, NZ

Re: Jade runtime has stopped working

Postby BeeJay » Fri Oct 03, 2014 2:57 pm

In that case you may want to follow up with your teacher at SIT to confirm they're not going to have any issues with you using a later release of Jade 7 for your project work, assuming the later version does indeed correct the crashing issue you're encountering.

Cheers,
BeeJay.


Return to “Tips and Techniques”

Who is online

Users browsing this forum: No registered users and 1 guest

cron