Max crash Java: AWT-AppKit

    Apr 12 2010 | 12:35 pm
    Hello all,
    I am experiencing a very frustrating error. For my graduation project I have to place 4 prototypes in the participants homes. This prototype consists of a mac mini with a touchscreen attached, running Max Runtime. Somehow, on all machines Max Runtime quits unexpectedly after a random time, usually about once a day. Could anyone please give me a clue of what's going wrong?
    Kind regards, Bas
    ps. Pasting the log file in here resulted in an empty topic, so I added it separately. Could the earlier two posts be removed?

    • Apr 13 2010 | 8:22 pm
      And now it suddenly gets the same error when I try to open the main patch with Max. However, with Max Runtime it does work...
    • Apr 14 2010 | 6:31 am
      It's hard to say without knowing more details.
      Is there Java UI involved in your project ? Are there loadbang methods in your mxj objects ? or complex initialisation processes in your mxj object constructors ? I'll try to put that in a separate method and call it after a delayed loadbang.
      Also, from the report I see that you're on snow leopard & max 5.1.1 I'll first try to upgrade max (I think max 5.1.3 solves several 10.6 bugs) and do all os updates
      Make sure you installed "Java for Mac OS X 10.6 Update 1" It should appear in your automatic update.
      Hope this helps.
    • Apr 14 2010 | 10:33 am
      Hello Léo,
      Thank you for your reply. I will perform the updates first. I am not using mxj objects (anymore). I used to have a mxj object for up- and downloading textfiles to a FTP-server, but assumed this caused the problems, so I am now using 'jit.uldl' for this. Apart from that, 'aka.datetime' is used in my patch, does this contain mxj objects?
      I do use a lot of loadbangs, some of them delayed.
      I turned off automatic update, because this screen should not appear while the prototypes were in the field. However, forgot to turn it on again.
      Last night when it suddenly crashed on startup, I found the patch that caused this. In this patch I dynamically create and delete 'pictctrl' objects, using: 'sprintf script newobject pictctrl @name Bullets-69.png @varname Bullet[%i] @patching_rect %i %i 10 10 @range 3 @frames 3 @mode 2'. When there were already some of these objects at startup it crashed When I removed them and saved the patch, it was working again.
      Kind regards, Bas
    • Apr 14 2010 | 11:58 am
      I forgot to mention I am using a Javascript called sendto.js, see attachment. Could this cause the problems?
      Kind regards, Bas
    • Apr 14 2010 | 4:51 pm
      If there's no mxj object in your code, I don't see why Java could crash Max, but your crash log seems to say so. Haven't you forgot one mxj object somewhere ? Are you using FTM ?
      You can try to list externals used in your patch (file menu) or do a search in your patch.
    • Apr 15 2010 | 9:38 am
      I am not at home right now, but will try to list externals a.s.a.p.
      So only mxj objects could cause the problem? The sendto.js file I sent definetely not?
      I will try to eliminate the aka.datetime object as well.
    • Apr 15 2010 | 1:04 pm
      scripting is always a probable source for crashes too.
      bug your crash log describes a java problem (java & javascript are two different things) unless there's some java going on under max that I don't know about, java only comes from mxj or mxj~ objects.
    • Apr 15 2010 | 2:12 pm
      Hello Leo,
      I updated OSX, Max and Java, but still all systems crashed. Attached is the list of externals, nothing Java right?
    • Apr 15 2010 | 2:55 pm
      Try removing aka.datetime
      other sensitive objects in your patch might be js & jit.uldl
    • Apr 16 2010 | 10:50 pm
      I replaced all of these sensitive objects on three individual sysytems. The one with sendto.js removed is still running (over 24h). Let's hope it still runs tomorrow morning.
    • Apr 17 2010 | 3:47 pm
      It crashed this afternoon, but in the crash log js or java is not mentioned anymore. It is now mentioning 'objc_msgSend() selector name: objectForKey:' and 'objc_msgSend + 27'.
      On comparable errors with Safari ( running in 32-bit mode is suggested. Is this possible in my case?
    • Apr 18 2010 | 1:04 pm
      Hello bas,
      I don't think max is able to run in 64bit - but I might be wrong - so your problem might be something different. Without more details it hard to tell. What does your patch ? What system is it running on ? Does it crashes alone ? or when someone interacts with it ? how ? Can you post the crashlog ?
    • Apr 19 2010 | 8:54 am
      Hello Leo,
      I am not at home right now, so I can't send the crashlog yet. My patch is actually an user interface. It mainly uses 'pictctrl', 'colls' and the associated textfiles. Certain textfiles are uploaded to and downloaded from a ftp-server with 'jit.uldl'. This is running on a mac mini. It crashes alone.
      I hope you have any idea what's causing this. I will try to send the crashlog tomorrow morning.
    • Apr 20 2010 | 12:40 pm
      Hello Leo,
      Attached is the latest crashlog. I hope you can get some information out of it.
    • Apr 20 2010 | 10:47 pm
      Seems to be a FTP problem, surely related to jit.uldl. I have no experience with this object, so I'm afraid I can't help you more.
      Is your ftp server on a local network ? Maybe a certain file is too big or corrupted. Maybe you can list in a log file what files are up- and downloaded before up- or downloading them.
    • Apr 21 2010 | 8:18 am
      Hello Leo,
      Thanks again! Do you mean the prototypes and the FTP-server are in the same local network, or that the FTP-server itself is part of a local network? The FTP-server is in my house with many other computers connected to the internet with a Linksys router.
      Good idea to make a log of the files that are -up and downloaded, I will do so immediately.