New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed assertion warning: (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL' #13

Closed
apjanke opened this Issue Jun 21, 2018 · 4 comments

Comments

1 participant
@apjanke
Contributor

apjanke commented Jun 21, 2018

When I fire up the Octave.app 4.4.0 beta build, I get this error message as the first output in the Command Window:

>> 2018-06-21 09:18 octave-gui[48030] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'

screen shot 2018-06-23 at 2 00 53 am

@apjanke apjanke added the bug label Jun 21, 2018

@apjanke apjanke added this to Needs triage in Octave.app Jun 21, 2018

@apjanke apjanke moved this from Needs triage to High priority in Octave.app Jun 21, 2018

@apjanke apjanke added this to the 4.4.0 milestone Jun 21, 2018

@apjanke apjanke changed the title from Failed assertion when starting Octave: to Failed assertion when starting Octave: '(SInt64)last_id > 0LL' Jun 21, 2018

@apjanke

This comment has been minimized.

Show comment
Hide comment
@apjanke

apjanke Jun 23, 2018

Contributor

I see a bunch of these during __run_test_suite__, too.

  libinterp/dldfcn/gzip.cc-tst ................................2018-06-23 01:36 octave-gui[56643] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'

2018-06-23 01:36 octave-gui[56643] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'

2018-06-23 01:36 octave-gui[56643] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'

2018-06-23 01:36:14.466 octave-gui[56643:31314756] Path  given to -[NSWorkspace iconForFile:] is not a full path.
2018-06-23 01:36 octave-gui[56643] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'

2018-06-23 01:36 octave-gui[56643] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'

2018-06-23 01:36 octave-gui[56643] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'

2018-06-23 01:36 octave-gui[56643] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'

2018-06-23 01:36 octave-gui[56643] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'

2018-06-23 01:36 octave-gui[56643] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'

2018-06-23 01:36 octave-gui[56643] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'

2018-06-23 01:36 octave-gui[56643] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'

2018-06-23 01:36 octave-gui[56643] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'

2018-06-23 01:36 octave-gui[56643] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'
Contributor

apjanke commented Jun 23, 2018

I see a bunch of these during __run_test_suite__, too.

  libinterp/dldfcn/gzip.cc-tst ................................2018-06-23 01:36 octave-gui[56643] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'

2018-06-23 01:36 octave-gui[56643] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'

2018-06-23 01:36 octave-gui[56643] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'

2018-06-23 01:36:14.466 octave-gui[56643:31314756] Path  given to -[NSWorkspace iconForFile:] is not a full path.
2018-06-23 01:36 octave-gui[56643] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'

2018-06-23 01:36 octave-gui[56643] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'

2018-06-23 01:36 octave-gui[56643] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'

2018-06-23 01:36 octave-gui[56643] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'

2018-06-23 01:36 octave-gui[56643] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'

2018-06-23 01:36 octave-gui[56643] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'

2018-06-23 01:36 octave-gui[56643] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'

2018-06-23 01:36 octave-gui[56643] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'

2018-06-23 01:36 octave-gui[56643] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'

2018-06-23 01:36 octave-gui[56643] (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL'
@apjanke

This comment has been minimized.

Show comment
Hide comment
@apjanke

apjanke Jun 23, 2018

Contributor

Unfortunately, it looks like this is coming from one of Octave's dependencies, and not Octave itself. There's no call to FSEventStreamFlushSync in Octave.

[~/local/repos/octave]
$ grep -r FSEventStreamFlushSync *

It does occur in Qt:

[~/tmp/qt/qt-everywhere-src-5.11.1]
$ grep -r FSEventStreamFlushSync *
qtbase/src/corelib/io/qfilesystemwatcher_fsevents.mm:        FSEventStreamFlushSync(stream);
qtbase/src/corelib/io/qfilesystemwatcher_fsevents.mm:    // soft-assert in FSEventStreamFlushSync in CarbonCore when no event occurred.

And Octave appears to use the Qt filesystem watcher, only in the File Editor.

[~/local/repos/octave]
$ grep -r QFileSystemWatcher *
libgui/src/m-editor/file-editor-tab.h:#include <QFileSystemWatcher>
libgui/src/m-editor/file-editor-tab.h:    QFileSystemWatcher _file_system_watcher;

The actual warning message appears to be emitted by one of Apple's libraries that Qt is linked against.

Contributor

apjanke commented Jun 23, 2018

Unfortunately, it looks like this is coming from one of Octave's dependencies, and not Octave itself. There's no call to FSEventStreamFlushSync in Octave.

[~/local/repos/octave]
$ grep -r FSEventStreamFlushSync *

It does occur in Qt:

[~/tmp/qt/qt-everywhere-src-5.11.1]
$ grep -r FSEventStreamFlushSync *
qtbase/src/corelib/io/qfilesystemwatcher_fsevents.mm:        FSEventStreamFlushSync(stream);
qtbase/src/corelib/io/qfilesystemwatcher_fsevents.mm:    // soft-assert in FSEventStreamFlushSync in CarbonCore when no event occurred.

And Octave appears to use the Qt filesystem watcher, only in the File Editor.

[~/local/repos/octave]
$ grep -r QFileSystemWatcher *
libgui/src/m-editor/file-editor-tab.h:#include <QFileSystemWatcher>
libgui/src/m-editor/file-editor-tab.h:    QFileSystemWatcher _file_system_watcher;

The actual warning message appears to be emitted by one of Apple's libraries that Qt is linked against.

@apjanke apjanke changed the title from Failed assertion when starting Octave: '(SInt64)last_id > 0LL' to Failed assertion warning: (FSEvents.framework) FSEventStreamFlushSync(): failed assertion '(SInt64)last_id > 0LL' Jun 23, 2018

@apjanke

This comment has been minimized.

Show comment
Hide comment
@apjanke

apjanke Jun 23, 2018

Contributor

Patching Qt to remove that FSEventStreamFlushSync(stream) call got rid of the warning. (Hope it's okay to remove, as stated here.

Done in octave-app/homebrew-octave-app@4950d0a.

Will probably need to add and switch to a qt-octave-app formula to keep this clean.

Contributor

apjanke commented Jun 23, 2018

Patching Qt to remove that FSEventStreamFlushSync(stream) call got rid of the warning. (Hope it's okay to remove, as stated here.

Done in octave-app/homebrew-octave-app@4950d0a.

Will probably need to add and switch to a qt-octave-app formula to keep this clean.

@apjanke apjanke closed this Jun 23, 2018

Octave.app automation moved this from High priority to Closed Jun 23, 2018

@apjanke

This comment has been minimized.

Show comment
Hide comment
@apjanke

apjanke Jun 23, 2018

Contributor

This warning only happens sometimes, too: I rebuilt Octave.app with an unpatched Qt, and when I fired it up, I'm not getting the assertion failure message any more.

Contributor

apjanke commented Jun 23, 2018

This warning only happens sometimes, too: I rebuilt Octave.app with an unpatched Qt, and when I fired it up, I'm not getting the assertion failure message any more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment