Quantcast
Channel: LabVIEW topics
Viewing all articles
Browse latest Browse all 69523

labview打包的exe总是随机崩溃

$
0
0
现在用labview生成应用程序后,运行的时候总是会出现崩溃现象,而且出现崩溃现象的时间每次不固定,有的时候是在我开发软件的账户登录的时候,有时候是在数据采集过程中(串口通讯采集)、有时候是在采集结束显示测量指标的时候、有时候是在数据查询的时候,反正就是任何时刻都可能出现崩溃。
       还有,这个问题是经常性出现的。起初认为是labview版本的问题,但是我换了好几个版本还是一样。目前用的labview2016
       需要说明的是,不会存在计算导致的内存溢出现象、也不存在数据库操作不当的问题,这些我已排除。
       另外,我们还考虑了,可能是背景图片渲染问题,所以我把程序中所有涉及到背景图片的地方都去除了,打包后运行还是会崩溃。
       现将崩溃时候的log日志发送给您,希望能得到有效的解决方案。请尽快回复。
 
附件没法上传,只能贴在这里,这是崩溃后lvlog文件的内容:


####
#Date: 2020年3月21日 周六 下午 1:09:10
#OSName: Windows 7 Ultimate Service Pack 1
#OSVers: 6.1
#OSBuild: 7601
#AppName: Stress
#Version: 16.0 32-bit
#AppKind: AppLib
#AppModDate: 3/21/2020 04:09 GMT
#LabVIEW Base Address: 0x30000000


InitExecSystem() call to GetCurrProcessNumProcessors() reports: 2 processors
InitExecSystem() call to GetNumProcessors() reports: 2 processors
InitExecSystem() will use: 2 processors
starting LabVIEW Execution System 2 Thread 0 , capacity: 24 at [3667612153.31128030, (13:09:13.311280251 2020:03:21)]
starting LabVIEW Execution System 2 Thread 1 , capacity: 24 at [3667612153.31128030, (13:09:13.311280251 2020:03:21)]
starting LabVIEW Execution System 2 Thread 2 , capacity: 24 at [3667612153.31128030, (13:09:13.311280251 2020:03:21)]
starting LabVIEW Execution System 2 Thread 3 , capacity: 24 at [3667612153.31128030, (13:09:13.311280251 2020:03:21)]
Thread consumption suspected: 4 Try starting 4 threads
starting LabVIEW Execution System 2 Thread 4 , capacity: 24 at [3667612359.83809280, (13:12:39.838092804 2020:03:21)]
starting LabVIEW Execution System 2 Thread 5 , capacity: 24 at [3667612359.83809280, (13:12:39.838092804 2020:03:21)]
starting LabVIEW Execution System 2 Thread 6 , capacity: 24 at [3667612359.83809280, (13:12:39.838092804 2020:03:21)]
starting LabVIEW Execution System 2 Thread 7 , capacity: 24 at [3667612359.83809280, (13:12:39.838092804 2020:03:21)]

 

<DEBUG_OUTPUT>
2020/3/21 星期六 下午 1:14:23.341
Crash 0x00000000: Crash caught by NIER
File Unknown(0) : Crash 0x00000000: Crash caught by NIER
minidump id: 60cfb174-7f58-4266-af89-ffa25903e806
ExceptionCode: 0x3

</DEBUG_OUTPUT>
0x100011AF - nierInterface <unknown> + 0
0x10005F5A - nierInterface <unknown> + 0
0x10006608 - nierInterface <unknown> + 0
0x10001101 - nierInterface <unknown> + 0
0x100021D9 - nierInterface <unknown> + 0
0x3007DB85 - lvrt <unknown> + 0
0x30846CD1 - lvrt <unknown> + 0
0x30859C6D - lvrt <unknown> + 0
0x7566C4B7 - USER32 <unknown> + 0
0x7566C5B7 - USER32 <unknown> + 0
0x7566CBE9 - USER32 <unknown> + 0
0x75662E11 - USER32 <unknown> + 0
0x308B244B - lvrt <unknown> + 0
0x308B25C3 - lvrt <unknown> + 0
0x308B26BF - lvrt <unknown> + 0
0x3086AB46 - lvrt <unknown> + 0
0x30029F69 - lvrt <unknown> + 0
0x3002A1F3 - lvrt <unknown> + 0
0x00401142 - Stress <unknown> + 0
0xFFFD57E9 - <unknown> <unknown> + 0


Viewing all articles
Browse latest Browse all 69523

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>