Welcome, Guest
Username: Password: Remember me

TOPIC: App Crash zooming in on jpg background

App Crash zooming in on jpg background 11 years 2 months ago #5620

  • longjohn119
  • longjohn119's Avatar
  • Offline
I'm getting a .NET Presentation Core out of memory error whenever I try to zoom in a a jpg. background image that's only 10mb (5000 x 3000 1 meter per pixel) on a Lenovo Thinkpad Tablet 2 w/ 2 Gb RAM When I monitor the memory worst case is 60% and usually closer to 50% when it crashes.

I don't have any problem running much larger maps in OziExplorer, OK Map, Dr Depth or even several 40 Mb Tiff layers at once in Qgis. I even run OziExplorer on the internal GPS and Dr Depth with an external GPS at the same time, no problems. In fact I've had this nearly a year and it's the first memory error I've ever had. I looked up the error and pretty much everything was about people having problems with their own coding and not users with program problems so I suspect a bug of sorts. Perhaps in the shared memory implementation not allocating enough memory for video

I'd like to get away from Dr Depth for obvious reasons but if I can't run it on my main field unit for data collection it really limits me to just using logs

Here's the Windows Error Report:

Version=1
EventType=CLR20r3
EventTime=130799485560109310
ReportType=2
Consent=1
ReportIdentifier=a726013b-1d63-11e5-977a-54ee7521f329
IntegratorReportIdentifier=a726013a-1d63-11e5-977a-54ee7521f329
NsAppName=ReefMaster.exe
Response.type=4
Sig[0].Name=Problem Signature 01
Sig[0].Value=ReefMaster.exe
Sig[1].Name=Problem Signature 02
Sig[1].Value=1.8.32.0
Sig[2].Name=Problem Signature 03
Sig[2].Value=55675968
Sig[3].Name=Problem Signature 04
Sig[3].Value=PresentationCore
Sig[4].Name=Problem Signature 05
Sig[4].Value=4.0.30319.34209
Sig[5].Name=Problem Signature 06
Sig[5].Value=5348b56b
Sig[6].Name=Problem Signature 07
Sig[6].Value=283
Sig[7].Name=Problem Signature 08
Sig[7].Value=13
Sig[8].Name=Problem Signature 09
Sig[8].Value=System.OutOfMemoryException
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.3.9600.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=545c
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=545c8b528f6299aa421a698934afbfa2
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=26b8
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=26b839f766442c7108949a4d014ecd2a
UI[2]=C:\Program Files\ReefMaster Software\ReefMaster\ReefMaster.exe
UI[3]=ReefMaster has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files\ReefMaster Software\ReefMaster\ReefMaster.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\SYSTEM32\MSCOREE.DLL
LoadedModule[3]=C:\Windows\system32\KERNEL32.dll
LoadedModule[4]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[5]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[6]=C:\Windows\system32\msvcrt.dll
LoadedModule[7]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[8]=C:\Windows\system32\RPCRT4.dll
LoadedModule[9]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
LoadedModule[10]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[11]=C:\Windows\SYSTEM32\combase.dll
LoadedModule[12]=C:\Windows\system32\USER32.dll
LoadedModule[13]=C:\Windows\system32\GDI32.dll
LoadedModule[14]=C:\Windows\system32\IMM32.DLL
LoadedModule[15]=C:\Windows\system32\MSCTF.dll
LoadedModule[16]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
LoadedModule[17]=C:\Windows\SYSTEM32\MSVCR120_CLR0400.dll
LoadedModule[18]=C:\Windows\assembly\NativeImages_v4.0.30319_32\mscorlib\d1265d6159ea876f9d63ea4c1361b587\mscorlib.ni.dll
LoadedModule[19]=C:\Windows\system32\ole32.dll
LoadedModule[20]=C:\Windows\SYSTEM32\kernel.appcore.dll
LoadedModule[21]=C:\Windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[22]=C:\Windows\SYSTEM32\bcryptPrimitives.dll
LoadedModule[23]=C:\Windows\system32\uxtheme.dll
LoadedModule[24]=C:\Program Files\Common Files\microsoft shared\ink\tiptsf.dll
LoadedModule[25]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[26]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
LoadedModule[27]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System\487c38839683ae7c3d773386adc02b18\System.ni.dll
LoadedModule[28]=C:\Windows\assembly\NativeImages_v4.0.30319_32\WindowsBase\b18c22eb10f119686040ab1354ff27fa\WindowsBase.ni.dll
LoadedModule[29]=C:\Windows\SYSTEM32\CRYPTSP.dll
LoadedModule[30]=C:\Windows\system32\rsaenh.dll
LoadedModule[31]=C:\Windows\SYSTEM32\bcrypt.dll
LoadedModule[32]=C:\Windows\assembly\NativeImages_v4.0.30319_32\PresentationCore\0a81cae6f5ddd1b8df1298d48a6151cb\PresentationCore.ni.dll
LoadedModule[33]=C:\Windows\assembly\NativeImages_v4.0.30319_32\Presentatio5ae0f00f#\5f400d325e34e0bc03219990ce87e264\PresentationFramework.ni.dll
LoadedModule[34]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Xaml\9d7192b328a08155b6cbb2f3ec728407\System.Xaml.ni.dll
LoadedModule[35]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Core\ccb5b082512497c88f8e84017a66a2d5\System.Core.ni.dll
LoadedModule[36]=C:\Windows\SYSTEM32\dwrite.dll
LoadedModule[37]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\wpfgfx_v0400.dll
LoadedModule[38]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\PresentationNative_v0400.dll
LoadedModule[39]=C:\Windows\system32\dwmapi.dll
LoadedModule[40]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Configuration\bd583bdbb9ef33ee379f1ab9907eda7c\System.Configuration.ni.dll
LoadedModule[41]=C:\Windows\SYSTEM32\VERSION.dll
LoadedModule[42]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Xml\e7dd54337058ee9fc1918ad615cdb185\System.Xml.ni.dll
LoadedModule[43]=C:\Windows\SYSTEM32\urlmon.dll
LoadedModule[44]=C:\Windows\SYSTEM32\iertutil.dll
LoadedModule[45]=C:\Windows\SYSTEM32\WININET.dll
LoadedModule[46]=C:\Windows\SYSTEM32\USERENV.dll
LoadedModule[47]=C:\Windows\SYSTEM32\profapi.dll
LoadedModule[48]=C:\Windows\SYSTEM32\Secur32.dll
LoadedModule[49]=C:\Windows\SYSTEM32\SSPICLI.DLL
LoadedModule[50]=C:\Windows\system32\SHELL32.dll
LoadedModule[51]=C:\Windows\system32\SHCORE.dll
LoadedModule[52]=C:\Windows\system32\WINTRUST.dll
LoadedModule[53]=C:\Windows\system32\CRYPT32.dll
LoadedModule[54]=C:\Windows\system32\MSASN1.dll
LoadedModule[55]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscorsecimpl.dll
LoadedModule[56]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.9600.17810_none_7c5b6194aa0716f1\COMCTL32.dll
LoadedModule[57]=C:\Windows\system32\imagehlp.dll
LoadedModule[58]=C:\Windows\SYSTEM32\ncrypt.dll
LoadedModule[59]=C:\Windows\SYSTEM32\NTASN1.dll
LoadedModule[60]=C:\Windows\SYSTEM32\gpapi.dll
LoadedModule[61]=C:\Windows\System32\cryptnet.dll
LoadedModule[62]=C:\Windows\system32\WLDAP32.dll
LoadedModule[63]=C:\Windows\SYSTEM32\IPHLPAPI.DLL
LoadedModule[64]=C:\Windows\system32\NSI.dll
LoadedModule[65]=C:\Windows\SYSTEM32\WINNSI.DLL
LoadedModule[66]=C:\Program Files\ReefMaster Software\ReefMaster\sqlite.interop.dll
LoadedModule[67]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Drawing\2fd03fa85d6a91f0ee14d21571369a26\System.Drawing.ni.dll
LoadedModule[68]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\b4f1dda828494fc76aa1ba8c9d4c5645\System.Windows.Forms.ni.dll
LoadedModule[69]=C:\Windows\SYSTEM32\WindowsCodecs.dll
LoadedModule[70]=C:\Windows\SYSTEM32\d3d9.dll
LoadedModule[71]=C:\Windows\SYSTEM32\igdumd32.dll
LoadedModule[72]=C:\Windows\system32\SETUPAPI.dll
LoadedModule[73]=C:\Windows\system32\CFGMGR32.dll
LoadedModule[74]=C:\Windows\assembly\NativeImages_v4.0.30319_32\Presentatioaec034ca#\28b11cad8855404dab40ab22e154c76d\PresentationFramework.Aero2.ni.dll
LoadedModule[75]=C:\Windows\SYSTEM32\mscms.dll
LoadedModule[76]=C:\Windows\SYSTEM32\WindowsCodecsExt.dll
LoadedModule[77]=C:\Program Files\ReefMaster Software\ReefMaster\TurboActivate.dll
LoadedModule[78]=C:\Windows\SYSTEM32\WINHTTP.dll
LoadedModule[79]=C:\Windows\system32\WS2_32.dll
LoadedModule[80]=C:\Windows\SYSTEM32\powrprof.dll
LoadedModule[81]=C:\Windows\SYSTEM32\WtsApi32.dll
LoadedModule[82]=C:\Windows\SYSTEM32\WINSTA.dll
LoadedModule[83]=C:\Windows\SYSTEM32\clbcatq.dll
LoadedModule[84]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\PenIMC.dll
LoadedModule[85]=C:\Windows\System32\wisp.dll
LoadedModule[86]=C:\Windows\SYSTEM32\atlthunk.dll
LoadedModule[87]=C:\Program Files\Common Files\Microsoft Shared\Ink\tpcps.dll
LoadedModule[88]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17810_none_a9edf09f013934e0\comctl32.dll
LoadedModule[89]=C:\Windows\SYSTEM32\oleacc.dll
LoadedModule[90]=C:\Windows\assembly\NativeImages_v4.0.30319_32\UIAutomationProvider\3461e03fa48e1c503b31ae6485d643e9\UIAutomationProvider.ni.dll
LoadedModule[91]=C:\Windows\assembly\NativeImages_v4.0.30319_32\UIAutomationTypes\4ecc9a930ce584ca105857e68bad3c5f\UIAutomationTypes.ni.dll
LoadedModule[92]=C:\Windows\SYSTEM32\UIAutomationCore.dll
LoadedModule[93]=C:\Windows\SYSTEM32\sxs.dll
LoadedModule[94]=C:\Windows\system32\msctfui.dll
LoadedModule[95]=C:\Windows\SYSTEM32\avrt.dll
LoadedModule[96]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Data\fd6e915b319eae7b3b1d659b12c7d171\System.Data.ni.dll
LoadedModule[97]=C:\Windows\Microsoft.Net\assembly\GAC_32\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll
LoadedModule[98]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Transactions\66de5b124d5ce067974da90443f99ba9\System.Transactions.ni.dll
LoadedModule[99]=C:\Windows\Microsoft.Net\assembly\GAC_32\System.Transactions\v4.0_4.0.0.0__b77a5c561934e089\System.Transactions.dll
LoadedModule[100]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Runt19c51595#\9e09b718a50c037bf8b869e0f53cabea\System.Runtime.Caching.ni.dll
LoadedModule[101]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrcompression.dll
LoadedModule[102]=C:\Windows\SYSTEM32\WINMM.dll
LoadedModule[103]=C:\Windows\SYSTEM32\WINMMBASE.dll
LoadedModule[104]=C:\Windows\SYSTEM32\DEVOBJ.dll
LoadedModule[105]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Ente96d83b35#\1b11bdb0ae6fb95bc56e3589b9ae7177\System.EnterpriseServices.ni.dll
LoadedModule[106]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Ente96d83b35#\1b11bdb0ae6fb95bc56e3589b9ae7177\System.EnterpriseServices.Wrapper.dll
LoadedModule[107]=C:\Windows\Microsoft.Net\assembly\GAC_32\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.Wrapper.dll
LoadedModule[108]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Numerics\de2a832558f95db343e443c365bd3575\System.Numerics.ni.dll
LoadedModule[109]=C:\Windows\SYSTEM32\ntmarta.dll
LoadedModule[110]=C:\Windows\assembly\NativeImages_v4.0.30319_32\Accessibility\f3c7721d3e73cf70c1cf85707a152c4e\Accessibility.ni.dll
LoadedModule[111]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\diasymreader.dll
FriendlyEventName=Stopped working
ConsentKey=CLR20r3
AppName=ReefMaster
AppPath=C:\Program Files\ReefMaster Software\ReefMaster\ReefMaster.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=B812163C51A45973E5BFC6DE33A10473
The administrator has disabled public write access.

App Crash zooming in on jpg background 11 years 2 months ago #5623

  • Matt
  • Matt's Avatar
  • Offline
Sounds like you are loading the JPG into ReefMaster and calibrating it there?
In this case, the entire image file is loaded when it is used, and memory usage can be surprisingly high. This is because the image cannot be compressed when it is stored in memory, so a 5000 x 3000 pixel image is actually over 60MBin size (5k x 3k x 4 bytes per pixel).

If you import an image with a KML calibration file instead, then RM will split the image into tiles and create an mbtiles file. This works in much the same way as Google Maps, with a large number of small image tiles stored in varying resolutions. This means that RM only needs to load the tiles that are required to visible portion of the image, and a lower resolution version can be used as required.

I recommend opening Google Earth, loading your JPG file in there and calibrating it. Then save this "ground overlay" as a kml file. Remove your existing image from RM and import the ground overlay instead by selecting the kml file during image import (make sure the associated image file is available in the same directory as the kml file). RM will perform the tiling operation and produce an .mbtiles file in the workspace directory which can then be used in other workspaces without having to go through the tiling process again.
The administrator has disabled public write access.

App Crash zooming in on jpg background 11 years 2 months ago #5629

  • longjohn119
  • longjohn119's Avatar
  • Offline
OK I'll give that a try and see what happens although it still bugs me I can use images 4 times larger or more in all my other mapping programs with 2 or more programs going at the same time and never experienced a crash and some of them have been used since 2010 on a much less powerful 1st gen Atom netbook I turned into a tablet. (Currently a server/access point for my weather station, AIS reciever, and Internet of Things devices I'm making) Also it means the background maps I made for Dr Depth going back to 2008 will all have to be redone before I can bring all that data in and convert it (That's a winter project

If anyone is curious these maps and map layers are available on my GitHub site and detailed with links on my blog and my gear and setup much of it 'homebrew' is detailed on my main blog. Including a NMEA GPS/Depth finder multiplexer and NMEA logger that logs depth and position from the time I hit the water until I pull out whether or not a computer is attached

The Lost Grove Lake Mapping Project

The Netbook2Chartplotter Project
The administrator has disabled public write access.

App Crash zooming in on jpg background 11 years 2 months ago #5630

  • Matt
  • Matt's Avatar
  • Offline
Did you have the same image showing in a lot of tabs? Something like DD would only ever have a single active window, whereas it is possible in RM to have any number of tabs open, and the image would be loaded for each of them. I admit I find it surprising that it crashed with your system specs - the image isn't that large - but issues with large image handling are why tiling exists, and you won't have any memory problems (from images, at least) if you go down that route.
The administrator has disabled public write access.
SCROLL TO TOP