close
Comments you submit will be routed for moderation. If you have an account, please log in first.
Modify

Opened 4 years ago

Closed 4 years ago

#161 closed bug

Crash when press send now on zune 68k(YAM do push method and delete the Object before)

Reported by: Bernd Roesch Owned by:
Priority: low Milestone:
Component: undefined Version: 2.6
Severity: trivial Keywords:
Cc: OS Platform:
Blocked By: Blocking:
Release Notes:

Description

I test YAM 2.6 release and 2.7 dev debug Version for 68k.Version do PushMethod, delete the object and later on
do_pushedmethods zune 68k execute OM_Set but the object is not here.Its a release mousebutton Event.

I use the default settings of a clean 2.6 install
this situation happen when write a mail and press send
now.
The Mail is then send correct and after the send progress Requester is close, the Problem happen.

what does YAM do with the pushMethod after press the send now Button ?

The output "push method" and "wrong object data in OM_notify set detect do Enforcer Hit for backtrace" is from zune.The other output is from the

YAM 2.7 debug Version build: 20100421, but YAM2.6 release have same Problem

push method

Timer.c:165:timer[4]: already stopped

Timer.c:165:timer[3]: already stopped

push method

Timer.c:165:timer[4]: already stopped

Timer.c:165:timer[3]: already stopped

push method
wrong object data in OM_notify set detect do Enforcer Hit for backtrace

YAM 2.7-dev [OS3/m68k] build: 20100421 startup
Exec version: v45.99
no 'yamdebug' variable found
set debug classes/flags (env:yamdebug): 000000F6/00000003
Normal processing follows *

YAM.c:232:InitLib: library intuition.library v40.88 successfully opened.
YAM.c:232:InitLib: library icon.library v53.543 successfully opened.
YAM.c:232:InitLib: library utility.library v40.1 successfully opened.
YAM.c:232:InitLib: library diskfont.library v46.0 successfully opened.

extrasrc/NewReadArgs.c:221:Args: 14
extrasrc/NewReadArgs.c:489:ReadArgs() okay

YAM.c:2553:ProgDir.: 'h1:YAM 2.5'
YAM.c:2554:ProgName: 'YAM_z'

YAM.c:669:didn't find any valid AutoDST facility active!

YAM.c:232:InitLib: library locale.library v44.5 successfully opened.
Locale.c:2968:successfully opened YAM.catalog version 7
YAM.c:232:InitLib: library graphics.library v40.24 successfully opened.
YAM.c:232:InitLib: library layers.library v40.1 successfully opened.
YAM.c:232:InitLib: library workbench.library v45.131 successfully opened.
YAM.c:232:InitLib: library keymap.library v40.4 successfully opened.
YAM.c:232:InitLib: library iffparse.library v40.1 successfully opened.
YAM.c:232:InitLib: library rexxsyslib.library v44.1 successfully opened.
YAM.c:232:InitLib: library datatypes.library v44.47 successfully opened.
YAM.c:232:InitLib: library cybergraphics.library v45.0 successfully opened.
YAM.c:232:InitLib: library muimaster.library v19.41 successfully opened.
YAM.c:232:InitLib: library openurl.library v7.5 successfully opened.
YAM.c:232:InitLib: library codesets.library v6.10 successfully opened.
YAM.c:236:InitLib: can't open library expat.library with minimum version v1.0
YAM.c:232:InitLib: library amisslmaster.library v3.6 successfully opened.

YAM.c:1926:successfully opened AmiSSL library.

YAM.c:299:checking for v26.2+ of 'TheBar.mcc'
YAM.c:322:TheBar.mcc v26.5 found through MUIA_Version/Revision
YAM.c:299:checking for v26.2+ of 'TheBarVirt.mcc'
YAM.c:322:TheBarVirt.mcc v26.5 found through MUIA_Version/Revision
YAM.c:299:checking for v26.2+ of 'TheButton.mcc'
YAM.c:322:TheButton.mcc v26.5 found through MUIA_Version/Revision
YAM.c:299:checking for v11.16+ of 'BetterString.mcc'
YAM.c:322:BetterString.mcc v11.17 found through MUIA_Version/Revision
YAM.c:299:checking for v20.121+ of 'NList.mcc'
YAM.c:322:NList.mcc v20.122 found through MUIA_Version/Revision
YAM.c:299:checking for v19.76+ of 'NListview.mcc'
YAM.c:322:NListview.mcc v19.77 found through MUIA_Version/Revision
YAM.c:299:checking for v19.57+ of 'NFloattext.mcc'
YAM.c:322:NFloattext.mcc v19.58 found through MUIA_Version/Revision
YAM.c:299:checking for v18.28+ of 'NListtree.mcc'
YAM.c:322:NListtree.mcc v18.29 found through MUIA_Version/Revision
YAM.c:299:checking for v15.2+ of 'NBalance.mcc'
YAM.c:322:NBalance.mcc v15.3 found through MUIA_Version/Revision
YAM.c:299:checking for v15.28+ of 'TextEditor.mcc'
YAM.c:322:TextEditor.mcc v15.31 found through MUIA_Version/Revision
YAM.c:797:creating startup semaphore...

YAM.c:1979:setup internal MUI classes...
YAM.c:1984:creating root object...

ImageCache.c:196:image 'logo' NOT found in cache, creating new node

YAM.c:1997:init libraries...

YAM.c:232:InitLib: library xadmaster.library v12.1 successfully opened.
YAM.c:232:InitLib: library xpkmaster.library v5.2 successfully opened.

YAM.c:1562:loading configuration...

YAM_CO.c:712:no PGP version found to be installed in 'C:'

ImageCache.c:196:image 'config_abook' NOT found in cache, creating new node
ImageCache.c:196:image 'config_abook_big' NOT found in cache, creating new node
ImageCache.c:196:image 'config_answer' NOT found in cache, creating new node
ImageCache.c:196:image 'config_answer_big' NOT found in cache, creating new node
ImageCache.c:196:image 'config_filters' NOT found in cache, creating new node
ImageCache.c:196:image 'config_filters_big' NOT found in cache, creating new node
ImageCache.c:196:image 'config_firststep' NOT found in cache, creating new node
ImageCache.c:196:image 'config_firststep_big' NOT found in cache, creating new node
ImageCache.c:196:image 'config_lists' NOT found in cache, creating new node
ImageCache.c:196:image 'config_lists_big' NOT found in cache, creating new node
ImageCache.c:196:image 'config_lookfeel' NOT found in cache, creating new node
ImageCache.c:196:image 'config_lookfeel_big' NOT found in cache, creating new node
ImageCache.c:196:image 'config_mime' NOT found in cache, creating new node
ImageCache.c:196:image 'config_mime_big' NOT found in cache, creating new node
ImageCache.c:196:image 'config_misc' NOT found in cache, creating new node
ImageCache.c:196:image 'config_misc_big' NOT found in cache, creating new node
ImageCache.c:196:image 'config_network' NOT found in cache, creating new node
ImageCache.c:196:image 'config_network_big' NOT found in cache, creating new node
ImageCache.c:196:image 'config_newmail' NOT found in cache, creating new node
ImageCache.c:196:image 'config_newmail_big' NOT found in cache, creating new node
ImageCache.c:196:image 'config_read' NOT found in cache, creating new node
ImageCache.c:196:image 'config_read_big' NOT found in cache, creating new node
ImageCache.c:196:image 'config_scripts' NOT found in cache, creating new node
ImageCache.c:196:image 'config_scripts_big' NOT found in cache, creating new node
ImageCache.c:196:image 'config_security' NOT found in cache, creating new node
ImageCache.c:196:image 'config_security_big' NOT found in cache, creating new node
ImageCache.c:196:image 'config_signature' NOT found in cache, creating new node
ImageCache.c:196:image 'config_signature_big' NOT found in cache, creating new node
ImageCache.c:196:image 'config_spam' NOT found in cache, creating new node
ImageCache.c:196:image 'config_spam_big' NOT found in cache, creating new node
ImageCache.c:196:image 'config_start' NOT found in cache, creating new node
ImageCache.c:196:image 'config_start_big' NOT found in cache, creating new node
ImageCache.c:196:image 'config_update' NOT found in cache, creating new node
ImageCache.c:196:image 'config_update_big' NOT found in cache, creating new node
ImageCache.c:196:image 'config_write' NOT found in cache, creating new node
ImageCache.c:196:image 'config_write_big' NOT found in cache, creating new node
ImageCache.c:196:image 'folder_fold' NOT found in cache, creating new node
ImageCache.c:196:image 'folder_unfold' NOT found in cache, creating new node
ImageCache.c:196:image 'folder_incoming' NOT found in cache, creating new node
ImageCache.c:196:image 'folder_incoming_new' NOT found in cache, creating new node
ImageCache.c:196:image 'folder_outgoing' NOT found in cache, creating new node
ImageCache.c:196:image 'folder_outgoing_new' NOT found in cache, creating new node
ImageCache.c:196:image 'folder_sent' NOT found in cache, creating new node
ImageCache.c:196:image 'folder_spam' NOT found in cache, creating new node
ImageCache.c:196:image 'folder_spam_new' NOT found in cache, creating new node
ImageCache.c:196:image 'folder_trash' NOT found in cache, creating new node
ImageCache.c:196:image 'folder_trash_new' NOT found in cache, creating new node
ImageCache.c:196:image 'status_attach' NOT found in cache, creating new node
ImageCache.c:196:image 'status_crypt' NOT found in cache, creating new node
ImageCache.c:196:image 'status_delete' NOT found in cache, creating new node
ImageCache.c:196:image 'status_download' NOT found in cache, creating new node
ImageCache.c:196:image 'status_error' NOT found in cache, creating new node
ImageCache.c:196:image 'status_forward' NOT found in cache, creating new node
ImageCache.c:196:image 'status_group' NOT found in cache, creating new node
ImageCache.c:196:image 'status_hold' NOT found in cache, creating new node
ImageCache.c:196:image 'status_mark' NOT found in cache, creating new node
ImageCache.c:196:image 'status_new' NOT found in cache, creating new node
ImageCache.c:196:image 'status_old' NOT found in cache, creating new node
ImageCache.c:196:image 'status_reply' NOT found in cache, creating new node
ImageCache.c:196:image 'status_report' NOT found in cache, creating new node
ImageCache.c:196:image 'status_sent' NOT found in cache, creating new node
ImageCache.c:196:image 'status_signed' NOT found in cache, creating new node
ImageCache.c:196:image 'status_spam' NOT found in cache, creating new node
ImageCache.c:196:image 'status_unread' NOT found in cache, creating new node
ImageCache.c:196:image 'status_urgent' NOT found in cache, creating new node
ImageCache.c:196:image 'status_waitsend' NOT found in cache, creating new node

ImageCache.c:657:init readwindow toolbar: 13390870
ImageCache.c:660:init writewindow toolbar: 13391ac0
ImageCache.c:663:init abookwindow toolbar: 133b5658

YAM.c:1584:creating GUI...

Timer.c:165:timer[5]: already stopped

Timer.c:165:timer[4]: already stopped

Timer.c:165:timer[3]: already stopped

YAM_MAf.c:546:skipping index loading due to LoadedMode 2 for folder 'Incoming'

YAM_MAf.c:546:skipping index loading due to LoadedMode 2 for folder 'Incoming'

Timer.c:165:timer[5]: already stopped

YAM.c:2110:user 'John Doe' differs from of the last start, performing startup actions

Timer.c:165:timer[10]: already stopped

YAM.c:2648:YAM allocated signals:
YAM.c:2649: adstsig = 00000000
YAM.c:2650: timsig = 04000000
YAM.c:2651: rexxsig = 00800000
YAM.c:2652: appsig = 02000000
YAM.c:2653: applibsig = 00000000
YAM.c:2654: writeWinNotifySig = 01000000
YAM.c:2655: threadsig = c0000000

Timer.c:85:timer[1]: secs and micros are zero, no prepare required
Timer.c:123:timer[1]: either already running or not prepared to get fired

Timer.c:165:timer[7]: already stopped

push method

YAM_MAf.c:546:skipping index loading due to LoadedMode 2 for folder 'Outgoing'

Timer.c:165:timer[5]: already stopped

Timer.c:165:timer[4]: already stopped
Timer.c:165:timer[3]: already stopped

Timer.c:165:timer[4]: already stopped

Timer.c:165:timer[3]: already stopped

push method

Timer.c:165:timer[4]: already stopped

Timer.c:165:timer[3]: already stopped

push method

Timer.c:165:timer[4]: already stopped

Timer.c:165:timer[3]: already stopped

push method
wrong object data in OM_notify set detect do Enforcer Hit for backtrace

Attachments (0)

Change History (3)

comment:1 Changed 4 years ago by damato

  • Status changed from new to pending

Sorry, but as far as I can see YAM is doing nothing wrong here. It seems to be a problem of zune and not YAM. So why are you posting this bug report here? You should instead continue to track the problem in the AROS mailing list and try to solve the problem in zune.

In addition, please use the attachment functionality of our bugtracker instead of posting large obfuscated text in the comments.

comment:2 Changed 4 years ago by damato

  • Priority changed from undecided to low
  • Severity changed from major to trivial

comment:3 Changed 4 years ago by trac-robot

  • Status changed from pending to closed

This ticket was closed automatically by the system. It was previously set to a Pending status and hasn't been updated within 14 days.

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.

This list contains all users that will be notified about changes made to this ticket.

These roles will be notified: Reporter, Owner, Subscriber

Nobody is currently notified about changes to this ticket.