# Segment violation in native code for SQLite - possible fixes

**URL:** <https://forum.inductiveautomation.com/t/segment-violation-in-native-code-for-sqlite-possible-fixes/11471>\
**Category:** Ignition\
**Created:** [April 5, 2016, 8:37pm UTC](https://forum.inductiveautomation.com/t/segment-violation-in-native-code-for-sqlite-possible-fixes/11471 "2016-04-05T20:37:59Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![driverk](https://avatars.discourse-cdn.com/v4/letter/d/aca169/32.png) [@driverk](https://forum.inductiveautomation.com/u/driverk)\
**Post date:** [April 5, 2016, 8:37pm UTC](https://forum.inductiveautomation.com/t/segment-violation-in-native-code-for-sqlite-possible-fixes/11471/1 "2016-04-05T20:37:59Z")

</div>

Lots of SIGSEGV fixes in later Java versions, just not clear if any of them would address this issue.

Ignition version = 7.8.2  
JDK = 1.8.0\_31  
OS = Red Hat Linux 6.7

This is on our test system; would like to make sure this doesn’t appear in our production environment.

=====

[code]

# A fatal error has been detected by the Java Runtime Environment:

# 

# SIGSEGV (0xb) at pc=0x00007fdae5ca2d00, pid=31164, tid=140578120029952

# 

# JRE version: Java™ SE Runtime Environment (8.0\_31-b13) (build 1.8.0\_31-b13)

# Java VM: Java HotSpot™ 64-Bit Server VM (25.31-b07 mixed mode linux-amd64 compressed oops)

# Problematic frame:

# C 0x00007fdae5ca2d00

[…]  
Stack: [0x00007fdae4d85000,0x00007fdae4e86000], sp=0x00007fdae4e83208, free space=1016k  
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)  
C 0x00007fdae5ca2d00  
J 19422 C1 org.sqlite.core.CoreConnection.open(II)V (417 bytes) @ 0x00007fdb2fdc8edc [0x00007fdb2fdc3020+0x5ebc]  
J 5877 C1 org.sqlite.core.CoreConnection.(Ljava/lang/String;Ljava/lang/String;Ljava/util/Properties;)V (195 bytes) @ 0x00007fdb2e033e54 [0x00007fdb2e033920+0x534]  
J 8386 C1 org.sqlite.SQLiteDataSource.getConnection(Ljava/lang/String;Ljava/lang/String;)Ljava/sql/Connection; (41 bytes) @ 0x00007fdb2e664304 [0x00007fdb2e6636e0+0xc24]  
J 5895 C1 org.sqlite.SQLiteDataSource.getConnection()Ljava/sql/Connection; (7 bytes) @ 0x00007fdb2dcb48a4 [0x00007fdb2dcb4800+0xa4]  
J 5514 C1 com.inductiveautomation.ignition.gateway.localdb.sqlite.SingleConnectionDatasource.getConnection()Ljava/sql/Connection; (127 bytes) @ 0x00007fdb2d15d88c [0x00007fdb2d15d740+0x14c][/code]  
[…]

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [April 5, 2016, 8:42pm UTC](https://forum.inductiveautomation.com/t/segment-violation-in-native-code-for-sqlite-possible-fixes/11471/2 "2016-04-05T20:42:41Z")

</div>

Are you seeing this during shutdown or at other times?

(we’ve observed this, but only during shutdown so far…)

---

<div class="post-metadata">

**Author:** ![driverk](https://avatars.discourse-cdn.com/v4/letter/d/aca169/32.png) [@driverk](https://forum.inductiveautomation.com/u/driverk)\
**Post date:** [April 5, 2016, 8:56pm UTC](https://forum.inductiveautomation.com/t/segment-violation-in-native-code-for-sqlite-possible-fixes/11471/3 "2016-04-05T20:56:30Z")

</div>

This is on a redundant system, and the master gateway had failed over to the backup. Part of the stack trace shows that this was during the startup process of the master.

I can supply the hs\_err file in a ticket if that would help. I have truncated the contents here for brevity.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [April 5, 2016, 9:02pm UTC](https://forum.inductiveautomation.com/t/segment-violation-in-native-code-for-sqlite-possible-fixes/11471/4 "2016-04-05T21:02:32Z")

</div>

Sure, and if you have the wrapper.log file(s), send those too. Just send them to the support email address.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [April 5, 2016, 10:06pm UTC](https://forum.inductiveautomation.com/t/segment-violation-in-native-code-for-sqlite-possible-fixes/11471/5 "2016-04-05T22:06:50Z")

</div>

Well for what it’s worth this one _did_ happen while your gateway was shutting down, which is the only time we’ve seen it so far.

We’ll continue to look into it.