Welcome to MapForums!

Register, sign in, or use Facebook Connect above to join in and participate in the forum.

When you are signed in, this message, the ads in this row, and the red-underlined link ads all go away.

Subscribe to receive our newsletter.
Subscribe Unsubscribe
Page 2 of 2 FirstFirst 12
Results 11 to 14 of 14

MapPoint.exe remains in process pool on crash of application in .net

This is a discussion on MapPoint.exe remains in process pool on crash of application in .net within the Development forums, part of the MapPoint Desktop Discussion category; hi, Originally Posted by malik.rizwan But if i have multiple instance of my application running (they would have seperate MapPoint ...

  1. #11
    Auge_Ohr's Avatar
    Auge_Ohr is offline Member Green Belt
    Join Date
    Sep 2008
    Location
    Hamburg, Germany
    Posts
    65

    Re: MapPoint.exe remains in process pool on crash of application in .net

    hi,
    Quote Originally Posted by malik.rizwan View Post
    But if i have multiple instance of my application running (they would have seperate MapPoint server running), how would i know which mappoint.exe instance relates to what instance of my application. Its possible that closing process by code could close the mappoint instance that is already in use and functional.
    ok it was just a Idee

    Quote Originally Posted by malik.rizwan View Post
    Yes, there's little you can do if the user does a kill
    i think there is a DLLcall to disable "Crtl-ALT-DEL" ...

  2. #12
    bluefireball is offline Junior Member Yellow Belt
    Join Date
    Mar 2007
    Posts
    27

    Re: MapPoint.exe remains in process pool on crash of application in .net

    Crash-free code is ideal but we all know that MapPoint ActiveX is not stable. I have tried many ways to aovid mappoint crashing, but so far one problem still drives me nuts. Sometimes MapPoint ActiveX crashes with an internal error (6-40028-1073741819), no recovery. Note that it's MapPoint ActiveX crashes, not my C# program. It happens randomly on some mahcines, no consistent behavious.

    Still there are some ways to avoid common problems when you coding C#, the following is from my own experience,

    1. always using try/catch whenever you call the object APIs. Some simple action may cause crashing, for example, your code trying to access the object while the find address window (modal) is open.

    2. try not to invoke anything related to dataset too fast. If you have to, try to use Thread.Sleep to slow you API calls and let the ActiveX have enough time to the current call.

    3. disable uncessary features as much as possible, such as the right mouse click etc.

    Hope this helps. Also, if anybody knows anything regarding the internal error mentioned above, let us know please.

    -bluefireball

  3. #13
    malik.rizwan is offline VisionXpo Softwares White Belt
    Join Date
    Sep 2008
    Location
    Sweden
    Posts
    7

    Re: MapPoint.exe remains in process pool on crash of application in .net

    Quote Originally Posted by Auge_Ohr View Post
    hi,

    ok it was just a Idee


    i think there is a DLLcall to disable "Crtl-ALT-DEL" ...
    I dont think Disabling Ctrl+ALT+DEL is a good thing for this problem. There could be multiple diff applications running at same time. User might want to kill some other process, or may be wants to view Performance graph or anything. Just to make your exe safe you are disallowing user to view many things
    VisionXpo Software Solutions, Stockholm
    http://www.visionxpo.net

  4. #14
    Auge_Ohr's Avatar
    Auge_Ohr is offline Member Green Belt
    Join Date
    Sep 2008
    Location
    Hamburg, Germany
    Posts
    65

    Re: MapPoint.exe remains in process pool on crash of application in .net

    hi,
    Quote Originally Posted by malik.rizwan View Post
    I dont think Disabling Ctrl+ALT+DEL is a good thing for this problem. There could be multiple diff applications running at same time. User might want to kill some other process, or may be wants to view Performance graph or anything. Just to make your exe safe you are disallowing user to view many things
    YES in general i agree ... but is there any Error-free USER ?

    most Error i got are made by User so i try to avoid possible User Action like
    disable Ctrl+ALT+DEL or ALT-TAB when e.g. MP do Calculate() in a Thread.

    there IS a "Emergency" Pushbutton on that Form to brake it "with control",
    not as a DAU woud do it "without Control".
    I also do maximize() Form and have disable minimize/normalize/close Button
    and use AllWaysOnTop() to make that Form like a modal Form, so User can
    not do "unwanted Action".

    So i think it does not help much using a Errorblock for Programmcode, when
    User "is the Error" ...

Page 2 of 2 FirstFirst 12

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. MapPoint Crash with Garmin 18Pc
    By stevet in forum MapPoint Desktop Discussion
    Replies: 3
    Last Post: 11-25-2007, 03:39 AM
  2. Finding MapPoint process
    By Marin in forum MapPoint Desktop Discussion
    Replies: 7
    Last Post: 05-04-2007, 11:04 AM
  3. MapPoint + VS 2005 + C# + 64 bit OS = Crash!
    By dkrafcheck in forum MapPoint Desktop Discussion
    Replies: 0
    Last Post: 02-03-2007, 07:20 PM
  4. MapPoint 2006 Windows Crash With GPS On
    By domino in forum MapPoint Desktop Discussion
    Replies: 4
    Last Post: 07-16-2006, 03:40 PM
  5. Mappoint 2004 crash on 'Find'
    By Anonymous in forum MapPoint Desktop Discussion
    Replies: 6
    Last Post: 11-19-2004, 03:49 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127